From: Hans Verkuil <hverkuil@xs4all.nl>
To: linux-media@vger.kernel.org
Cc: corbet@lwn.net, Hans Verkuil <hans.verkuil@cisco.com>
Subject: Re: [PATCH 18/18] marvell-ccic: fix Y'CbCr ordering
Date: Tue, 10 Mar 2015 16:56:39 +0100 [thread overview]
Message-ID: <54FF1437.1050206@xs4all.nl> (raw)
In-Reply-To: <1425936143-5658-19-git-send-email-hverkuil@xs4all.nl>
On 03/09/2015 10:22 PM, Hans Verkuil wrote:
> From: Hans Verkuil <hans.verkuil@cisco.com>
>
> Various formats had their byte ordering implemented incorrectly, and
> the V4L2_PIX_FMT_UYVY is actually impossible to create, instead you
> get V4L2_PIX_FMT_YVYU.
>
> This was working before commit ad6ac452227b7cb93ac79beec092850d178740b1
> ("add new formats support for marvell-ccic driver"). That commit broke
> the original format support and the OLPC XO-1 laptop showed wrong
> colors ever since (if you are crazy enough to attempt to run the latest
> kernel on it, like I did).
I tried to contact the original authors of that commit but I couldn't reach
them. So I've added the following to the commit log of this patch:
"The email addresses of the authors of that patch are no longer valid,
so without a way to reach them and ask them about their test setup
I am going with what I can test on the OLPC laptop.
If this breaks something for someone on their non-OLPC setup, then
contact the linux-media mailinglist. My suspicion however is that
that commit went in untested."
Regards,
Hans
next prev parent reply other threads:[~2015-03-10 15:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 21:22 [PATCH 00/18] marvell-ccic + ov7670 fixes Hans Verkuil
2015-03-09 21:22 ` [PATCH 01/18] marvell-ccic: fix vb2 warning Hans Verkuil
2015-03-09 21:22 ` [PATCH 02/18] marvell-ccic: fill in bus_info Hans Verkuil
2015-03-09 21:22 ` [PATCH 03/18] marvell-ccic: webcam drivers shouldn't support g/s_std Hans Verkuil
2015-03-09 21:22 ` [PATCH 04/18] ov7670: check for valid width/height in ov7670_enum_frame_interval Hans Verkuil
2015-03-09 21:22 ` [PATCH 05/18] marvell-ccic: fill in colorspace Hans Verkuil
2015-03-09 21:22 ` [PATCH 06/18] marvell-ccic: control handler fixes Hans Verkuil
2015-03-09 21:22 ` [PATCH 07/18] marvell-ccic: switch to struct v4l2_fh Hans Verkuil
2015-03-09 21:22 ` [PATCH 08/18] marvell-ccic: implement control events Hans Verkuil
2015-03-09 21:22 ` [PATCH 09/18] marvell-ccic: use vb2 helpers and core locking Hans Verkuil
2015-03-09 21:22 ` [PATCH 10/18] marvell-ccic: add create_bufs support Hans Verkuil
2015-03-09 21:22 ` [PATCH 11/18] marvell-ccic: add DMABUF support for all three DMA modes Hans Verkuil
2015-03-09 21:22 ` [PATCH 12/18] marvell-ccic: fix streaming issues Hans Verkuil
2015-03-09 21:22 ` [PATCH 13/18] marvell-ccic: correctly requeue buffers Hans Verkuil
2015-03-09 21:22 ` [PATCH 14/18] marvell-ccic: add planar support to dma-vmalloc Hans Verkuil
2015-03-09 21:22 ` [PATCH 15/18] marvell-ccic: drop V4L2_PIX_FMT_JPEG dead code Hans Verkuil
2015-03-09 21:22 ` [PATCH 16/18] ov7670: use colorspace SRGB instead of JPEG Hans Verkuil
2015-03-09 21:22 ` [PATCH 17/18] marvell-ccic: fix the bytesperline and sizeimage calculations Hans Verkuil
2015-03-09 21:22 ` [PATCH 18/18] marvell-ccic: fix Y'CbCr ordering Hans Verkuil
2015-03-10 15:56 ` Hans Verkuil [this message]
2015-03-10 14:30 ` [PATCH 00/18] marvell-ccic + ov7670 fixes Jonathan Corbet
2015-03-10 14:49 ` 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=54FF1437.1050206@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=corbet@lwn.net \
--cc=hans.verkuil@cisco.com \
--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