Hello all,
I would like to re-task a bunch of Hyundai w152 thin clients with on board XGA screens (circa 2003) running on Geode SCx200 (SC2200 specifically) SOC which according to the supported chip-sets page hasn't been tested since back in coreboot v1.
My questions:
Would I be better off starting with the old v1 code base and back porting the PC87360 Super IO code (which is in the v4 code base) or start from v4 code base and bring the scx200 code forward? and Given that the scx200 product lines have been retired would working on v4 support for them benefit anyone else besides myself?
I have 12 of these (plus a 13th I sacrificed so I can trace the motherboard connections to the CPU) so am willing to put a bit of work into doing the board support for my own purposes but I can't really see anyone else using the port in the future considering the hardware is all but extinct.
From the hind site of of somebody who is all ready familiar with the
coreboot code what would be the shortest route for me to get these things booting under my control?
The important parts of the system are: NSC Geode sc2200 cpu/SoC, NSC PC87360 SuperIO, SST 39SF020A 2 Mbit flash (with XpressROM installed) M-Systems MD-2811-032-v3 DiskOnChip (with Windows CE.Net 4.1 installed), 64MB ram module
Thanks in advance for your input -regards Shane Norris
start with v1 until you're pretty sure it all works, then you could try a forward port. The issue with v1 is that the last time we built that board was the gcc 2.96 toolchain and we know that toolchain version if a factor.
ron
On 9/25/10 5:30 PM, ron minnich wrote:
start with v1 until you're pretty sure it all works, then you could try a forward port. The issue with v1 is that the last time we built that board was the gcc 2.96 toolchain and we know that toolchain version if a factor.
ron
That said, I got the v1 tree compiling on my system with a gcc 4 toolchain a while ago, but I never tested the resulting binaries as I don't have any hardware left.
Stefan
yeah, I would shoot for 1. build v1 tree 2. load on your hardware and see if it works. If it works, stop there and test it out 3. if you really care, port to v4
ron
Thanks to all that replied, so looks like ill be starting with v1. Hopefully I can find an archived live-cd from around that time with a tool chain all ready to go. Longer term I plan to get v4 going since I will still need to support these things once there running.
-r Shane
On Sat, Sep 25, 2010 at 11:28 PM, Shane Norris norlesh@gmail.com wrote:
Hello all,
I would like to re-task a bunch of Hyundai w152 thin clients with on board XGA screens (circa 2003) running on Geode SCx200 (SC2200 specifically) SOC which according to the supported chip-sets page hasn't been tested since back in coreboot v1.
My questions:
Would I be better off starting with the old v1 code base and back porting the PC87360 Super IO code (which is in the v4 code base) or start from v4 code base and bring the scx200 code forward? and Given that the scx200 product lines have been retired would working on v4 support for them benefit anyone else besides myself?
I have 12 of these (plus a 13th I sacrificed so I can trace the motherboard connections to the CPU) so am willing to put a bit of work into doing the board support for my own purposes but I can't really see anyone else using the port in the future considering the hardware is all but extinct.
From the hind site of of somebody who is all ready familiar with the coreboot code what would be the shortest route for me to get these things booting under my control?
The important parts of the system are: NSC Geode sc2200 cpu/SoC, NSC PC87360 SuperIO, SST 39SF020A 2 Mbit flash (with XpressROM installed) M-Systems MD-2811-032-v3 DiskOnChip (with Windows CE.Net 4.1 installed), 64MB ram module
Thanks in advance for your input -regards Shane Norris
-
ron minnich -
Shane Norris -
Stefan Reinauer