| commit | 4f0c8f43ee5e9e12ed36a5950e19cfe513669ae7 | |
| author | Alan Cox <alan@linux.jf.intel.com> | |
| Fri, 13 May 2011 10:08:26 +0000 (13 11:08 +0100) | ||
| committer | Greg Kroah-Hartman <gregkh@suse.de> | |
| Tue, 17 May 2011 18:37:56 +0000 (17 11:37 -0700) | ||
| tree | f2657d266415973cb4f8ddd22f9647f65e0ee653 | treesnapshot (tar.gz zip) |
| parent | 3a229fd54db17f39ce14348c9de898b3671771ca | commitdiff |
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 <alan@linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
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 <alan@linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
| drivers/staging/gma500/psb_fb.c | diffblobblamehistory |