From: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-fbdev@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [PATCH v4 0/3] fbdev: Add FOURCC-based format configuration API
Date: Mon, 12 Dec 2011 18:49:38 +0000 [thread overview]
Message-ID: <4EE64CC2.5090906@gmx.de> (raw)
In-Reply-To: <201112121708.30839.laurent.pinchart@ideasonboard.com>
Hi Laurent,
On 12/12/2011 04:08 PM, Laurent Pinchart wrote:
> Hi Florian,
>
> On Tuesday 29 November 2011 11:26:56 Laurent Pinchart wrote:
>> Hi everybody,
>>
>> Here's the fourth version of the fbdev FOURCC-based format configuration
>> API.
>
> Is there a chance this will make it to v3.3 ?
Yes, that's likely. I thought you wanted to post a new version of 2/3?
I think you also want to do something with red, green, blue, transp when
entering FOURCC mode, at least setting them to zero or maybe even requiring that
they are zero to enter FOURCC mode (as additional safety barrier).
Best regards,
Florian Tobias Schandinat
next prev parent reply other threads:[~2011-12-12 18:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 10:26 [PATCH v4 0/3] fbdev: Add FOURCC-based format configuration API Laurent Pinchart
2011-11-29 10:26 ` [PATCH v4 1/3] " Laurent Pinchart
2011-11-29 10:26 ` [PATCH v4 2/3] v4l: Add V4L2_PIX_FMT_NV24 and V4L2_PIX_FMT_NV42 formats Laurent Pinchart
2011-11-29 17:19 ` [PATCH v4 2/3] v4l: Add V4L2_PIX_FMT_NV24 and V4L2_PIX_FMT_NV42 Sylwester Nawrocki
2011-11-29 18:11 ` [PATCH v4 2/3] v4l: Add V4L2_PIX_FMT_NV24 and V4L2_PIX_FMT_NV42 formats Laurent Pinchart
2011-11-29 10:26 ` [PATCH v4 3/3] fbdev: sh_mobile_lcdc: Support FOURCC-based format API Laurent Pinchart
2011-12-12 16:08 ` [PATCH v4 0/3] fbdev: Add FOURCC-based format configuration API Laurent Pinchart
2011-12-12 18:49 ` Florian Tobias Schandinat [this message]
2011-12-13 0:40 ` Laurent Pinchart
2011-12-13 10:47 ` Geert Uytterhoeven
2011-12-13 11:46 ` 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=4EE64CC2.5090906@gmx.de \
--to=florianschandinat@gmx.de \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).