From: Jon Smirl <jonsmirl@yahoo.com>
To: fb-devel <linux-fbdev-devel@lists.sourceforge.net>,
dri-devel <dri-devel@lists.sourceforge.net>
Subject: Linux kernel PCI IDs vs Xfree
Date: Sat, 9 Aug 2003 12:23:06 -0700 (PDT) [thread overview]
Message-ID: <20030809192306.10704.qmail@web14910.mail.yahoo.com> (raw)
linux/pci_ids.h and xf86PciInfo.h are in disagreement
for several Rage128 PCI ids. Xfree appears to be
correct and the kernel file is wrong. This impacts the
Rage framebuffer driver when loading. I verified these
with two PCI databases.
Rage Mobility 128 AGP 4x
#define PCI_CHIP_RAGE128MF 0x4D46
#define PCI_DEVICE_ID_ATI_RADEON_LF 0x4d46
Rage Mobility 128 AGP
#define PCI_CHIP_RAGE128ML 0x4D4C
missing
Rage 128 SE/4x PCI
#define PCI_CHIP_RAGE128SE 0x5345
#define PCI_DEVICE_ID_ATI_RAGE128_RM 0x5345
Rage 128 SF/4x AGP 2x
#define PCI_CHIP_RAGE128SF 0x5346
#define PCI_DEVICE_ID_ATI_RAGE128_RN 0x5346
Rage 128 SG/4x AGP 4x
#define PCI_CHIP_RAGE128SG 0x5347
#define PCI_DEVICE_ID_ATI_RAGE128_RO 0x5347
Rage 128 SH/4x
#define PCI_CHIP_RAGE128SH 0x5348
missing
Rage 128 SK/4x
#define PCI_CHIP_RAGE128SK 0x534B
#define PCI_DEVICE_ID_ATI_RAGE128_RG 0x534b
Rage 128 SL/4x AGP 2x
#define PCI_CHIP_RAGE128SL 0x534C
#define PCI_DEVICE_ID_ATI_RAGE128_RH 0x534c
Rage 128 SM/4x AGP 4x
#define PCI_CHIP_RAGE128SM 0x534D
#define PCI_DEVICE_ID_ATI_RAGE128_RI 0x534d
Rage 128 4x
#define PCI_CHIP_RAGE128SN 0x534E
missing
Rage 128 Pro Ultra TF
#define PCI_CHIP_RAGE128TF 0x5446
#define PCI_DEVICE_ID_ATI_RAGE128_U1 0x5446
Rage 128 Pro Ultra TL
#define PCI_CHIP_RAGE128TL 0x544C
#define PCI_DEVICE_ID_ATI_RAGE128_U2 0x544C
Rage 128 Pro Ultra TS
#define PCI_CHIP_RAGE128TS 0x5453
missing
Rage 128 Pro Ultra TT
#define PCI_CHIP_RAGE128TT 0x5454
missing
Rage 128 Pro Ultra TU
#define PCI_CHIP_RAGE128TU 0x5455
missing
=====
Jon Smirl
jonsmirl@yahoo.com
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
reply other threads:[~2003-08-09 19:23 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=20030809192306.10704.qmail@web14910.mail.yahoo.com \
--to=jonsmirl@yahoo.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).