[tulip] Compiling in the tulip driver

David Shochat shochat@acm.org
Wed, 22 Nov 2000 17:09:38 -0500

That's a novel approach and maybe there's a way to make it work. But if 
you just want to get things working, here is how I did it:
1. With the kernel built and running normally (using only drivers that 
came with it), copy those 4 files into some random directory.
2. compile them using the compile commands that you will find in the .c 
source files.
3. (as root) Copy pci-scan.o and tulip.o into /lib/modules/`uname 
-r`/net [you may want to rename the tulip.o that may have been built 
with your kernel first if you don't want to clobber it, but that tulip.o 
has never worked for me]
4. depmod -a
5. modprobe tulip
6. If all goes well you can try bringing up the interface.
7. And put alias eth<n> tulip in /etc/modules.conf for automation.

James Lamanna wrote:

> I'm using Kernel 2.2.17 and I've copied in the
> pci-scan.c, pci-scan.h, kern_compat.h, and tulip.c into the drivers/net
> directory in the kernel source tree.
> I've also changed the Makefile so that L_OBJS includes pci-scan.o
> However, when I do a make bzImage, everything works ok
> until I get to the linking stage where I receive these messages:
> drivers/net/net.a(tulip.o): In function `tulip_probe1':
> tulip.o(.text+0x3f): undefined reference to
> `pci_write_config_dword_Rf0fbd200'
> tulip.o(.text+0x6a): undefined reference to `printk_R1b7d4074'
> tulip.o(.text+0x83): undefined reference to `init_etherdev_R651e9648'
> tulip.o(.text+0x93): undefined reference to `kmalloc_R93d4cfe6'
> tulip.o(.text+0xee): undefined reference to
> `pci_read_config_byte_Re5ceea13'