From: Andries Brouwer <aebr@win.tue.nl>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: Dave Jones <davej@suse.de>, Jens Axboe <axboe@suse.de>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Would the real 82801E_9 please stand up. (fwd)
Date: Tue, 11 Mar 2003 22:35:04 +0100 [thread overview]
Message-ID: <20030311213504.GA4550@win.tue.nl> (raw)
In-Reply-To: <20030311192945.GA16212@fs.tum.de>
On Tue, Mar 11, 2003 at 08:29:45PM +0100, Adrian Bunk wrote:
> The issue described in Dave's mail below is still present:
>
> 2.4.21-pre5-ac1:
> #define PCI_DEVICE_ID_INTEL_82801E_9 0x2459
> #define PCI_DEVICE_ID_INTEL_82801E_11 0x245B
>
>
> 2.5.64-ac3:
> #define PCI_DEVICE_ID_INTEL_82801E_9 0x245b
> #define PCI_DEVICE_ID_INTEL_82801E_11 PCI_DEVICE_ID_INTEL_82801E_9
The 82801E has seven device IDs:
B1:D8:F0 2459 Ethernet Controller 0
B1:D9:F0 245d Ethernet Controller 1
D30:F0 245e PCI Hub
D31:F0 2450 LPC I/F
D31:F1 245b IDE
D31:F2 2452 USB
D31:F3 2453 SMBus
Clearly, the 2.5.64 uses are for IDE and must be 0x245b.
PCI_DEVICE_ID_INTEL_82801E_9 does not occur in 2.5.64,
apart from its definition.
Conclusion: 2.4 is right.
--- /linux/2.5/linux-2.5.64/linux/include/linux/pci_ids.h Wed Mar 5 10:47:31 2003
+++ /linux/2.5/linux-2.5.64a/linux/include/linux/pci_ids.h Tue Mar 11 22:31:53 2003
@@ -1831,8 +1831,8 @@
#define PCI_DEVICE_ID_INTEL_82801E_0 0x2450
#define PCI_DEVICE_ID_INTEL_82801E_2 0x2452
#define PCI_DEVICE_ID_INTEL_82801E_3 0x2453
-#define PCI_DEVICE_ID_INTEL_82801E_9 0x245b
-#define PCI_DEVICE_ID_INTEL_82801E_11 PCI_DEVICE_ID_INTEL_82801E_9
+#define PCI_DEVICE_ID_INTEL_82801E_9 0x2459
+#define PCI_DEVICE_ID_INTEL_82801E_11 0x245b
#define PCI_DEVICE_ID_INTEL_82801E_13 0x245d
#define PCI_DEVICE_ID_INTEL_82801E_14 0x245e
#define PCI_DEVICE_ID_INTEL_82801CA_0 0x2480
Andries
prev parent reply other threads:[~2003-03-11 21:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-11 19:29 Adrian Bunk
2003-03-11 19:31 ` Jens Axboe
2003-03-11 21:35 ` Andries Brouwer [this message]
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=20030311213504.GA4550@win.tue.nl \
--to=aebr@win.tue.nl \
--cc=axboe@suse.de \
--cc=bunk@fs.tum.de \
--cc=davej@suse.de \
--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®