Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=5413
------- Additional Comments From [EMAIL PROTECTED] 2005-12-28 13:36 -------
Created an attachment (id=4176)
--> (https://bugs.freedesktop.org/attachment.cgi?id=4176&action=view)
drm part of radeon pci id patch
add ids for drm. I've changed the family enum to look more alike the ddx/dri
versions, which meant ditching the non-existant r250 and the rs250 which is too
similar to rs200 to warrant its own entry.
Some problems though:
drm will think r300 and r350 chips have hier-z buffer, which is not correct for
the 4-pipe versions (that is, they DO have hier-z buffer, but it's not working
correctly). Shouldn't be a problem however, since dri will tell if hier-z is
used or not too (and it isn't currently anyway) (the r4xx chips can use hier-z
even with disabled pixel quads).
BUT a problem may be that I have REMOVED some pci ids. There were ids only in
drm. Some only in dri. Some in both drm and dri but not ddx. Pretty much all
combinations imaginable, what a mess. I believe some of these ids were
secondary ids and thus rightfully removed. However, there are still more ids in
xorgs xf86PciInfo.h file than radeon ddx recognizes.
Here's the list of the ids which are not recognized by ddx (some were in
dri/drm before, but no longer):
#define PCI_CHIP_RV380_3151 0x3151
#define PCI_CHIP_RV380_3152 0x3152
#define PCI_CHIP_RV380_3153 0x3153
#define PCI_CHIP_RV380_3156 0x3156
#define PCI_CHIP_RV380_3E51 0x3E51
#define PCI_CHIP_RV380_3E52 0x3E52
#define PCI_CHIP_RV380_3E53 0x3E53
#define PCI_CHIP_RV380_3E56 0x3E56
#define PCI_CHIP_RV250_Id 0x4964
#define PCI_CHIP_RV250_Ie 0x4965
#define PCI_CHIP_RV250_Le 0x4C65
#define PCI_CHIP_RV250_Ln 0x4C6E
#define PCI_CHIP_R200_QI 0x5149
#define PCI_CHIP_R200_QJ 0x514A
#define PCI_CHIP_R200_QK 0x514B
#define PCI_CHIP_R200_QN 0x514E
#define PCI_CHIP_R200_QO 0x514F
#define PCI_CHIP_RV370_5461 0x5461
#define PCI_CHIP_RV370_5462 0x5462
#define PCI_CHIP_RV370_5463 0x5463
#define PCI_CHIP_RV370_5465 0x5465
#define PCI_CHIP_RV370_5466 0x5466
#define PCI_CHIP_RV370_5467 0x5467
#define PCI_CHIP_RS300_5836 0x5836
#define PCI_CHIP_RS300_5837 0x5837
#define PCI_CHIP_RV370_5B61 0x5B61
#define PCI_CHIP_RV370_5B63 0x5B63
#define PCI_CHIP_RV370_5B66 0x5B66
#define PCI_CHIP_RV370_5B67 0x5B67
Someone knows what's up with them? I.e. do these devices exist and if so,
what's their proper marketing name? If they exist they need to be added to ddx,
drm and dri obviously (I didn't touch ddx, I think rs400 should really get its
own family there too).
Also, at least one id (5d5d) seems to have a bogus name in the ddx
radeon_chipset.h file.
There are also ids in there which likely don't work. RS400 family for one, and
I'm not sure about the firemv2200 pci neither (it has strangely just one id,
I'd have guessed it would get two but apparently not - it should be just two
rv280 chips afaik or does it also need a pci-pci bridge or something?).
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
