On Wednesday 29 April 2009 05:49:31 Carl Worth wrote: > This is a development snapshot very early in the process toward > developing 2.8. There have been some big changes to the code, and > we're anxious to get feedback on these changes as early as possible. I tried this snapshot with KMS/DRI2 on GM965, kernel 2.6.30-rc4, xserver 1.6.1, mesa 7.4, libdrm 2.4.9. Redirecting output on VGA now seems to work, so I am closing bug #21250. With 2.7.0, I was also seing some corruption similar to that of bug #21415, especially after a couple of resume from STD. With 2.7.99.1 and after 3-4 resumes, there is no corruption at all. Maybe reporters of that bug may try the latest snapshot as well... Thanks, Stefano > > Here is a summary of the biggest changes: > > * Driver now depends on X server 1.6 or later > > * Eliminate XAA and EXA support (in favor of UXA) > > * Eliminate DRI1 support > > * Fixes for running without DRI at all > > These code removals represent a deletion of a substantial amount of > code, (and hopefully piles of bugs), as well as reduce the maintenance > effort going forward as the number of combinatorial configurations for > the driver are greatly reduced. This means that users are much more > likely to be running code that has actually been tested, and it will > be much easy for developers to replicate bugs that users experience. > > Many thanks to Eric Anholt for gutting so much code! And see Keith > Packard's writeup describing the benefits of this code removal: > > http://keithp.com/blogs/Sharpening_the_Intel_Driver_Focus/ > > One of the things that would be most useful in testing this release is > to revisit any outstanding bugs that you have previously reported. If > the buggy behavior is gone, (or the bug is no longer relevant---such > as a bug that's specific to XAA only), please feel free to indicate so > in bugzilla or even just close the bug. > > If you confirm that the bug is still present, please indicate so in > the bug report. (I was going to ask that you select a 1.7.99 version, > but it looks like bugzilla only has versions for products not > compoenents, while we use a "xorg" product and a "driver/intel" > component.) We definitely want to make any such confirmed bugs a > priority, so it would be nice to have a consistent mechanism to search > for these bugs. Suggestions are welcome on the best approach. > > Thanks in advance for any testing or feedback on this snapshot. > > -Carl > > Getting the snapshot > -------------------- > git tag: 2.7.99.1 > > http://xorg.freedesktop.org/archive/individual/driver/xf86-video-intel-2.7. >99.1.tar.bz2 MD5: ec222b8e617f79c3dee03db71db053a2 > xf86-video-intel-2.7.99.1.tar.bz2 SHA1: > c8c88d341dd79c4561018c5a279c8f6e66f84089 > xf86-video-intel-2.7.99.1.tar.bz2 > > http://xorg.freedesktop.org/archive/individual/driver/xf86-video-intel-2.7. >99.1.tar.gz MD5: 797eaa5d8abdabd92bdc261ca1b53634 > xf86-video-intel-2.7.99.1.tar.gz SHA1: > 5ee985ed22e483ac470cceaa65866a871370b747 > xf86-video-intel-2.7.99.1.tar.gz > _______________________________________________ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg