Martin Spott wrote:
Unfortunately the result of the merge is less stable with FlightGear on my
Radeon7500 than 'xc-texmem-0-0-1-20030123-trunk-premerge' - it's quite as
stable (or unstable) as the 'trunk' itself.

Would it make sense to split the merge up into a set of patches ? This way I
could revert the merge in slices and look which one shows to be significant
for FlightGear ?
There have been rumblings on [EMAIL PROTECTED] about problems with Radeon in 4.2.99.4, but I didn't think that those problems had propogated into DRI CVS yet. That's a shame. :(

In the mean time, you ought to be able to revert back to texmem-0-0-1-20030123-trunk-premerge and update everything EXCEPT programs/Xserver/hw/xfree86/drivers/ati/. You may need to update radeon_regs.h in drivers/ati, but that should be the only file that you need. That should get you all the recent Mesa updates, the Radeon DRM updates, and a few minor fixes in the Radeon user-space driver. Please let me know what success / problems you have.

Until the Radeon driver issues are worked out in XFree86, I would recommend that most people stick with the premerge radeon_drv.o.



-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to