On Mon, Feb 27, 2006 at 07:11:34AM -0500, Mike A. Harris wrote: > My current plan for the r300 dri driver, is to leave it out of FC5, and > once the various issues are resolved upstream we will re-enable it in > rawhide post-FC5. This will allow the driver to get the level of > testing that is needed, and hopefully to stabilize sooner. Then, once > the major problems are resolved upstream by X.Org/DRI developers, and > new upstream stable packages have been released with the fixes, we will > probably include them in rawhide. Sounds decent. I'd be extremely reluctant to update FC5 to something that's only in CVS. The only reason for suggesting it is that it seemed like you were saying that some people were seeing lockups even with the r300 dri driver from Mesa not even present on their system. Maybe I misread it, but if it turns out that there's no other way to prevent hangs on r300-based cards then the CVS patches should perhaps be considered. Note that some of the bug reports claim that even without DRI lockups occur from using the framebuffer device, and that a lot of the patches apply to the main radeon X driver rather than dri. I don't know if removing the dri driver is enough to fix it. Hopefully so. John Thacker
Attachment:
pgpOtBhvkDuFw.pgp
Description: PGP signature
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
