Re: [2.2.0-pre4 and earlier] 8390 module dependencies
Alan Cox (alan@lxorguk.ukuu.org.uk)
Sun, 3 Jan 1999 22:45:54 +0000 (GMT)
> It is impossible to compile a network device driver which uses code from
> 8390.c into the kernel and another one as a module, because the 8390
> module isn't built and installed then (but required by the modularized
> driver). For example, building ne2k-pci into the kernel and ne as a
> module doesn't work.
> Perhaps this should be documented somewhere, or caught by configure
> process.
What should (and as far as I can tell) does happen is that building an
8390 driver into the kernel puts the 8390.o into the kernel and exports
the symbols for it - allowing modules like ne2k-pci.o to load just fine.
What specific .config causes a problem and what specific errors
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/