aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/radeon/radeon_kms.c
diff options
context:
space:
mode:
authorDave Airlie <airlied@redhat.com>2011-02-07 12:16:14 +1000
committerDave Airlie <airlied@redhat.com>2011-02-07 12:16:14 +1000
commitff72145badb834e8051719ea66e024784d000cb4 (patch)
tree39dc5fc512e3e0836713de9defb91ea8b4033aa2 /drivers/gpu/drm/radeon/radeon_kms.c
parent1f692a14cbfbeb11f9a9c16f25c8ecb8ab50d3d5 (diff)
downloadkernel_samsung_smdk4412-ff72145badb834e8051719ea66e024784d000cb4.zip
kernel_samsung_smdk4412-ff72145badb834e8051719ea66e024784d000cb4.tar.gz
kernel_samsung_smdk4412-ff72145badb834e8051719ea66e024784d000cb4.tar.bz2
drm: dumb scanout create/mmap for intel/radeon (v3)
This is just an idea that might or might not be a good idea, it basically adds two ioctls to create a dumb and map a dumb buffer suitable for scanout. The handle can be passed to the KMS ioctls to create a framebuffer. It looks to me like it would be useful in the following cases: a) in development drivers - we can always provide a shadowfb fallback. b) libkms users - we can clean up libkms a lot and avoid linking to libdrm_*. c) plymouth via libkms is a lot easier. Userspace bits would be just calls + mmaps. We could probably mark these handles somehow as not being suitable for acceleartion so as top stop people who are dumber than dumb. Signed-off-by: Dave Airlie <airlied@redhat.com>
Diffstat (limited to 'drivers/gpu/drm/radeon/radeon_kms.c')
0 files changed, 0 insertions, 0 deletions