From: Hans Verkuil <hverkuil@xs4all.nl>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCHv2 00/21] marvell-ccic: drop and fix formats
Date: Fri, 13 Mar 2015 22:59:00 +0100 [thread overview]
Message-ID: <55035DA4.2020903@xs4all.nl> (raw)
In-Reply-To: <20150313172801.6bc4bf75@lwn.net>
Hi Jon,
On 03/13/2015 10:28 PM, Jonathan Corbet wrote:
> On Wed, 11 Mar 2015 09:10:24 +0100
> Hans Verkuil <hverkuil@xs4all.nl> wrote:
>
>> After some more testing I realized that the 422P format produced
>> wrong colors and I couldn't get it to work. Since it never worked and
>> nobody complained about it (and it is a fairly obscure format as well)
>> I've dropped it.
>
> I'm not sure how that format came in anymore; I didn't add it. No
> objections to its removal.
It came in with the patches from Marvell.
>> I also tested RGB444 format for the first time, and that had wrong colors
>> as well, but that was easy to fix. Finally there was a Bayer format
>> reported, but it was never implemented. So that too was dropped.
>
> The RGB444 change worries me somewhat; that was the default format on the
> XO1 and worked for years. I vaguely remember some discussions about the
> ordering of the colors there, but that was a while ago. Did you test it
> with any of the Sugar apps?
I've tested with the 'Record' app, and that picks a YUV format, not RGB444.
Are there other apps that I can test with where you can select the capture
format?
> In the end, correctness is probably the right way to go (it usually is!),
> but I'd hate to get a regression report from somebody who is crazy enough
> to put current kernels on those machines. Fortunately, such people
> should be rare.
>
> Bayer sort-of worked once, honest. I added it for some academic who
> wanted to do stuff, and was never really able to close the loop on
> getting it working correctly. It might be worth removing the alleged
> support from ov7670 as well.
I might give it try to get it to work. I'm in the process of adding Bayer
support to the vivid driver, which makes it easier to test. I'll see if
I have some time this weekend.
> In any case, for all of them:
>
> Acked-by: Jonathan Corbet <corbet@lwn.net>
Thanks!
Hans
next prev parent reply other threads:[~2015-03-13 21:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 8:10 [PATCHv2 00/21] marvell-ccic: drop and fix formats Hans Verkuil
2015-03-11 8:10 ` [PATCHv2 18/21] marvell-ccic: fix Y'CbCr ordering Hans Verkuil
2015-03-11 8:10 ` [PATCHv2 19/21] marvell-ccic: add XRGB444 and fix (X)RGB444 colors Hans Verkuil
2015-03-11 8:10 ` [PATCHv2 20/21] marvell-ccic: drop bayer format Hans Verkuil
2015-03-11 8:10 ` [PATCHv2 21/21] marvell-ccic: drop support for PIX_FMT_422P Hans Verkuil
2015-03-13 21:28 ` [PATCHv2 00/21] marvell-ccic: drop and fix formats Jonathan Corbet
2015-03-13 21:59 ` Hans Verkuil [this message]
2015-03-14 9:15 ` Hans Verkuil
2015-03-14 10:54 ` Hans Verkuil
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=55035DA4.2020903@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=corbet@lwn.net \
--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 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.