- Jun 18, 2008
-
-
Zhenyu Wang authored
-
- Jun 17, 2008
-
-
Zhenyu Wang authored
(cherry picked from commit 289790c0)
-
- Jun 15, 2008
-
-
Lukas Hejtmanek authored
(cherry picked from commit 4c4ef277)
-
- Jun 12, 2008
-
-
Zhenyu Wang authored
-
This should improve behavior in the presence of VT switching, but also avoids a crash on X exit from writing the register after unmapping mmio.
-
fd.o #16160 (cherry picked from commit 231a3020)
-
Fxies FDO bug #14000; we need to wait for vblank after writing TV_CTL or followi ng "DPMS on" calls may not actually enable the output. (cherry picked from commit 1142be53)
-
Make sure we wait for vblank when using the TV DAC to detect the connection type. Fixes FDO bug #14000. (cherry picked from commit 64a8f243) (cherry picked from commit e4e61e8c97c585993b4b69b86350b3987178a47e)
-
(cherry picked from commit bff180e6)
-
The bit set is now reserved -- used to be a workaround for early revisions. (cherry picked from commit ad459b21)
-
-
We want these to always be set when our driver's in control. They are already appropriately save/restored at leave/entervt. (cherry picked from commit 8061e5ac)
-
(cherry picked from commit b61cb928)
-
(cherry picked from commit adb4f5a5)
-
(cherry picked from commit 7e51384c)
-
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. (cherry picked from commit 65306cdd)
-
Fix fd.o bug 15766 (cherry picked from commit beb72ae5)
-
Zhenyu Wang authored
Also safe check context size to not exceed surface max.
-
Zhenyu Wang authored
(cherry picked from commit 96955003)
-
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. (cherry picked from commit 89bb53cc)
-
Besides our driver having fallen through to the GM965 path for RENCLK_GATE_D1, the BIOS was turning some of these on. It may be relevant for previous platforms as well to zero out the fields that should be zero in the other registers. (cherry picked from commit 552a1b82)
-
(cherry picked from commit 165c0865)
-
- May 26, 2008
-
-
- May 20, 2008
-
-
Zhenyu Wang authored
This reverts commit 0c00a638. Those FIFO watermark regs are 945-ish, and cause problem on G35. (cherry picked from commit 740a73da)
-
- May 14, 2008
-
-
(cherry picked from commit e9532f3a)
-
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 5103e5a3)
-
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 18ef4158)
-
(cherry picked from commit 6366e4de)
-
- May 12, 2008
-
-
Zhenyu Wang authored
-
Zhenyu Wang authored
Seems not resolve the issue (fdo bug #15885). (cherry picked from commit f280c50d)
-
- May 10, 2008
-
-
Bryce Harrington authored
(cherry picked from commit d91d9e6a)
-
- May 09, 2008
-
-
The Intel xorg driver tries mightily to determine the native fixed panel mode settings for the LVDS output. It does this through various means, including scanning video BIOS tables, and noticing if the pipe in question has already been set up by somebody else (and adopting those timings). This strategy works well for say a laptop where the LCD panel is an integral part of the machine. But for other applications where the display is unrelated to the system's BIOS or other software, then the BIOS will likely have no clue how to configure the LVDS output. Worse still, the BIOS can simply "get it wrong", leaving the pipe misconfigured. Unfortunately the Intel driver can potentially notice this, adopt the same settings, leaving a messed up display. All of this complexity normally happens independently, behind the scenes, from the mode timings that might otherwise be specified by the user. This driver has a concept of fixed, i.e. "native" mode, and then user-specified mode. If the corresponding resolutions between those concepts don't match, then the driver in theory will arrange for scaling to take place while adhering to the actual native mode of the panel. Said another way, if the user says 800x600 but the driver mistakenly (see above) thinks the native mode is 640x480, then 640x480 is the mode set with scaling to an 800x600 frame buffer. If the driver gets the wrong native mode, then the result is a miserable mess with no way for the user to override what the driver thinks is right. This patch provides a means to override the driver. This implements a new driver option, "LVDSFixedMode" which defaults to true (the normal, probe-what-I-need behavior). However when set to false, then all the guessing is skipped and the driver will assume no fixed, i.e. "native" mode for the display device. Instead with this option set to false, the driver will directly set the timings specified by the user, providing an escape hatch for situations where the driver can't correctly figure out the right mode. Under most scenarios of course, this option should not be needed. But in situations where the Intel video BIOS is hopelessly fouled up related to the LVDS output, this option provides the escape hatch for the user to get a working display in spite of the BIOS situation. Signed-off-by: Mike Isely <isely@pobox.com> (cherry picked from commit 9f324860)
-
- May 08, 2008
-
-
There are lots of good reasons for doing this, one of them is fdo bug #11305. (cherry picked from commit 33f033cb)
-
Zhenyu Wang authored
(cherry picked from commit a7188b1f)
-
- May 07, 2008
-
-
The fix for flushing at blockhandler with no DRI on 965 was broken and would try to flush the chip even when the driver wasn't in control of the VT. Hilarity ensued. (cherry picked from commit 36ec9330)
-
(cherry picked from commit 0c00a638)
-
Zhenyu Wang authored
Don't check xvmc lib if user has already wanted to disable it. Fix fdo bug #15762. (cherry picked from commit c81a4687)
-
(cherry picked from commit be746a90)
-
Dell Latitude D500s seem to have this problem. At lid close/open, the DSPABASE reg gets reset to 0, so we either need to keep the framebuffer at offset 0 or make sure we reprogram the CRTCs after the lid opens again. Since we can't make sure the former is always true (buffer resize, etc.), this patch adds a quirk to reset the modes at lid open time. Fixes FDO bug #14890. (cherry picked from commit a0ced923)
-
This simply moves code from the driver up into the X server; use it where available. (cherry picked from commit fff17b9d)
-