On Sat, Aug 09, 2003 at 10:41:01PM +0200, Alexander Stohr wrote:
> Which ones? e.g. www.yourvote.com\pci is the database
> where the Linux kernel does get its listing.
wrong. it occasionally gets merges from http://pciids.sf.net,
though IDs also get added directly to the kernel tree without
bein
What do you think about the attached patch?
I removed this, it just looks wrong and it conflicts
with Rage128
- /* Radeon M4 */
-#define PCI_DEVICE_ID_ATI_RADEON_LE0x4d45
-#define PCI_DEVICE_ID_ATI_RADEON_LF0x4d46
Radeonfb wasn't using them anyway.
Updated pci_ids.h to reflect all of the
All of the Rage128 and Radeon IDs I am refering to in
my posts are already in http://pciids.sf.net. These
IDs are missing in various combinations from the linux
and xfree header files. I usually have to also update
the framebuffer drivers to handle the added IDs.
=
Jon Smirl
[EMAIL PROTECTED]
all info contained below is my personal opinion,
should be retriveable from several pbulic sources
and it is only accurate to my best knowledge.
> 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 i
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
