summaryrefslogtreecommitdiff
path: root/shared-core
diff options
context:
space:
mode:
authorKristian Høgsberg <krh@redhat.com>2007-10-09 21:09:30 -0400
committerDave Airlie <airlied@linux.ie>2007-10-16 22:03:05 +1100
commitdccefba71a65566e7e1628b3be67621866000411 (patch)
tree339b8d236f0ebca9e88554042fbc648309bc21bc /shared-core
parent440fc5113ef1ffb1a22bff92cf34eaf23896db8d (diff)
Take bo type argument out of the ioctl interface.
The buffer object type is still tracked internally, but it is no longer part of the user space visible ioctl interface. If the bo create ioctl specifies a non-NULL buffer address we assume drm_bo_type_user, otherwise drm_bo_type_dc. Kernel side allocations call drm_buffer_object_create() directly and can still specify drm_bo_type_kernel. Not 100% this makes sense either, but with this patch, the buffer type is no longer exported and we can clean up the internals later on.
Diffstat (limited to 'shared-core')
-rw-r--r--shared-core/drm.h8
1 files changed, 0 insertions, 8 deletions
diff --git a/shared-core/drm.h b/shared-core/drm.h
index 279f858f..568b1003 100644
--- a/shared-core/drm.h
+++ b/shared-core/drm.h
@@ -754,12 +754,6 @@ struct drm_fence_arg {
#define DRM_BO_INIT_MINOR 1
-enum drm_bo_type {
- drm_bo_type_dc,
- drm_bo_type_user,
- drm_bo_type_kernel, /* for initial kernel allocations */
-};
-
struct drm_bo_info_req {
uint64_t mask;
uint64_t flags;
@@ -775,8 +769,6 @@ struct drm_bo_create_req {
uint64_t buffer_start;
unsigned int hint;
unsigned int page_alignment;
- enum drm_bo_type type;
- unsigned int pad64;
};
struct drm_bo_op_req {