* Eric W. Biederman <[EMAIL PROTECTED]> [020305 23:01]:
> O.k. I wasn't clear.  Motherboard independent does above not mean you
> can not have smaller builds that only support a subset of the hardware.
> 
> Motherboard independent means that you do have any code that says:
> if (motherboard_a) do x
> if (motherboard_b) do y
> if (motherboard_c) do z
> in the code.  
> And it also means that you can compile one big image that will work
> on everything.  
 
Host bridges and other PCI stuff can be probed even in early system 
initialization, Phillip Rumpf wrote some code to do that. But for the
SuperIO stuff, which is often(always?) not done in PCI hardware, you
don't have a descent way of probing. This could be handled by variable
areas in the bios image like the ESCD stuff. Is this what is done via
the LinuxBIOS table?

> With restrictions like that if you can move significant chunks of the
> PCI init out of LinuxBIOS fine.  But all of the motherboard specific
> information needs to live in LinuxBIOS.  Otherwise testing of the
> other pieces becomes insane.

Exactly. Hide the specific stuff early and handle pci initialization in
a more generic per device way.

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* 3 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 266 +loop cr 5de +loop

Reply via email to