changes from later intel versions (after the UMS removal). 95% of this
is the xvmc reworks that makes that code even halfway sane. xvmc is now
enabled by default on 965+.
Tested by many on tech@, thanks!
ok matthieu@
While this feature at best can save 05w idle power, it is very flakey. Disabling
it fixes (or at the least masks) the problem that some 915 and 945 users were
seeing where they ended up with a blank screen (it turns out that no problems
fired because everything was still working, just FBC screwed up and never
actually scanned out the framebuffer).
As some examples for reliability linux with kms has disabled fbc on these
chipsets due to some unreliability issues (especially over suspend). and the
window driver apparently also does not used it.
Tested by kettenis@, Tom Murphy, edd@ and myself.
ok matthieu@
These files were missing from the last commit. (due to shuffling the cvs
diff between old driver and new one was 155246 lines, so two files isn't
that bad...)
2.9.1 is the last version of the intel DDX that supports UMS (User
modesetting), with 2.10 onwards being purely KMS only. As such, this
driver contains backports of almost every correctness or performance
related fix to the rendering layer in later intel drivers. This driver
*REQUIRES* a GEM enabled kernel. it claims to support non-gem mode but
this is essentially unmaintained and due to the way the abstraciton
works is slow, if it works at all (it often does not). You have been
warned.
tested by many many people on tech over the last few weeks.
driver idles the ringbuffer, stops it, unbinds all memory, then hands
back off.
Now here's the clever bit: just before we call to idle the ringbuffer
(which sleeps waiting for an interrupt) let's TURN OFF THE FUCKING
INTERRUPT. That's a great idea, really, isn't it?
Move the interrupt disable to *after* stop_ring. Theo's T61 VT switches
again. everyone elses' intel stuff worked by magic (or shared
interrupts) before now.
Fixed after discussion with deraadt@, thanks to miod for suggestions.
ok matthieu@
Original commit message from barry scott to upstream:
Author: Barry Scott <barry.scott@onelan.co.uk>
Date: Tue Jun 23 14:14:50 2009 +0100
Fix segv for clipped movie window
When playing a movie that is clipped on its left and right edges the
Xorg server will SEGV sometimes. This is because the intel driver
ignores the clipping info when it copies the planes out of the XV
data. The check for the optimised copy was wrong to ignore the
width required. Which leads to too much data being copied by the
memcpy. It the source buffe happens to end exactly on a page
boundary the server will SEGV.
As we reviewed the code we checked the calculation of src1, src2 and
src3. The patch includes additional comments to make it clear what
the elements of the calculation are.
This bug exists in git head and we also see it in 2.4.1.
both XkbOptions and XkbVariant. now we can understand the .dvorak,
.nodeadkeys and .swapctrlcaps wscons variants and pass them correctly onto XKB.
Means that xmodmap or setxkbmap magic isn't needed in those cases
anymore.
"no objections" matthieu@. Diff from Tobias Ulmer (tobiasu at tmux dot
org); thanks!
