To improve the conformability and avoid compiling error with libva/intel-driver(expected specifier-qualifier-list before uint32_t),
I think it's better to use __u32 instead of using uint32_t.
Thanks and best regards.
Hai Lan
> #define DRM_MODE_FB_DIRTY_ANNOTATE_COPY 0x01
> #define DRM_MODE_FB_DIRTY_ANNOTATE_FILL 0x02
> #define DRM_MODE_FB_DIRTY_FLAGS 0x03
> @@ -346,31 +410,31 @@ struct drm_mode_crtc_page_flip {
>
> /* create a dumb scanout buffer */
> struct drm_mode_create_dumb {
> - __u32 height;
> - __u32 width;
> - __u32 bpp;
> - __u32 flags;
> - /* handle, pitch, size will be returned */
> - __u32 handle;
> - __u32 pitch;
> - __u64 size;
> + uint32_t height;
> + uint32_t width;
> + uint32_t bpp;
> + uint32_t flags;
> + /* handle, pitch, size will be returned */
> + uint32_t handle;
> + uint32_t pitch;
> + uint64_t size;
> };
>
> /* set up for mmap of a dumb scanout buffer */
> struct drm_mode_map_dumb {
> - /** Handle for the object being mapped. */
> - __u32 handle;
> - __u32 pad;
> - /**
> - * Fake offset to use for subsequent mmap call
> - *
> - * This is a fixed-size type for 32/64 compatibility.
> - */
> - __u64 offset;
> + /** Handle for the object being mapped. */
> + __u32 handle;
> + __u32 pad;
> + /**
> + * Fake offset to use for subsequent mmap call
> + *
> + * This is a fixed-size type for 32/64 compatibility.
> + */
> + __u64 offset;
> };
>
> struct drm_mode_destroy_dumb {
> - __u32 handle;
> + uint32_t handle;
> };
>
> #endif
_______________________________________________
dri-devel mailing list
dri-devel@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/dri-devel
