I warned you guys that when I started my CX700 port that my lack of intellect would be a problem. Well, I don't even know where to start.
I assume that I need to create a VT8454 directory in targets/via and mainboard/via (VT8454 is the eval board,I'm actually working on getting an MSI Industrial MS-9802 so I may have to copy everything over to that since I doubt the VT8454 will do anyone any good). But I'm not sure what to copy into those directories as a starting point? Is the EPIA-M good enough, I'm having a hard time parsing the files in there so I'm at a loss. In the src/northbridge and src/sourthbridge directories I assume I'll need to create a cx700 directory. But once again I'm at a loss as to which directory to use as a base platform. Everything I know about the CX700 seems so different that I'm concerned nothing will work. If I can just get it started to a point where I start getting serial output I think I'll have a place where I can at least start working and try things. If I use the EPIA-M setup, do you think I'll at least get that far? I've included my lspci and dmidecode output for everyone's reading pleasure.
Thanks,
Randy
On Wed, Apr 18, 2007 at 09:39:54AM -0500, Randall Philipson wrote:
I assume that I need to create a VT8454 directory in targets/via and mainboard/via
Yep. In mainboard/ you'll need to put one Options.lb that lists all the options used by this mainboard, and their defaults.
Also a file Config.lb which can do clever calculations using options set by Options.lb, but most importantly it is sort-of a macro file for generating the Makefile and some of the binaries. Here you'll specify what other files to pull in and what devices are where on the PCI bus.
In targets you'll have a Config.lb with the options that should be used to build the board, here you can overried the defaults set by mainboard/*/Options.lb, but AFAICS the mainboard/*/Config.lb can not be overridden.
(VT8454 is the eval board,I'm actually working on getting an MSI Industrial MS-9802 so I may have to copy everything over to that since I doubt the VT8454 will do anyone any good).
Right. Please make two directories. Work with the mainboard/via/vt8454 until it works, then copy things over to mainboard/msi/ms9802.
But I'm not sure what to copy into those directories as a starting point? Is the EPIA-M good enough, I'm having a hard time parsing the files in there so I'm at a loss.
It seems the EPIA-M port is rather cut-n-pasty from various other files. Not 100% tidy, but it does work.
In the src/northbridge and src/sourthbridge directories I assume I'll need to create a cx700 directory.
northbridge yes, southbridge maybe. The southbridge seems to be a vt8237 core, perhaps you don't need to make a special southbridge directory for it.
What about CPU? Does your board have a C3 or C7 CPU? Currently there's only code for C3 in LB.
But once again I'm at a loss as to which directory to use as a base platform. Everything I know about the CX700 seems so different that I'm concerned nothing will work. If I can just get it started to a point where I start getting serial output
This is definately the starting point, but it already requires the superio to be working properly. There's no support for vt8237 but perhaps the vt8235 is at least a little similar. (Wasn't the 8237 being worked on already by the way?)
I think I'll have a place where I can at least start working and try things. If I use the EPIA-M setup, do you think I'll at least get that far?
Maybe if you're lucky. epia-m has vt8235. Try it. :)
I've included my lspci and dmidecode output for everyone's reading pleasure.
Not so much a pleasure since everything is listed as unknown. :\ Could you update your pci.ids? (Look in /usr/share somewhere.)
0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge (prog-if 00 [Normal decode])
Here's the 8237.
//Peter
Peter Stuge wrote:
In the src/northbridge and src/sourthbridge directories I assume I'll need to create a cx700 directory.
northbridge yes, southbridge maybe. The southbridge seems to be a vt8237 core, perhaps you don't need to make a special southbridge directory for it.
I'm rather curious, I'm wondering if CX700 = CN700 + VT8237. If that's the case, CX700 should work with CN700 code, which should be ready by the 27th. I'll take a look later, right now I'm off to work.
Also, do you have the CX700 datasheets? And is your board using ddr or ddr2?
What about CPU? Does your board have a C3 or C7 CPU? Currently there's only code for C3 in LB.
C7 *should* work (if I'm reading the docs right, that is) with the C3 code, the only thing that needs to be changed is the device IDs added to src/cpu/via/model_centaur/model_centaur_init.c, C7 is 0x06A[0-F]. Other issues may crop up after ram is working, but again should be working by the 27th, if all goes well.
But once again I'm at a loss as to which directory to use as a base platform. Everything I know about the CX700 seems so different that I'm concerned nothing will work. If I can just get it started to a point where I start getting serial output
This is definately the starting point, but it already requires the superio to be working properly. There's no support for vt8237 but perhaps the vt8235 is at least a little similar. (Wasn't the 8237 being worked on already by the way?)
Yes, it is ;)
I think I'll have a place where I can at least start working and try things. If I use the EPIA-M setup, do you think I'll at least get that far?
Maybe if you're lucky. epia-m has vt8235. Try it. :)
VT8235 has its own superio, and epia-m uses it. VT8237 doesn't. Also, the device IDs are entirely different, and so are some of the registers. I used epia-m as a starting point also, but it requires a lot of gutting out and fixing up.
-Corey
On Wed, Apr 18, 2007 at 04:51:52PM -0400, Corey Osgood wrote:
Peter Stuge wrote:
In the src/northbridge and src/sourthbridge directories I assume I'll need to create a cx700 directory.
northbridge yes, southbridge maybe. The southbridge seems to be a vt8237 core, perhaps you don't need to make a special southbridge directory for it.
I'm rather curious, I'm wondering if CX700 = CN700 + VT8237.
Probably.
If that's the case, CX700 should work with CN700 code
They've probably tweaked it a bit. It's like GX1+CS5530 -> Geode; Very similar, but not identical.
I think I'll have a place where I can at least start working and try things. If I use the EPIA-M setup, do you think I'll at least get that far?
Maybe if you're lucky. epia-m has vt8235. Try it. :)
VT8235 has its own superio, and epia-m uses it. VT8237 doesn't.
Ah. No go then.
Also, the device IDs are entirely different, and so are some of the registers. I used epia-m as a starting point also, but it requires a lot of gutting out and fixing up.
Aye. I'll attempt an epia-cn port once cn700 is working. Maybe even in v3.
//Peter
Peter Stuge wrote:
On Wed, Apr 18, 2007 at 04:51:52PM -0400, Corey Osgood wrote:
Peter Stuge wrote:
In the src/northbridge and src/sourthbridge directories I assume I'll need to create a cx700 directory.
northbridge yes, southbridge maybe. The southbridge seems to be a vt8237 core, perhaps you don't need to make a special southbridge directory for it.
I'm rather curious, I'm wondering if CX700 = CN700 + VT8237.
Probably.
Probably would be best just to have everything in northbridge/cx700, to avoid any confusion. Either that, or we can probably hack the vt8237r code to make it work for both, so there's not two separate sets of nearly identical code.
If that's the case, CX700 should work with CN700 code
They've probably tweaked it a bit. It's like GX1+CS5530 -> Geode; Very similar, but not identical.
Yeah, seems that way. The device IDs are almost all CN700/VT8237R + 0010. We'll know a lot more once we get working on this, and also once I get the CN700 docs (which I'm still waiting on Via on, deadline's been pushed back thankfully, but I'm still desperate for 'em).
Also, the device IDs are entirely different, and so are some of the registers. I used epia-m as a starting point also, but it requires a lot of gutting out and fixing up.
Aye. I'll attempt an epia-cn port once cn700 is working. Maybe even in v3.
Good to hear!
-Corey
-
Corey Osgood -
Peter Stuge -
Randall Philipson