summaryrefslogtreecommitdiff
path: root/drivers/gpu/drm/gma500/framebuffer.h
diff options
context:
space:
mode:
authorAlan Cox <alan@linux.intel.com>2011-11-30 02:19:47 +0400
committerDave Airlie <airlied@redhat.com>2011-12-06 13:55:29 +0400
commitdffc9ceb55695f121adc57dd1fde7304c3afe81e (patch)
treeb1457b5299c08ad2a03e9da4f38743f2fbcb7556 /drivers/gpu/drm/gma500/framebuffer.h
parent838fa588a29331da012876623c3bc170d7d647c2 (diff)
downloadlinux-dffc9ceb55695f121adc57dd1fde7304c3afe81e.tar.xz
gma500: kill virtual mapping support
This isn't actually usable - we simply don't have the vmap space on a 32bit system to do this stunt. Instead we will rely on the low level drivers limiting the console resolution as before. The real fix is for someone to write a page table aware version of the framebuffer console blit functions. Good university student project perhaps.. Signed-off-by: Alan Cox <alan@linux.intel.com> Signed-off-by: Dave Airlie <airlied@redhat.com>
Diffstat (limited to 'drivers/gpu/drm/gma500/framebuffer.h')
-rw-r--r--drivers/gpu/drm/gma500/framebuffer.h1
1 files changed, 0 insertions, 1 deletions
diff --git a/drivers/gpu/drm/gma500/framebuffer.h b/drivers/gpu/drm/gma500/framebuffer.h
index d1b2289447f0..989558a9e6ee 100644
--- a/drivers/gpu/drm/gma500/framebuffer.h
+++ b/drivers/gpu/drm/gma500/framebuffer.h
@@ -32,7 +32,6 @@ struct psb_framebuffer {
struct address_space *addr_space;
struct fb_info *fbdev;
struct gtt_range *gtt;
- bool vm_map; /* True if we must undo a vm_map_ram */
};
struct psb_fbdev {