Jan Kiszka wrote:
Sebastian Smolorz wrote:
is anyone working on a rt_e100 driver? Maybe half-finished? If not I would probably start a port since we need such a driver soon.

Did you already tried to add the new PCI ID to the rt_eepro100? As RTnet
only needs basic support from the NIC, they might be hope to get along
with a cheap update of the existing code.

Yes, a one-liner indeed is a cheap solution. ;-)

You'll find the small patch attached.

Thanks.

--
Sebastian
Index: drivers/rt_eepro100.c
===================================================================
--- drivers/rt_eepro100.c       (Revision 1197)
+++ drivers/rt_eepro100.c       (Arbeitskopie)
@@ -1980,6 +1980,7 @@
        { PCI_VENDOR_ID_INTEL, 0x2449, PCI_ANY_ID, PCI_ANY_ID, },
        { PCI_VENDOR_ID_INTEL, 0x2459, PCI_ANY_ID, PCI_ANY_ID, },
        { PCI_VENDOR_ID_INTEL, 0x245D, PCI_ANY_ID, PCI_ANY_ID, },
+       { PCI_VENDOR_ID_INTEL, 0x27DC, PCI_ANY_ID, PCI_ANY_ID, },
        { PCI_VENDOR_ID_INTEL, 0x5200, PCI_ANY_ID, PCI_ANY_ID, },
        { PCI_VENDOR_ID_INTEL, 0x5201, PCI_ANY_ID, PCI_ANY_ID, },
        { 0,}
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
RTnet-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/rtnet-developers

Reply via email to