Re: [Etherboot-developers] UNDI driver

[<ebi...@ln...>]

Michael Brown <mb...@fe...> writes:

> > > Another small difference is that the UNDI driver claims to be able to
> > > handle any NIC, whereas most drivers specify a list of PCI IDs.  If the
> > > UNDI driver can't find an UNDI ROM for the card, it will give up.  We may
> > > therefore need to change the core driver scanning code to try multiple
> > > drivers for a specific PCI vendor:device ID, if people are going to want 
> > > to build images that contain UNDI and other drivers.
> > Actually I am pretty certain that functionality is already present.
> 
> There's a comment in pci.c that says 
>   /* Assume there is only one match of the correct type */
> 
> I haven't checked the actual code, so it might be a leftover comment.

It needs a close look but it appears to be a left over comment.
 
> > I had a few bug fixes sitting in my tree with respect to pci scanning
> > and I have just commited them.
> 
> I'm not seeing anything appearing in CVS.  Can you check that the commit 
> worked ok?

I put everything in the tree and then for got the all important
cvs commit .

The code should show up now.  The changes were very tiny but there
was an obscure bug that etherboot would miss the second NIC in a multi-NIC
configuration.  If one nic was a subfunction.  That should be cleared up
now.

Eric