> 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.
I can't comment on that combination, but have been using the reverse
(ne built in and ne2k-pci as a module) for some time without problems.
Are you sure you're not suffering from the fact that ne as a module
lacks some of the functionality it has when it's built in?
> Perhaps this should be documented somewhere, or caught by configure
> process.
If it's true, it needs to be documented...
Best wishes from Riley.
--- * ftp://ps.cus.umist.ac.uk/pub/rhw/Linux * http://ps.cus.umist.ac.uk/~rhw/kernel.versions.html
- 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/