[tulip] how to compile into 2.2.18 kernel?

[Roisman, Dani]

Yes, I needed that new file, as well as the new pci-scan.h file, and now it
enumerates the correct number, thanks.

FYI, there was one thing I had to differently than how you documented
compiling into the kernel.

You suggest adding the following to linux/drivers/net/Makefile:

+L_OBJS   := auto_irq.o pci-scan.o
+M_OBJS   := pci-scan.o
 
That didn't work for me.  It only worked when I did the following:

L_OBJS   += auto_irq.o pci-scan.o
M_OBJS   += pci-scan.o

I really don't know the difference between the two (not really a
programmer), except the latter works.

----
Dani Roisman
droisman@station.sony.com

> -----Original Message-----
> From: Donald Becker [mailto:becker@scyld.com]
> Sent: Thursday, March 29, 2001 2:07 PM
> To: Roisman, Dani
> Cc: tulip@scyld.com
> Subject: Re: [tulip] how to compile into 2.2.18 kernel?
> 
> 
> On Tue, 20 Mar 2001, Roisman, Dani wrote:
> 
> > Becker's instructions on 
> http://www.scyld.com/network/updates.html result in
> > a system that enumerates the 1-port tulip card 8 times 
> (e.g. I have eth0
> > thru eth7 found as 21143's, even though I only have one 
> ethernet card!)
> 
> This is caused by later 2.2.* kernels calling the PCI probe routine
> multiple times.  Drivers that use PCI memory space can not register
> their memory region for exclusive access, unlike drivers 
> using I/O space
> access.
> 
> The fix is in the v1.04 pci-scan code from
>       ftp://www.scyld.com/pub/network/test/pci-scan.c
> 
> Donald Becker				becker@scyld.com
> Scyld Computing Corporation		http://www.scyld.com
> 410 Severn Ave. Suite 210		Second Generation 
> Beowulf Clusters
> Annapolis MD 21403			410-990-9993
> 
>