Highlights include glamor/maxwell/dri3 support, but it also fixes a screen corruption problem on my setup (randr+composite). Working fine here with current ~arch packages, though I did not try to enable glamor or other new features
Unfortunately xf86-video-nouveau-1.0.11 introduces an automagic dependency on xorg-server[glamor] which I want to address before adding this version to portage.
Is GLAMOR even optional? From what I have read on various websites it seems that with X.org 1.16 it's part of the server itself rather than an independent library and while I'm all for configurability and flexibility it seems that this time next year GLAMOR will likely be required for anything passing for at that time modern and current Linux graphical stack anyway, so as long as it does not break legacy hardware or add an unacceptable level of bloat for realistic use cases, I really don't think there's any need to spend more months on trying to get rid of GLAMOR.
(In reply to niks1024 from comment #2) > Is GLAMOR even optional? I haven't looked at nouveau but the bit that's probably bother Chí-Thanh is the "automagic" bit, not the dependency itself. If glamor is optional, we need to be able to control it. Either force it on, or off, or with a USE flag. > I really don't think there's any need to > spend more months on trying to get rid of GLAMOR. No one's trying to get rid of glamor. We're just trying to figure out the best way to package things properly.
In >=xorg-server-1.16, glamor is optional and configurable with USE="glamor". >=xf86-video-nouveau-1.0.11 autodetects whether the X server has glamor enabled and if so, enables it for nouveau too. This is the automagic part. Per http://wiki.gentoo.org/wiki/Project:Quality_Assurance/Automagic_dependencies this either needs to be made configurable or a hard dependency on xorg-server[glamor] be added. The former is on my TODO list, the latter is not a good idea I think.
But does it make sense to build X11 without GLAMOR if it's available? Can it break some setups? Cause incompatibilities? And would they realistically be encountered by some using nouveau? There's countless switches for every package that are not exposed via their own USE flag because there's no practical reason to have tens or hundreds of switches for everything. And it seems that for now GLAMOR is going that way, that it's how things will be done both in post-1.16 X11 and Xwayland or whatever the Wayland X11 compatibility layer was called, so in my opinion making it optional makes sense only if enabling GLAMOR breaks a use case or adds an unacceptable level of bloat. Doubly so when making xorg-server[glamor] optional has delayed 1.0.11 for over a month already.
1.0.11 is now in CVS. Patch to make building of glamor optional sent upstream: http://lists.freedesktop.org/archives/nouveau/2014-October/018987.html
