From: Tom Alsberg <alsbergt@cs.huji.ac.il>
To: "Andrey V. Savochkin" <saw@saw.sw.com.sg>
Cc: Linux-Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: PCI ID Patch for Intel Ether Express Pro 100 VE (82801BA)
Date: Sat, 14 Jun 2003 15:09:38 +0300 [thread overview]
Message-ID: <20030614120938.GA1058@cs.huji.ac.il> (raw)
Hi there.
We got a new machine here a few days ago - an Intel ICH D865 PERL
board based Pentium IV machine, with an on-board Intel EtherExpress
Pro 100 VE.
After Linux was installed on it, I was called to see why the network
adapter does not work. The module was not loaded automatically (it
was Red Hat something - don't remember, don't use it normally, but it
has some sort of hardware detection), and loading the eepro100
modules failed (no such device).
After a few minutes, I traced it to the PCI ID (8086:1050) not being
in the module's table (new chip or something, apparently). Having
added it, it seems to work.
Following is a trivial patch for it:
<patch>
--- drivers/net/eepro100.c.orig Sat Jun 14 14:51:26 2003
+++ drivers/net/eepro100.c Sat Jun 14 14:51:08 2003
@@ -2392,6 +2392,7 @@
{ PCI_VENDOR_ID_INTEL, 0x103C, PCI_ANY_ID, PCI_ANY_ID, },
{ PCI_VENDOR_ID_INTEL, 0x103D, PCI_ANY_ID, PCI_ANY_ID, },
{ PCI_VENDOR_ID_INTEL, 0x103E, PCI_ANY_ID, PCI_ANY_ID, },
+ { PCI_VENDOR_ID_INTEL, 0x1050, PCI_ANY_ID, PCI_ANY_ID, },
{ PCI_VENDOR_ID_INTEL, 0x1059, PCI_ANY_ID, PCI_ANY_ID, },
{ PCI_VENDOR_ID_INTEL, 0x1227, PCI_ANY_ID, PCI_ANY_ID, },
{ PCI_VENDOR_ID_INTEL, 0x1228, PCI_ANY_ID, PCI_ANY_ID, },
</patch>
I am not sure how reliable it is, and whther other modifications
should be made, but it worked fine for now.
I tried the alternative e100 driver - didn't originally work as well,
but I did not bother to try patching it too.
Anyway, I would like it to be added to the driver, so that new
machines with that adapter will work out of the box.
Thanks,
-- Tom
--
Tom Alsberg - hacker (being the best description fitting this space)
Web page: http://www.cs.huji.ac.il/~alsbergt/
DISCLAIMER: The above message does not even necessarily represent what
my fingers have typed on the keyboard, save anything further.
reply other threads:[~2003-06-14 11:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030614120938.GA1058@cs.huji.ac.il \
--to=alsbergt@cs.huji.ac.il \
--cc=linux-kernel@vger.kernel.org \
--cc=saw@saw.sw.com.sg \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®