[epic] Re: epic100.c fix for 2.2.x kernels
Thu, 06 Jul 2000 19:44:29 +0200 (MEST)
got that, I was missing pci-scan.c - I was already guessing by source reading
with the required headers and missed this source completely (lack of at least
hints on the driver's web page). Nevertheless the problem in the source remains
(I just did a quick source code read of the affected routines), so the fix I
posted is still required.
Now, what I don't like is that except for a (temporary) test machine that will
become a future server all of my servers run with module support disabled -
first the hardware doesn't change and second there's security reasons. So using
this new version of the driver I'll have either to modify the kernel's network
driver build or (single source version) include pci-scan.c in epic100.c (brrr,
On 06-Jul-2000 Jeff Garzik wrote:
> On Thu, 6 Jul 2000, Andreas Steinmetz wrote:
>> Not exactly:
>> You can compile the module - that's it. There's calls to pci_drv_register()
>> pci_drv_unregister that are not part of the 2.2.x kernels. Thus you're stuck
>> with unresolved symbols and an unloadable module.
>> Reworking this would mean to reimplement the 2.2.x semantics which would
>> basically result in a new driver version.
> You will not find these symbols in 2.3.x/2.4.x kernels either.
> You are missing Donald's pci-scan module. You must compile and build the
> driver AND the pci-scan module, install, and then insmod both of them,
> or "depmod -a ; modprobe <eth driver>"
> It would be nice if Donald would do something like the following in each
> of this independent drivers. This would reduce the FAQs and problem
> reports to nil...
>#ifndef PCI_SCAN_MODULE /* any symbol unique to pci-scan.h */
>#error You must also download pci-scan.c, pci-scan.h, and kern_compat.h
> Granted the compile will bomb out without these, but the missing headers
> lead people (such as the poster above) to believe that the drivers will
> not work under 2.2.x kernels.
D.O.M. Datenverarbeitung GmbH