I'm not very surprised about the 3c59x driver not working, as I only
tested ne-pci. However, I hope that all the drivers can be made to
work by making small changes ...
> What am I doing wrong?
Nothing, probably. It's probably my fault.
> What's the syntax for network devices?
e.g. kernel= (nd)/export/bzImage
> Is it possible to specify the port?
Apparently not. Probably worth adding.
> How do I enable verbose diagnostic in 3c59x.c ?
I'll have to look ...
> Indeed, there are no traces of PCI_VENDOR_ID_VORTEX in the sources.
> It can be found in /usr/include/linux/pci.h
> /usr/local/src/grub/netboot/3c59x.c:467: undefined reference to `inl'
...
This is because the source previously depended on Linux header files.
I removed enough of the dependences to make ne-pci work, but neglected
the other drivers.
netboot/io.h contains extracts from Linux's include/asm-i386/io.h, but
see the comment about the order of the arguments being different for
the output functions. It looks like more of include/asm-i386/io.h
should be borried into netboot/io.h to get inl, etc.
I shall try later to see if I can successfully compile 3c59x.
Edmund
P.S. Prompted by Michael Hohmuth, I have been wondering whether it
might be better to use Linux's net drivers in GRUB instead of the
current ones, which come from a variety of other sources. If they
could be used with suitable glue code and without modifying the
drivers themselves we would have drivers that are well maintained.
OSKit shows how to reuse Linux drivers, and is GPL. OSKit uses 2.0.x,
though. I was thinking of gluing 2.2.x net drivers into GRUB. Does
this sound like a worthwhile thing to try?
Are there any other known recent cases of Linux net drivers being
reused? (I read about them being ported to L3, but that's not very
recent.) Does Mach use Linux network drivers, or just char ones?
