From: Laurent Pinchart <laurent.pinchart@ideasonboard.com> To: Geert Uytterhoeven <geert@linux-m68k.org> Cc: linux-fbdev@vger.kernel.org, linux-media@vger.kernel.org, magnus.damm@gmail.com Subject: Re: [PATCH/RFC v2 1/3] fbdev: Add FOURCC-based format configuration API Date: Mon, 29 Aug 2011 13:08:49 +0200 [thread overview] Message-ID: <201108291308.50244.laurent.pinchart@ideasonboard.com> (raw) In-Reply-To: <CAMuHMdU3eO34zmGVejUj4B7Z5JWiwM_pieoycfinSspSiL1reQ@mail.gmail.com> Hi Geert, On Monday 29 August 2011 13:04:15 Geert Uytterhoeven wrote: > On Mon, Aug 29, 2011 at 12:09, Laurent Pinchart wrote: > > On Monday 29 August 2011 11:36:07 Geert Uytterhoeven wrote: > >> On Mon, Aug 29, 2011 at 10:50, Laurent Pinchart wrote: > [...] > > > If my understanding is now correct, a V4L2 planar YUV type where Y, U and > > V components are stored in separate byte-oriented planes, with each > > plane storing Y, U or V components packed (such as > > http://linuxtv.org/downloads/v4l- dvb-apis/V4L2-PIX-FMT-YUV422P.html), > > would be of neither FB_TYPE_PLANES nor FB_TYPE_PACKED. The same would be > > true for an RGB format where each component is stored in a separate > > plane with each plane sotring R, G or B packed. > > Indeed. Currently this cannot be represented. Good, at least I now understand the situation :-) > For ideas from the past, see e.g. > http://comments.gmane.org/gmane.linux.fbdev.devel/10951. > > > If the above is correct, what FB_TYPE_* should a driver report when using > > FB_VISUAL_FOURCC with V4L2_PIX_FMT_YUV422P > > (http://linuxtv.org/downloads/v4l- dvb-apis/V4L2-PIX-FMT-YUV422P.html) > > or V4L2_PIX_FMT_NV12 > > (http://linuxtv.org/downloads/v4l-dvb-apis/re25.html) for instance ? > > We need new types for those. Or always use FOURCC for them. My proposal currently defined FB_VISUAL_FOURCC. What about adding FB_TYPE_FOURCC as well ? -- Regards, Laurent Pinchart
WARNING: multiple messages have this Message-ID (diff)
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com> To: Geert Uytterhoeven <geert@linux-m68k.org> Cc: linux-fbdev@vger.kernel.org, linux-media@vger.kernel.org, magnus.damm@gmail.com Subject: Re: [PATCH/RFC v2 1/3] fbdev: Add FOURCC-based format configuration API Date: Mon, 29 Aug 2011 11:08:49 +0000 [thread overview] Message-ID: <201108291308.50244.laurent.pinchart@ideasonboard.com> (raw) In-Reply-To: <CAMuHMdU3eO34zmGVejUj4B7Z5JWiwM_pieoycfinSspSiL1reQ@mail.gmail.com> Hi Geert, On Monday 29 August 2011 13:04:15 Geert Uytterhoeven wrote: > On Mon, Aug 29, 2011 at 12:09, Laurent Pinchart wrote: > > On Monday 29 August 2011 11:36:07 Geert Uytterhoeven wrote: > >> On Mon, Aug 29, 2011 at 10:50, Laurent Pinchart wrote: > [...] > > > If my understanding is now correct, a V4L2 planar YUV type where Y, U and > > V components are stored in separate byte-oriented planes, with each > > plane storing Y, U or V components packed (such as > > http://linuxtv.org/downloads/v4l- dvb-apis/V4L2-PIX-FMT-YUV422P.html), > > would be of neither FB_TYPE_PLANES nor FB_TYPE_PACKED. The same would be > > true for an RGB format where each component is stored in a separate > > plane with each plane sotring R, G or B packed. > > Indeed. Currently this cannot be represented. Good, at least I now understand the situation :-) > For ideas from the past, see e.g. > http://comments.gmane.org/gmane.linux.fbdev.devel/10951. > > > If the above is correct, what FB_TYPE_* should a driver report when using > > FB_VISUAL_FOURCC with V4L2_PIX_FMT_YUV422P > > (http://linuxtv.org/downloads/v4l- dvb-apis/V4L2-PIX-FMT-YUV422P.html) > > or V4L2_PIX_FMT_NV12 > > (http://linuxtv.org/downloads/v4l-dvb-apis/re25.html) for instance ? > > We need new types for those. Or always use FOURCC for them. My proposal currently defined FB_VISUAL_FOURCC. What about adding FB_TYPE_FOURCC as well ? -- Regards, Laurent Pinchart
next prev parent reply other threads:[~2011-08-29 11:08 UTC|newest] Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-08-19 9:37 [PATCH/RFC v2 0/3] fbdev: Add FOURCC-based format configuration API Laurent Pinchart 2011-08-19 9:37 ` Laurent Pinchart 2011-08-19 9:37 ` [PATCH/RFC v2 1/3] " Laurent Pinchart 2011-08-19 9:37 ` Laurent Pinchart 2011-08-26 17:07 ` Florian Tobias Schandinat 2011-08-26 17:07 ` [PATCH/RFC v2 1/3] fbdev: Add FOURCC-based format configuration Florian Tobias Schandinat 2011-08-28 8:48 ` [PATCH/RFC v2 1/3] fbdev: Add FOURCC-based format configuration API Laurent Pinchart 2011-08-28 8:48 ` Laurent Pinchart 2011-08-29 8:13 ` Geert Uytterhoeven 2011-08-29 8:13 ` Geert Uytterhoeven 2011-08-29 8:50 ` Laurent Pinchart 2011-08-29 8:50 ` Laurent Pinchart 2011-08-29 9:36 ` Geert Uytterhoeven 2011-08-29 9:36 ` Geert Uytterhoeven 2011-08-29 10:09 ` Laurent Pinchart 2011-08-29 10:09 ` Laurent Pinchart 2011-08-29 11:04 ` Geert Uytterhoeven 2011-08-29 11:04 ` Geert Uytterhoeven 2011-08-29 11:08 ` Laurent Pinchart [this message] 2011-08-29 11:08 ` Laurent Pinchart 2011-08-29 11:20 ` Geert Uytterhoeven 2011-08-29 11:20 ` Geert Uytterhoeven 2011-08-29 12:55 ` Laurent Pinchart 2011-08-29 12:55 ` Laurent Pinchart 2011-08-29 13:09 ` Geert Uytterhoeven 2011-08-29 13:09 ` Geert Uytterhoeven 2011-08-29 13:34 ` Laurent Pinchart 2011-08-29 13:34 ` Laurent Pinchart 2011-08-29 14:14 ` Geert Uytterhoeven 2011-08-29 14:14 ` Geert Uytterhoeven 2011-08-29 14:17 ` Laurent Pinchart 2011-08-29 14:17 ` Laurent Pinchart 2011-08-29 14:26 ` Geert Uytterhoeven 2011-08-29 14:26 ` Geert Uytterhoeven 2011-08-29 14:32 ` Laurent Pinchart 2011-08-29 14:32 ` Laurent Pinchart 2011-08-29 16:41 ` Florian Tobias Schandinat 2011-08-29 16:41 ` [PATCH/RFC v2 1/3] fbdev: Add FOURCC-based format configuration Florian Tobias Schandinat 2011-08-30 1:09 ` [PATCH/RFC v2 1/3] fbdev: Add FOURCC-based format configuration API Laurent Pinchart 2011-08-30 1:09 ` Laurent Pinchart 2011-08-19 9:37 ` [PATCH/RFC v2 2/3] v4l: Add V4L2_PIX_FMT_NV24 and V4L2_PIX_FMT_NV42 formats Laurent Pinchart 2011-08-19 9:37 ` Laurent Pinchart 2011-08-19 9:37 ` [PATCH/RFC v2 3/3] fbdev: sh_mobile_lcdc: Support FOURCC-based format API Laurent Pinchart 2011-08-19 9:37 ` Laurent Pinchart 2011-08-26 17:24 ` Florian Tobias Schandinat 2011-08-26 17:24 ` [PATCH/RFC v2 3/3] fbdev: sh_mobile_lcdc: Support FOURCC-based Florian Tobias Schandinat 2011-08-28 8:59 ` [PATCH/RFC v2 3/3] fbdev: sh_mobile_lcdc: Support FOURCC-based format API Laurent Pinchart 2011-08-28 8:59 ` Laurent Pinchart 2011-08-29 0:39 ` Magnus Damm 2011-08-29 0:39 ` [PATCH/RFC v2 3/3] fbdev: sh_mobile_lcdc: Support FOURCC-based Magnus Damm 2011-08-29 8:30 ` [PATCH/RFC v2 3/3] fbdev: sh_mobile_lcdc: Support FOURCC-based format API Laurent Pinchart 2011-08-29 8:30 ` Laurent Pinchart
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=201108291308.50244.laurent.pinchart@ideasonboard.com \ --to=laurent.pinchart@ideasonboard.com \ --cc=geert@linux-m68k.org \ --cc=linux-fbdev@vger.kernel.org \ --cc=linux-media@vger.kernel.org \ --cc=magnus.damm@gmail.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.