From: Burkhard K. <bu...@bu...> - 2000-09-27 07:00:25
|
David Paschal > Hi, Burkhard. > > > BTW: in ieee12844/Makefile.in the "cp" expression to move kernel > > modules to the appropriate location was commented out. Was this > > done for any particular purpose? I am asking because it meant > > that the modules had to be installed by hand. > That part is left over from the previous maintainers. The new > "make install" I added to the top-level directory doesn't even invoke > makefiles in subdirectories. By default, it installs the modules under > /usr/local/lib, which doesn't help make it accessible to modprobe. > Based on John Chmielewski's message from September 13, it sounds like it > could be moved to (or possibly symlinked in) /lib/modules/misc, but there's > still the problem that modprobe doesn't detect that ieee12844pp.o depends > on parport_probe, not just parport and parport_pc. My idea was to add a > dummy function in ieee12844pp.c which never got called but which made a > reference to a function in parport_probe (for example, parport_probe()). > Since you're working on this code at the moment could you try this out and > let me know if it fixes the problem (or I can try it myself later). parport_probe no longer exist in the 2.4 kernel, so there it will be some other candidate. This issue should be resolved with the use of the new parport_driver_register interface. So it will be a mixed (kernel version dependant) solution. Burkhard -- Burkhard Kohl bu...@bu... |