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
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
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
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
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
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
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
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
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
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
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
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
On Wed, 2 Nov 2011 13:03:20 -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.
11/03/2011 05:03 AM, 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 B
On Fri, 04 Nov 2011 16:34:22 +0900
Joonyoung Shim wrote:
> > + case V4L2_PIX_FMT_RGB24:
> > + *depth = 24;
> > + *bpp = 24;
> > + break;
>
> In the depth = 24 and bpp = 32 case also the pixed_format is
> V4L2_PIX_FMT_RGB24, but above function cannot detect it.
On Mon, 7 Nov 2011 23:55:02 +0900
InKi Dae wrote:
> > +struct drm_mode_fb_cmd2 {
> > + __u32 fb_id;
> > + __u32 width, height;
> > + __u32 pixel_format; /* fourcc code from videodev2.h */
> > +
> > + /*
> > + * In case of planar formats, this ioctl allows one
> > +
On Mon, Nov 7, 2011 at 10:12 AM, Jesse Barnes wrote:
> On Mon, 7 Nov 2011 23:55:02 +0900
> InKi Dae wrote:
>> > +struct drm_mode_fb_cmd2 {
>> > + __u32 fb_id;
>> > + __u32 width, height;
>> > + __u32 pixel_format; /* fourcc code from videodev2.h */
>> > +
>> > + /*
>> > +
On Wed, 2 Nov 2011 13:03:20 -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.
11/03/2011 05:03 AM, 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 B
On Fri, 04 Nov 2011 16:34:22 +0900
Joonyoung Shim wrote:
> > + case V4L2_PIX_FMT_RGB24:
> > + *depth = 24;
> > + *bpp = 24;
> > + break;
>
> In the depth = 24 and bpp = 32 case also the pixed_format is
> V4L2_PIX_FMT_RGB24, but above function cannot detect it.
On Mon, 7 Nov 2011 23:55:02 +0900
InKi Dae wrote:
> > +struct drm_mode_fb_cmd2 {
> > + __u32 fb_id;
> > + __u32 width, height;
> > + __u32 pixel_format; /* fourcc code from videodev2.h */
> > +
> > + /*
> > + * In case of planar formats, this ioctl allows one
> > +
On Mon, Nov 7, 2011 at 10:12 AM, Jesse Barnes wrote:
> On Mon, 7 Nov 2011 23:55:02 +0900
> InKi Dae wrote:
>> > +struct drm_mode_fb_cmd2 {
>> > + __u32 fb_id;
>> > + __u32 width, height;
>> > + __u32 pixel_format; /* fourcc code from videodev2.h */
>> > +
>> > + /*
>> > +
On Wed, 2 Nov 2011 13:03:20 -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.
11/03/2011 05:03 AM, 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 B
On Fri, 04 Nov 2011 16:34:22 +0900
Joonyoung Shim wrote:
> > + case V4L2_PIX_FMT_RGB24:
> > + *depth = 24;
> > + *bpp = 24;
> > + break;
>
> In the depth = 24 and bpp = 32 case also the pixed_format is
> V4L2_PIX_FMT_RGB24, but above function cannot detect it.
On Mon, 7 Nov 2011 23:55:02 +0900
InKi Dae wrote:
> > +struct drm_mode_fb_cmd2 {
> > + __u32 fb_id;
> > + __u32 width, height;
> > + __u32 pixel_format; /* fourcc code from videodev2.h */
> > +
> > + /*
> > + * In case of planar formats, this ioctl allows one
> > +
On Mon, Nov 7, 2011 at 10:12 AM, Jesse Barnes wrote:
> On Mon, 7 Nov 2011 23:55:02 +0900
> InKi Dae wrote:
>> > +struct drm_mode_fb_cmd2 {
>> > + __u32 fb_id;
>> > + __u32 width, height;
>> > + __u32 pixel_format; /* fourcc code from videodev2.h */
>> > +
>> > + /*
>> > +
On Wed, 2 Nov 2011 13:03:20 -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.
11/03/2011 05:03 AM, 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 B
On Fri, 04 Nov 2011 16:34:22 +0900
Joonyoung Shim wrote:
> > + case V4L2_PIX_FMT_RGB24:
> > + *depth = 24;
> > + *bpp = 24;
> > + break;
>
> In the depth = 24 and bpp = 32 case also the pixed_format is
> V4L2_PIX_FMT_RGB24, but above function cannot detect it.
On Mon, 7 Nov 2011 23:55:02 +0900
InKi Dae wrote:
> > +struct drm_mode_fb_cmd2 {
> > + __u32 fb_id;
> > + __u32 width, height;
> > + __u32 pixel_format; /* fourcc code from videodev2.h */
> > +
> > + /*
> > + * In case of planar formats, this ioctl allows one
> > +
On Mon, Nov 7, 2011 at 10:12 AM, Jesse Barnes wrote:
> On Mon, 7 Nov 2011 23:55:02 +0900
> InKi Dae wrote:
>> > +struct drm_mode_fb_cmd2 {
>> > + __u32 fb_id;
>> > + __u32 width, height;
>> > + __u32 pixel_format; /* fourcc code from videodev2.h */
>> > +
>> > + /*
>> > +
On Wed, 2 Nov 2011 13:03:20 -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.
11/03/2011 05:03 AM, 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 B
On Fri, 04 Nov 2011 16:34:22 +0900
Joonyoung Shim wrote:
> > + case V4L2_PIX_FMT_RGB24:
> > + *depth = 24;
> > + *bpp = 24;
> > + break;
>
> In the depth = 24 and bpp = 32 case also the pixed_format is
> V4L2_PIX_FMT_RGB24, but above function cannot detect it.
On Mon, 7 Nov 2011 23:55:02 +0900
InKi Dae wrote:
> > +struct drm_mode_fb_cmd2 {
> > + __u32 fb_id;
> > + __u32 width, height;
> > + __u32 pixel_format; /* fourcc code from videodev2.h */
> > +
> > + /*
> > + * In case of planar formats, this ioctl allows one
> > +
On Mon, Nov 7, 2011 at 10:12 AM, Jesse Barnes wrote:
> On Mon, 7 Nov 2011 23:55:02 +0900
> InKi Dae wrote:
>> > +struct drm_mode_fb_cmd2 {
>> > + __u32 fb_id;
>> > + __u32 width, height;
>> > + __u32 pixel_format; /* fourcc code from videodev2.h */
>> > +
>> > + /*
>> > +
On Wed, 2 Nov 2011 13:03:20 -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.
11/03/2011 05:03 AM, 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 B
On Fri, 04 Nov 2011 16:34:22 +0900
Joonyoung Shim wrote:
> > + case V4L2_PIX_FMT_RGB24:
> > + *depth = 24;
> > + *bpp = 24;
> > + break;
>
> In the depth = 24 and bpp = 32 case also the pixed_format is
> V4L2_PIX_FMT_RGB24, but above function cannot detect it.
On Mon, 7 Nov 2011 23:55:02 +0900
InKi Dae wrote:
> > +struct drm_mode_fb_cmd2 {
> > + __u32 fb_id;
> > + __u32 width, height;
> > + __u32 pixel_format; /* fourcc code from videodev2.h */
> > +
> > + /*
> > + * In case of planar formats, this ioctl allows one
> > +
On Mon, Nov 7, 2011 at 10:12 AM, Jesse Barnes wrote:
> On Mon, 7 Nov 2011 23:55:02 +0900
> InKi Dae wrote:
>> > +struct drm_mode_fb_cmd2 {
>> > + __u32 fb_id;
>> > + __u32 width, height;
>> > + __u32 pixel_format; /* fourcc code from videodev2.h */
>> > +
>> > + /*
>> > +
42 matches
Mail list logo
