gma500: begin adding GEM
authorAlan Cox <alan@linux.jf.intel.com>
Tue, 19 Apr 2011 14:27:28 +0000 (15:27 +0100)
committerGreg Kroah-Hartman <gregkh@suse.de>
Tue, 26 Apr 2011 00:13:48 +0000 (17:13 -0700)
commitf20ee24445b54be28cae8609c4194fb400377c63
tree0fbd997ce4ccedf161930151d6b1d264160959ce
parentf11dd9b14f48941ca4282174a282ee4f17ded530
gma500: begin adding GEM

This puts in place the infrastructure for GEM allocators. Our implementation
is fairly simplistic at this point and we don't deal with things like
evicting objects from the GART to make space, nor compaction.

We extent our gtt_range struct to include a GEM object and that allows GEM
to do all the handle management and most of the memory mapping work for us.

This patch also doesn't load GEM pages into the GART so the GEM side isn't
very useful. Before we can do that a fair bit of work is needed reworking the
internal GTT code.

Signed-off-by: Alan Cox <alan@linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
drivers/staging/gma500/Makefile
drivers/staging/gma500/psb_drv.c
drivers/staging/gma500/psb_drv.h
drivers/staging/gma500/psb_fb.c
drivers/staging/gma500/psb_gem.c [new file with mode: 0644]
drivers/staging/gma500/psb_gtt.c
drivers/staging/gma500/psb_gtt.h