Re: [Etherboot-developers] UNDI driver

[<prl...@sy...>]

> > Thought - can the UNDI driver avoid the annoying attribute of 3Com's PXE
> > initialisation (and therefore probably everyone else's, though I haven't
> > tried) with multiple NICs that the MAC address used is that of the
> > *last* NIC to initialise? This confuses people because it almost always
> > means that it never uses the one that Linux calls eth0.
> 
> MAC address used is the MAC address stored on the NIC EEPROM; the one 
> known to UNDI as the "Permanent Node Address".
> 
> We will use PCI cards in the same order that Etherboot normally finds 
> them.  If Etherboot uses the same scanning order as Linux, then we should 
> end up using the one that Linux calls eth0.  This is independent of the 
> Etherboot UNDI driver; it's determined by pci.c.

The order is "normal Etherboot order, whatever that is". Good, this is a
definite win.

> The UNDI driver will therefore consist of  two files: undi.c and
> undi_wrapper.S (plus the headers); most drivers consist only of a single
> C file.  The Makefile will, I think, have to be altered to allow drivers
> to consist of more than just the one file.

Oh, I see. I suppose you could munge the assembler into the C (if it's
GNU friendly, but it's a good thing to have drivers be >1 C file.