From: Ed Vance <EdV@macrolink.com>
To: "'Alan Cox'" <alan@lxorguk.ukuu.org.uk>,
"'Jeff Garzik'" <jgarzik@mandrakesoft.com>
Cc: "'Russell King'" <rmk@arm.linux.org.uk>,
"'linux-kernel'" <linux-kernel@vger.kernel.org>
Subject: [PATCH] PCI device ID Oxford 952 UART
Date: Fri, 15 Feb 2002 15:25:21 -0800 [thread overview]
Message-ID: <11E89240C407D311958800A0C9ACF7D13A76A0@EXCHANGE> (raw)
This patch corrects PCI device id in pci_ids.h for Oxford Semi OX16PCI952
PCI/dual 16950 UART chip, and adds this entry to pci.ids. I downloaded the
datasheet today and verified that 9521 is the correct device id.
Generated for 2.4.18-rc1, should also be applied to 2.5.
Thanks in
Ed Vance
diff -urN -X dontdiff.txt linux-2.4.18-rc1/drivers/pci/pci.ids
rc1-ml/drivers/pci/pci.ids
--- linux-2.4.18-rc1/drivers/pci/pci.ids Fri Feb 15 14:24:19 2002
+++ rc1-ml/drivers/pci/pci.ids Fri Feb 15 14:49:07 2002
@@ -3952,6 +3952,7 @@
1413 Addonics
1414 Microsoft Corporation
1415 Oxford Semiconductor Ltd
+ 9521 Oxford Semi OX16PCI952 PCI/dual 16950 UART
1416 Multiwave Innovation pte Ltd
1417 Convergenet Technologies Inc
1418 Kyushu electronics systems Inc
diff -urN -X dontdiff.txt linux-2.4.18-rc1/include/linux/pci_ids.h
rc1-ml/include/linux/pci_ids.h
--- linux-2.4.18-rc1/include/linux/pci_ids.h Fri Feb 15 14:24:27 2002
+++ rc1-ml/include/linux/pci_ids.h Fri Feb 15 14:51:35 2002
@@ -1474,9 +1474,9 @@
#define PCI_VENDOR_ID_OXSEMI 0x1415
#define PCI_DEVICE_ID_OXSEMI_12PCI840 0x8403
#define PCI_DEVICE_ID_OXSEMI_16PCI954 0x9501
-#define PCI_DEVICE_ID_OXSEMI_16PCI952 0x950A
#define PCI_DEVICE_ID_OXSEMI_16PCI95N 0x9511
#define PCI_DEVICE_ID_OXSEMI_16PCI954PP 0x9513
+#define PCI_DEVICE_ID_OXSEMI_16PCI952 0x9521
#define PCI_VENDOR_ID_AIRONET 0x14b9
#define PCI_DEVICE_ID_AIRONET_4800_1 0x0001
----------------------------------------------------------------
Ed Vance edv@macrolink.com
Macrolink, Inc. 1500 N. Kellogg Dr Anaheim, CA 92807
PH 714.777.8800 x335 Fax 714.777.8807 http://www.macrolink.com
----------------------------------------------------------------
reply other threads:[~2002-02-15 23:24 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=11E89240C407D311958800A0C9ACF7D13A76A0@EXCHANGE \
--to=edv@macrolink.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).