From: Tim Hockin <thockin@sun.com>
To: jgarzik@mandrakesoft.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
alan@redhat.com, torvalds@transmeta.com
Subject: [PATCH] add pci ids
Date: Tue, 23 Oct 2001 16:54:06 -0700 [thread overview]
Message-ID: <3BD6031E.5A55DDD3@sun.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 192 bytes --]
Patch adds pci ids for Natsemi DP83820 and Netgear GA622. Please pop into
next 2.4.x.
Tim
--
Tim Hockin
Systems Software Engineer
Sun Microsystems, Cobalt Server Appliances
thockin@sun.com
[-- Attachment #2: pci_ids.diff --]
[-- Type: text/plain, Size: 1149 bytes --]
--- virgin-2.4.12/drivers/pci/pci.ids Wed Oct 10 14:37:15 2001
+++ CVS-checkout/drivers/pci/pci.ids Mon Oct 22 09:36:36 2001
@@ -268,6 +268,7 @@
0011 National PCI System I/O
0012 USB Controller
0020 DP83815
+ 0022 DP83820
d001 87410 IDE
100c Tseng Labs Inc
3202 ET4000/W32p rev A
@@ -3591,6 +3592,7 @@
1384 Reality Simulation Systems Inc
1385 Netgear
620a GA620
+ 622a GA622
f311 FA311
1386 Video Domain Technologies
1387 Systran Corp
--- virgin-2.4.12/include/linux/pci_ids.h Thu Oct 11 13:46:54 2001
+++ CVS-checkout/include/linux/pci_ids.h Tue Oct 23 16:45:44 2001
@@ -285,6 +285,8 @@
#define PCI_DEVICE_ID_NS_87415 0x0002
#define PCI_DEVICE_ID_NS_87560_LIO 0x000e
#define PCI_DEVICE_ID_NS_87560_USB 0x0012
+#define PCI_DEVICE_ID_NS_83815 0x0020
+#define PCI_DEVICE_ID_NS_83820 0x0022
#define PCI_DEVICE_ID_NS_87410 0xd001
#define PCI_VENDOR_ID_TSENG 0x100c
@@ -1382,6 +1384,7 @@
#define PCI_VENDOR_ID_NETGEAR 0x1385
#define PCI_DEVICE_ID_NETGEAR_GA620 0x620a
+#define PCI_DEVICE_ID_NETGEAR_GA622 0x622a
#define PCI_VENDOR_ID_APPLICOM 0x1389
#define PCI_DEVICE_ID_APPLICOM_PCIGENERIC 0x0001
next reply other threads:[~2001-10-23 23:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-23 23:54 Tim Hockin [this message]
2001-10-24 1:48 ` [PATCH] add pci ids Jeff Garzik
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=3BD6031E.5A55DDD3@sun.com \
--to=thockin@sun.com \
--cc=alan@redhat.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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