| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
The bit set is now reserved -- used to be a workaround for early revisions.
|
|
|
|
We want these to always be set when our driver's in control. They are
already appropriately save/restored at leave/entervt.
|
|
|
|
|
|
|
|
|
|
|
|
Besides not being #ifdef __linux__ed as requested, some linux kernels break
in exciting new ways when you try to mprotect from PROT_NONE back to
PROT_READ|PROT_WRITE. Yes, there are bugs in the code we're calling in a
bug-exploiting bug workaround.
If you want this workaround for the original bug exposed when moving to
libpciaccess, it's already in libpciaccess.
|
|
Fix fd.o bug 15766
|
|
From the spec, only 965GM and IGD_GM have 128 FIFO entries.
With DSPARB change introduced by commit bd137a, I've got PIPE B
underrun when dual-headed on G35 platform.
|
|
|
|
|
|
Also safe check context size to not exceed surface max.
|
|
|
|
"3.0 (quilt)" source package.
Thanks to Raphael Hertzog.
See http://lists.debian.org/debian-x/2008/05/msg01250.html for details.
|
|
Policy 3.7.3 allows /bin/sh scripts to use 'local'.
|
|
This variant of remove_conffile_prepare looks for the given conffile's
canonical md5sum in dpkg's status database itself instead of using
provided values.
|
|
It turns out 855 has a different DSPARB layout than 915+. And 945+ have more
FIFO entries, so we have to allocate things differently. So on 855 split the
FIFO evenly again between A & B planes, and do the same on 945, where we have a
larger FIFO. Fixes an issue reported by Daniel Stone with the previous default
value.
|
|
|
|
What I originally checked in was a bit misleading.
|
|
Add some debug code to catch FIFO underruns, which are normally bugs (unless
they occur during mode setting) and remove any plane C FIFO allocations, since
we don't use that plane at all. We may eventually need to be a little smarter
about this on platforms that use plane C for the popup.
|
|
Update clock gating disable bits to match docs and allocate a power context
memory area so that newer chips can save state and power down the render unit.
|
|
|
|
|
|
|
|
|
|
This reverts commit 53e3693ef13f31f3fc33bcff7286ab2b03b2d430.
Conflicts:
src/i830_driver.c - default FBC on for 965+
|
|
This reverts commit 0c00a638ef57aa9d6a3047176b0bfad733f781f0.
Those FIFO watermark regs are 945-ish, and cause problem
on G35.
(cherry picked from commit 740a73dad1d9a9b0ebf1cc7d6f2a056abad57aaf)
|
|
This reverts commit 0c00a638ef57aa9d6a3047176b0bfad733f781f0.
Those FIFO watermark regs are 945-ish, and cause problem
on G35.
|
|
|
|
|
|
(cherry picked from commit e9532f3abf1e0b62b2569d4aae60a5a63add571f)
|
|
In full_aspect mode, we try to preserve the aspect ratio by adding
either top & bottom or left & right borders. In the letterbox case (top
& bottom borders) we were miscalculating the top border which led to
programming a bad mode. Fix the calculation and bug #15559.
(cherry picked from commit 5103e5a39a4869a714b8a59da8bf51ecc8c65e4f)
|
|
The XVMC code uses a magic FOURCC code to signal frame updates, but that
code is only defined when the XVMC code is used.
(cherry picked from commit 18ef4158e5574bfc6621b268821532f13e261d13)
|
|
(cherry picked from commit 6366e4de540c4713cbc8402c89516464bbdc35b9)
|
|
|
|
|
|
|
|
allocate → create
unreference → close
name → flink
|
|
GEM needs memory alignment requirements sent at pin time, which is a bit
after the allocation itself. Store the required alignment in the memory
object for later use by pin.
|
|
In full_aspect mode, we try to preserve the aspect ratio by adding
either top & bottom or left & right borders. In the letterbox case (top
& bottom borders) we were miscalculating the top border which led to
programming a bad mode. Fix the calculation and bug #15559.
|
|
|
|
|
|
|
|
Seems not resolve the issue (fdo bug #15885).
(cherry picked from commit f280c50dd5d29c5717adc6da2368363cb3d0adbb)
|
|
Seems not resolve the issue (fdo bug #15885).
|
|
(cherry picked from commit d91d9e6a2f2ba18b35cb6fd7bc3fe8bc617eb44f)
|
