Dave Airlie wrote:
2. make ycbcr on r200 dependant on a new chipset flag.. if your chip has a
broken ycbcr (r200 and rv280 look fine so far..) then the flag needs to be
set for it...
I removed support for ycbcr some time ago on everything except r200
based on the assumption that it was just a feature removed (the only
results available were for r200, rv250 and M9). However, since it
apparently works on rv280 cards, it is probably just an asic bug, in
which case it likely works on everything but rv250/M9 (i.e. it should
work on r200, rv280/M9+, and igp9100).
That's at least how I've added that now to the unified driver
http://homepage.hispeed.ch/rscheidegger/dri_experimental/ati_radeon.tar.bz2,
which already has had all required pci id stuff...
It could still be some sort of initialization issue I guess (though I
wouldn't understand why rv280 and r200 would be identical, but not rv250).
Roland
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
