Hi,
while I was trying to improve Supertek ST-3WT support, I noticed a
little bit ugly thing. The final southbridge fixup for the cs5530
sets interrupt mapping and initializes USB in a way that conflicts
with what you need on the ST-3wt. The way I got network working
is kind of a workaround as I'm overwriting those settings in the
motherboard specific file. Not too evil as it is now, but LinuxBIOS
is still far away from what award bios can do on this machine.
* USB is not working
* Sound is not working
* VGA is not working (And running the VGA BIOS does not really help)
* APM etc
I started changing this and I got USB working by fiddling around with
the VSA/SMI stuff (Well, at least partly. with "webcam" from the xawtv
suite I get 2-3 pictures, then it breaks with I/O error, so there's
probably some SMI or timing problem.
Generally nothing bad happens. I can just overwrite the settings I
need to, even though they have been made in
southbridge/nsc/cs5530/southbridge.c, but this is against the principle
to keep the code as small as possible and makes it not really easy to
understand, why values are first set and then overwritten.
Another way to go might be to move USB and such completely to mainboard
setup. But this again will make porting to a new geode board a bit ugly
(or maybe not. Code that doesn't work on a new motherboard, will not do
any good anyways)
The third idea would be to make southbridge.c even more configurable
than it is now. This will give some additional config options but keep
the concept clean. (USB is part of the southbridge, not of the
motherboard)
Is there any preferred direction?
Another thing is I am not able to reboot on the ST-3WT. Any idea where
to start debugging?
Best regards,
Stefan Reinauer
--
Ok hex 4666 dup negate do i 4000 dup 2* negate do " *" 0 dup 2dup 1e 0 do
2swap * e >>a 2* 5 pick + -rot - j + dup dup * e >>a rot dup dup * e >>a
rot swap 2dup + 10000 > if 3drop 3drop " " 0 dup 2dup leave then loop
2drop 2drop type 268 +loop cr drop 5de +loop
