From 4f0c8f43ee5e9e12ed36a5950e19cfe513669ae7 Mon Sep 17 00:00:00 2001 From: Alan Cox Date: Fri, 13 May 2011 11:08:26 +0100 Subject: [PATCH] gma500: Don't try and take a GEM handle of a non GEM fb The initial GMA500 framebuffer is not GEM but stolen memory. We can't therefore take a GEM handle of it. Stop anyone trying to do this and causing a crash. Ideally we need a way to have GEM handles to non GEM objects but it's not clear how and if GEM and the modesetting/fb interfaces it provides are supposed to or indeed if they can handle it. Signed-off-by: Alan Cox Signed-off-by: Greg Kroah-Hartman --- drivers/staging/gma500/psb_fb.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/staging/gma500/psb_fb.c b/drivers/staging/gma500/psb_fb.c index ae097cd883f..99c03a2e06b 100644 --- a/drivers/staging/gma500/psb_fb.c +++ b/drivers/staging/gma500/psb_fb.c @@ -648,6 +648,8 @@ static int psb_user_framebuffer_create_handle(struct drm_framebuffer *fb, { struct psb_framebuffer *psbfb = to_psb_fb(fb); struct gtt_range *r = psbfb->gtt; + if (r->stolen) + return -EOPNOTSUPP; return drm_gem_handle_create(file_priv, &r->gem, handle); } -- 2.11.4.GIT