[PATCH 2/4] drm: add an fb creation ioctl that takes a pixel format

2011-06-21 Thread Laurent Pinchart
(Looping linux-media in) On Thursday 09 June 2011 13:55:13 Alan Cox wrote: > > > You also don't need a headwer with a complete list of fourcc names in > > > it, that is the half the point of FourCC. > > > > #define V4L2_PIX_FMT_RGB332 v4l2_fourcc('R', 'G', 'B', '1') /* 8 > > RGB-3-3-2 */ >

Re: [PATCH 2/4] drm: add an fb creation ioctl that takes a pixel format

2011-06-21 Thread Laurent Pinchart
(Looping linux-media in) On Thursday 09 June 2011 13:55:13 Alan Cox wrote: > > > You also don't need a headwer with a complete list of fourcc names in > > > it, that is the half the point of FourCC. > > > > #define V4L2_PIX_FMT_RGB332 v4l2_fourcc('R', 'G', 'B', '1') /* 8 > > RGB-3-3-2 */ >

[PATCH 2/4] drm: add an fb creation ioctl that takes a pixel format

2011-06-20 Thread Jesse Barnes
To properly support the various plane formats supported by different hardware, the kernel must know the pixel format of a framebuffer object. So add a new ioctl taking a format argument corresponding to a fourcc name from videodev2.h. Signed-off-by: Jesse Barnes --- drivers/gpu/drm/drm_crtc.c

[PATCH 2/4] drm: add an fb creation ioctl that takes a pixel format

2011-06-20 Thread Jesse Barnes
To properly support the various plane formats supported by different hardware, the kernel must know the pixel format of a framebuffer object. So add a new ioctl taking a format argument corresponding to a fourcc name from videodev2.h. Signed-off-by: Jesse Barnes --- drivers/gpu/drm/drm_crtc.c

[PATCH 2/4] drm: add an fb creation ioctl that takes a pixel format

2011-06-09 Thread Dave Airlie
On Thu, 2011-06-09 at 09:21 +0100, Alan Cox wrote: > On Thu, 09 Jun 2011 14:05:59 +1000 > Dave Airlie wrote: > > > On Tue, 2011-06-07 at 13:07 -0700, Jesse Barnes wrote: > > > To properly support the various plane formats supported by different > > > hardware, the kernel must know the pixel forma

[PATCH 2/4] drm: add an fb creation ioctl that takes a pixel format

2011-06-09 Thread Dave Airlie
On Tue, 2011-06-07 at 13:07 -0700, Jesse Barnes wrote: > To properly support the various plane formats supported by different > hardware, the kernel must know the pixel format of a framebuffer object. > So add a new ioctl taking a format argument corresponding to a fourcc > name from videodev2.h.

[PATCH 2/4] drm: add an fb creation ioctl that takes a pixel format

2011-06-09 Thread Alan Cox
> > You also don't need a headwer with a complete list of fourcc names in it, > > that is the half the point of FourCC. > > #define V4L2_PIX_FMT_RGB332 v4l2_fourcc('R', 'G', 'B', '1') /* 8 > RGB-3-3-2 */ > > See that V4L2 and v4l2? I'd rather not have them used in the drm They are just hel

[PATCH 2/4] drm: add an fb creation ioctl that takes a pixel format

2011-06-09 Thread Alan Cox
On Thu, 09 Jun 2011 14:05:59 +1000 Dave Airlie wrote: > On Tue, 2011-06-07 at 13:07 -0700, Jesse Barnes wrote: > > To properly support the various plane formats supported by different > > hardware, the kernel must know the pixel format of a framebuffer object. > > So add a new ioctl taking a form

Re: [PATCH 2/4] drm: add an fb creation ioctl that takes a pixel format

2011-06-09 Thread Alan Cox
> > You also don't need a headwer with a complete list of fourcc names in it, > > that is the half the point of FourCC. > > #define V4L2_PIX_FMT_RGB332 v4l2_fourcc('R', 'G', 'B', '1') /* 8 > RGB-3-3-2 */ > > See that V4L2 and v4l2? I'd rather not have them used in the drm They are just hel

Re: [PATCH 2/4] drm: add an fb creation ioctl that takes a pixel format

2011-06-09 Thread Dave Airlie
On Thu, 2011-06-09 at 09:21 +0100, Alan Cox wrote: > On Thu, 09 Jun 2011 14:05:59 +1000 > Dave Airlie wrote: > > > On Tue, 2011-06-07 at 13:07 -0700, Jesse Barnes wrote: > > > To properly support the various plane formats supported by different > > > hardware, the kernel must know the pixel forma

Re: [PATCH 2/4] drm: add an fb creation ioctl that takes a pixel format

2011-06-09 Thread Alan Cox
On Thu, 09 Jun 2011 14:05:59 +1000 Dave Airlie wrote: > On Tue, 2011-06-07 at 13:07 -0700, Jesse Barnes wrote: > > To properly support the various plane formats supported by different > > hardware, the kernel must know the pixel format of a framebuffer object. > > So add a new ioctl taking a form

Re: [PATCH 2/4] drm: add an fb creation ioctl that takes a pixel format

2011-06-08 Thread Dave Airlie
On Tue, 2011-06-07 at 13:07 -0700, Jesse Barnes wrote: > To properly support the various plane formats supported by different > hardware, the kernel must know the pixel format of a framebuffer object. > So add a new ioctl taking a format argument corresponding to a fourcc > name from videodev2.h.

[PATCH 2/4] drm: add an fb creation ioctl that takes a pixel format

2011-06-07 Thread Jesse Barnes
To properly support the various plane formats supported by different hardware, the kernel must know the pixel format of a framebuffer object. So add a new ioctl taking a format argument corresponding to a fourcc name from videodev2.h. Signed-off-by: Jesse Barnes --- drivers/gpu/drm/drm_crtc.c

[PATCH 2/4] drm: add an fb creation ioctl that takes a pixel format

2011-06-07 Thread Jesse Barnes
To properly support the various plane formats supported by different hardware, the kernel must know the pixel format of a framebuffer object. So add a new ioctl taking a format argument corresponding to a fourcc name from videodev2.h. Signed-off-by: Jesse Barnes --- drivers/gpu/drm/drm_crtc.c

[PATCH 2/4] drm: add an fb creation ioctl that takes a pixel format

2011-06-07 Thread Jesse Barnes
To properly support the various plane formats supported by different hardware, the kernel must know the pixel format of a framebuffer object. So add a new ioctl taking a format argument corresponding to a fourcc name from videodev2.h. Signed-off-by: Jesse Barnes --- drivers/gpu/drm/drm_crtc.c