From: <bug...@fr...> - 2005-12-29 03:51:09
|
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 ag...@ya... 2005-12-29 14:45 ------- (In reply to comment #7) > (In reply to comment #6) > > I'm a bit worried about adding all IDs from the DDX to the DRM/Mesa as the 3D > > isn't reported stable on all the combinations especially with 64-bit things... > > > > I'd prefer to add them on a it works for me basis, and even that isn't probably > > that great.. maybe we shouldn't be enabling DRI on r300 by default... > The point of the patch isn't so much about adding ids only, but to make it more > conistent too. It's a bit messy currently with the 3 distinct sets of ids of > ddx, drm and dri (though it makes sense if ddx supports a superset). Also, I'm > not sure I agree about "adding 1 by 1", with 133 (in ddx) devices you're bound > to have some which are very rare (for instance some firegl cards). Personally I > think all chips from a family should be added or not, except probably some > "special" ones (very few of these exist afaik, like the multi-chip rv280). There > is absolutely no reason some X600 card is listed there but some other (maybe > X600Pro) is not imho (though you might want to enable or not based on the > interface, i.e. agp or pci-e too). I have to agree with Roland. More bugs get shaken out when it's easier to test. Adding them one by one will probably leave out a lot of potentially supported cards and users will just think that their card is only supported by fglrx. besides, r300 DRI isn't yet supported in any "official" xorg release yet anyway. Other than the XPRESS chips, most other r3xx and r4xx chips seem to work pretty well. -- 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. |