- 26 Aug, 2010 4 commits
-
-
Francisco Jerez authored
This commit fixes fdo bug 29685. Reported-by:
Vlado Plaga <rechner@vlado-do.de> Signed-off-by:
Francisco Jerez <currojerez@riseup.net> Signed-off-by:
Ben Skeggs <bskeggs@redhat.com>
-
Patrice Mandin authored
Signed-off-by:
Patrice Mandin <patmandin@gmail.com> Reviewed-by:
-
Francisco Jerez authored
Signed-off-by:
-
Ben Skeggs authored
Signed-off-by:
-
- 17 Aug, 2010 11 commits
-
-
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Francisco Jerez authored
This should fix the reported TV-out load detection false positives (fdo bug 29455). Reported-by:
-
Francisco Jerez authored
The blob also thinks there's a TV connected, so hardware bug... Signed-off-by:
-
Ben Skeggs authored
Fixes an infinite loop that can happen in RAMHT lookup. Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
This message is apparently confusing people, and is being blamed for some modesetting issues. Lets remove the message, and instead replace it with an unconditional printout of the table revision. Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
When VRAM is running out it's possible that the client's push buffers get evicted to main memory. When they're validated back in, the GPU may be used for the copy back to VRAM, but the existing synchronisation code only deals with inter-channel sync, not sync between PFIFO and PGRAPH on the same channel. This leads to PFIFO fetching from command buffers that haven't quite been copied by PGRAPH yet. This patch marks push buffers as so, and forces any GPU-assisted buffer moves to be done on a different channel, which triggers the correct synchronisation to happen before we submit them. Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Francisco Jerez authored
Signed-off-by:
-
- 09 Aug, 2010 6 commits
-
-
Ben Skeggs authored
Signed-off-by: -
Francisco Jerez authored
Thinko caused by 43bda05428a3d2021f3c12220073e0251c65df8b. Signed-off-by: -
Francisco Jerez authored
Fixes a regression introduced by 58bbb63720c8997e0136fe1884101e7ca40d68fd (fdo bug 29324). Reported-by:
Johannes Obermayr <johannesobermayr@gmx.de> Signed-off-by:
-
Francisco Jerez authored
Signed-off-by:
-
Francisco Jerez authored
Signed-off-by:
-
Francisco Jerez authored
We need a valid OR value because there're a few nv17 cards with DCB v1.4. Signed-off-by:
-
- 05 Aug, 2010 19 commits
-
-
Ben Skeggs authored
There's some known configurations where the lack of these tables/scripts is perfectly normal, reduce visibilty of complaint messages to debug. Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Marcin Kościelnicki authored
Signed-off-by:
Marcin Kościelnicki <koriakin@0x04.net>
-
Marcin Kościelnicki authored
Signed-off-by:
-
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Francisco Jerez authored
Signed-off-by:
-
Francisco Jerez authored
Signed-off-by:
-
Francisco Jerez authored
sil164 and friends are the most common, usually they just need to be poked once because a fixed configuration is enough for any modes and clocks, so they worked without this patch if the BIOS had done a good job on POST. Display couldn't survive a suspend/resume cycle though. Unfortunately, BIOS scripts are useless here. Signed-off-by:
-
Francisco Jerez authored
Not very nice, but I don't think there's a simpler workaround. Signed-off-by:
-
Francisco Jerez authored
Leaving the IRQ unack'ed while switching contexts makes the switch fail randomly on some nv1x. Signed-off-by:
-
Francisco Jerez authored
Signed-off-by:
-
Francisco Jerez authored
Signed-off-by:
-
Dan Carpenter authored
nouveau_load() just returned directly if there was an error instead of releasing resources. Signed-off-by:
Dan Carpenter <error27@gmail.com> Reviewed-by:
Marcin Slusarz <marcin.slusarz@gmail.com> Signed-off-by:
-
Francisco Jerez authored
Previously nouveau_mem_reset_agp() was only disabling AGP fast writes when coming back from suspend. However, the "locked out of the card because of FW" problem can also be reproduced on init if you unload/reload nouveau.ko several times. This patch makes the AGP code reset FW on init. Signed-off-by:
-
