There are quite a few small fixes (even a new driver drop) for some of the drivers (including some I've written) floating around on xfree86 bugzilla. For the most part they aren't critical for this upcoming release. I just putting this bug here as a place holder. I'll gather the patches and post them here for review and integration at some point unless someone has a better plan.
Alex, could you please add links to the entires in the XFree86 bugzilla? That would make it easier to do this. If you wnat to you can also do this yourself. If you are not sure please ask someone to take a quick look.
that's what I was planning to do.
possible patches - none of these are critical as far as I know. I also make no claim that all these patchs are 100% correct. HW cursor probs in I810 http://bugs.xfree86.org/show_bug.cgi?id=2 radeon Power management support http://bugs.xfree86.org/show_bug.cgi?id=96 PCIDATA creates false video cards http://bugs.xfree86.org/show_bug.cgi?id=604 Fix for LCDs on PPC laptops with radeon M10 http://bugs.xfree86.org/show_bug.cgi?id=798 New Driver: SMI 501 http://bugs.xfree86.org/show_bug.cgi?id=1001 Keyboard LEDs and VT switches http://bugs.xfree86.org/show_bug.cgi?id=963 Driver for linux joysticks http://bugs.xfree86.org/show_bug.cgi?id=1003 multimedia keyboard print key needs it's own symbol http://bugs.xfree86.org/show_bug.cgi?id=1027 xman cannot display SGML man pages on Solaris http://bugs.xfree86.org/show_bug.cgi?id=1030 Additional features for TWM http://bugs.xfree86.org/show_bug.cgi?id=1124 Better memory allocation for dualhead radeons http://bugs.xfree86.org/show_bug.cgi?id=1149 xev should handle WM_DELETE_WINDOW http://bugs.xfree86.org/show_bug.cgi?id=1154 Keymapping for MS natural USB keyboard http://bugs.xfree86.org/show_bug.cgi?id=1155 Older neomagic chips also support XV http://bugs.xfree86.org/show_bug.cgi?id=1161 New feature, single button double-click http://bugs.xfree86.org/show_bug.cgi?id=1184 Middle button mouse scrolling (Mathias Fröhlich) http://www.mail-archive.com/devel@xfree86.org/msg03333.html turn off backlight for nv driver on Dell D800 http://bugs.xfree86.org/show_bug.cgi?id=1196 incorrect memory region in M2B macro http://bugs.xfree86.org/show_bug.cgi?id=1220 Enhanced symbols file for new keyboard http://bugs.xfree86.org/show_bug.cgi?id=1227 missing bus to host address translations for PPC/Linux http://bugs.xfree86.org/show_bug.cgi?id=1229 DRM_CAS in xf86drm.h generates lots of warnings http://bugs.xfree86.org/show_bug.cgi?id=1232 turn off DAC with dpms for radeons http://bugs.xfree86.org/show_bug.cgi?id=1221 Gamma correction for radeon Xv (Alex Deucher) http://www.botchco.com/alex/radeon/Xv/xv_gamma/radeon_video_gamma.diff Alpha blending support for radeon Xv (Alex Deucher) http://www.botchco.com/alex/radeon/Xv/xv_alpha/radeon_xvalpha.diff IBM 526 DAC support for s3 driver (John Hay) http://marc.theaimsgroup.com/?l=xfree86-devel&m=107843043004076&w=2
It might be useful to use this bug report as a master tracker for each of the issues included above, and file individual reports for each issue, so they can be closed one at a time once they're reviewed and/or fixed. That would also take a bit of time, so I can understand if someone would be too busy to do so right away however. Adding myself to CC list, to monitor. If I investigate any of the issues myself, I'll file a new report for each and mark it as blocking this one. Thanks for reporting these Alex!
new one: Add interlaced support to S3 driver http://bugs.xfree86.org/show_bug.cgi?id=1254
Some of these may be interesting for the RELEASE.
FWIW, there are also quite a few new features in the DRI tree that could be merged in at some point. off the top of my head: - mergedfb support for radeon - dri-interface changes - configuration infrastructure - new 3d features - fbconfig support
The problem with having 40 bug reports all in one bug report, is that you can't fix "just one issue" and then close the bug "FIXED", because there are 39 other problems still open. That makes it difficult to impossible for anyone reading the report to know which of the 40 bugs reported all in one report have been fixed and are closed, or are still open. Even if one updated the comments one at a time as they were investigated, you end up with a very very long single bug report and have to manually parse the whole report to figure out which bugs are fixed/open/etc. There is no per-issue tracking. I think many of the issues look interesting for consideration once the first release is out the door, but no new features should be added IMHO unless it is very very small, and very obvious that there is no regression risk. I've changed the summary to add the word [Tracker], so that when individual bug reports get filed later on for the above, they can block this tracker. Individual reports can be considered to block bug 213 also. Hope this helps.
If I have time next week I'll break this into separate bugs. My only hesitation was that most of these are already xfree86 bug reports so I feel like it's just duplicating work, but I guess we are dealing with separate trees...
Alex, Please break these up into separate bugs, so we can can track them and keep track of which go into the first release branch, and which go into the current branch.
OK, I've separated them. Please don't add any more to this bug. Create seperate ones and let them block this one.
Is this tracker still relevant? IMHO, the bugs blocking this should be removed and this closed, or alternatively the bugs blocking this should be added to the official 7.0 release tracker/blocker bug.
Ping on answer to mharris's request
Sorry about the phenomenal bug spam, guys. Adding xorg-team@ to the QA contact so bugs don't get lost in future.
Closing.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.