History log of /drivers/gpu/drm/gma500/framebuffer.h
Revision Date Author Comments
dffc9ceb55695f121adc57dd1fde7304c3afe81e 29-Nov-2011 Alan Cox <alan@linux.intel.com> 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>
4d8d096e9ae86621cc38b5417f4353305c5fd3a9 03-Nov-2011 Alan Cox <alan@linux.intel.com> gma500: introduce the framebuffer support code

We support 2D acceleration on some devices but we try and do tricks with
the GTT as a starting point as this is far faster. The GTT logic could be
improved further but for most display sizes it already makes a pretty good
decision.

Signed-off-by: Alan Cox <alan@linux.intel.com>
Signed-off-by: Dave Airlie <airlied@redhat.com>