summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorIlia Mirkin <imirkin@alum.mit.edu>2015-06-29 04:07:20 -0400
committerBen Skeggs <bskeggs@redhat.com>2015-07-27 18:35:21 +1000
commitf4ac86ca400e5f706d2bb0ddbace0992f4206360 (patch)
treec27208b1d0cd923289e3199365e09810d0f484c6
parentaf88c6e2dd6e07ffcdbd55c6b34043483dd270f0 (diff)
downloadnouveau-f4ac86ca400e5f706d2bb0ddbace0992f4206360.tar.gz
fbcon/nv11-: correctly account for ring space usage
The RING_SPACE macro accounts how much space is used up so it's important to ask it for the right amount. Incorrect accounting of this can cause page faults down the line as writes are attempted outside of the ring. Signed-off-by: Ilia Mirkin <imirkin@alum.mit.edu> Cc: stable@vger.kernel.org Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
-rw-r--r--drm/nouveau/nv04_fbcon.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drm/nouveau/nv04_fbcon.c b/drm/nouveau/nv04_fbcon.c
index 4ef602c54..495c57644 100644
--- a/drm/nouveau/nv04_fbcon.c
+++ b/drm/nouveau/nv04_fbcon.c
@@ -203,7 +203,7 @@ nv04_fbcon_accel_init(struct fb_info *info)
if (ret)
return ret;
- if (RING_SPACE(chan, 49)) {
+ if (RING_SPACE(chan, 49 + (device->info.chipset >= 0x11 ? 4 : 0))) {
nouveau_fbcon_gpu_lockup(info);
return 0;
}