From: davej@codemonkey.org.uk
To: jgarzik@pobox.com
Cc: linux-kernel@vger.kernel.org
Subject: extra dmfe ID.
Date: Mon, 24 Mar 2003 16:41:50 +0000 [thread overview]
Message-ID: <200303241642.h2OGg235008241@deviant.impure.org.uk> (raw)
Snarfed from Alans tree, and tested to work ok here
on a 1563.
diff -urpN --exclude-from=/home/davej/.exclude bk-linus/drivers/net/tulip/dmfe.c linux-2.5/drivers/net/tulip/dmfe.c
--- bk-linus/drivers/net/tulip/dmfe.c 2003-03-08 09:57:19.000000000 +0000
+++ linux-2.5/drivers/net/tulip/dmfe.c 2003-03-17 23:42:29.000000000 +0000
@@ -49,6 +49,10 @@
support. Updated PCI resource allocation. Do not
forget to unmap PCI mapped skbs.
+ Alan Cox <alan@redhat.com>
+ Added new PCI identifiers provided by Clear Zhang at ALi
+ for their 1563 ethernet device.
+
TODO
Implement pci_driver::suspend() and pci_driver::resume()
@@ -1975,6 +1979,7 @@ static struct pci_device_id dmfe_pci_tbl
{ 0x1282, 0x9102, PCI_ANY_ID, PCI_ANY_ID, 0, 0, PCI_DM9102_ID },
{ 0x1282, 0x9100, PCI_ANY_ID, PCI_ANY_ID, 0, 0, PCI_DM9100_ID },
{ 0x1282, 0x9009, PCI_ANY_ID, PCI_ANY_ID, 0, 0, PCI_DM9009_ID },
+ { 0x10B9, 0x5261, PCI_ANY_ID, PCI_ANY_ID, 0, 0, PCI_DM9102_ID },
{ 0, }
};
MODULE_DEVICE_TABLE(pci, dmfe_pci_tbl);
reply other threads:[~2003-03-24 16:51 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=200303241642.h2OGg235008241@deviant.impure.org.uk \
--to=davej@codemonkey.org.uk \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
/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®