linux.git/drivers/gpu/drm/drm_hashtab.c, branch v2.6.31 Linux kernel source tree drm: Remove memory debugging infrastructure. 2009-06-18T20:00:33+00:00 Eric Anholt eric@anholt.net 2009-03-24T19:23:04+00:00 9a298b2acd771d8a5c0004d8f8e4156c65b11f6b It hasn't been used in ages, and having the user tell your how much memory is being freed at free time is a recipe for disaster even if it was ever used. Signed-off-by: Eric Anholt <eric@anholt.net> 
It hasn't been used in ages, and having the user tell your how much
memory is being freed at free time is a recipe for disaster even if it
was ever used.

Signed-off-by: Eric Anholt <eric@anholt.net>
drm: Export hash table functionality. 2009-06-12T05:56:33+00:00 Jerome Glisse glisse@freedesktop.org 2009-04-08T15:16:24+00:00 f2cb5d86e1af175a9b210241800f03a447f92621 add exports so TTM module can use these functions. Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com> Signed-off-by: Dave Airlie <airlied@redhat.com> 
add exports so TTM module can use these functions.

Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com>
Signed-off-by: Dave Airlie <airlied@redhat.com>
drm: GEM mmap support 2008-12-29T07:47:22+00:00 Jesse Barnes jbarnes@virtuousgeek.org 2008-11-05T18:31:53+00:00 a2c0a97b784f837300f7b0869c82ab712c600952 Add core support for mapping of GEM objects. Drivers should provide a vm_operations_struct if they want to support page faulting of objects. The code for handling GEM object offsets was taken from TTM, which was written by Thomas Hellström. Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org> Signed-off-by: Eric Anholt <eric@anholt.net> Signed-off-by: Dave Airlie <airlied@redhat.com> 
Add core support for mapping of GEM objects.  Drivers should provide a
vm_operations_struct if they want to support page faulting of objects.
The code for handling GEM object offsets was taken from TTM, which was
written by Thomas Hellström.

Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
drm: reorganise drm tree to be more future proof. 2008-07-14T00:45:01+00:00 Dave Airlie airlied@redhat.com 2008-05-29T00:09:59+00:00 c0e09200dc0813972442e550a5905a132768e56c With the coming of kernel based modesetting and the memory manager stuff, the everything in one directory approach was getting very ugly and starting to be unmanageable. This restructures the drm along the lines of other kernel components. It creates a drivers/gpu/drm directory and moves the hw drivers into subdirectores. It moves the includes into an include/drm, and sets up the unifdef for the userspace headers we should be exporting. Signed-off-by: Dave Airlie <airlied@redhat.com> 
With the coming of kernel based modesetting and the memory manager stuff,
the everything in one directory approach was getting very ugly and
starting to be unmanageable.

This restructures the drm along the lines of other kernel components.

It creates a drivers/gpu/drm directory and moves the hw drivers into
subdirectores. It moves the includes into an include/drm, and
sets up the unifdef for the userspace headers we should be exporting.

Signed-off-by: Dave Airlie <airlied@redhat.com>