From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: video4linux-list@redhat.com
Subject: Re: [PATCH] mt9m111: Fix YUYV format for pxa-camera
Date: Mon, 03 Nov 2008 21:19:50 +0100 [thread overview]
Message-ID: <87mygg4l5l.fsf@free.fr> (raw)
In-Reply-To: <Pine.LNX.4.64.0811031944340.7744@axis700.grange> (Guennadi Liakhovetski's message of "Mon\, 3 Nov 2008 20\:09\:53 +0100 \(CET\)")
Guennadi Liakhovetski <g.liakhovetski@gmx.de> writes:
> Hm, wondering how you know?:-) I agree most probably there are about 2
> users of this driver in the world:-), but who knows?
Yes, who knows ...
> I don't see why 27-19 should be wrong - it specifies exactly the byte
> order CbYCrY, i.r., UYVY (I think, this is what you meant by "UYUV".)
Well, the one working configuration known, Antonio's is :
- pxa CPU
- mt9m111, with OUTPUT_FORMAT_CTRL[1]=1
According to the mt9m111 datasheet, table 3, page 14, when OUTPUT_FORMAT_CTRL[1]
= 1 and OUTPUT_FORMAT_CTRL[0] = 0, the MT9M111 sensor outputs data as follows :
- byte1 = Y1
- byte2 = Cb1
- byte3 = Y2
- byte4 = Cr1
- and so on ...
According to PXA27x datasheet, table 27-19, input bytes from the sensor should
be :
- byte1 = Cb1
- byte2 = Y1
- byte3 = Cr1
- byte4 = Y2
- and so on ...
Do you see the discrepancy now ? Either pxa27x datasheet of mt9m111 datasheet is
wrong, or else Antonio's setup wouldn't work.
> Good, then this is the fix that I'd like to have. It seems pretty simple,
> it will preserve behaviour of mt9m111. It will change the behaviour of
> pxa-camera for the YUYV format, to be precise, it will stop supporting
> this format. So, I would print out a warning, explaining that this format
> is not supported by pxa270 and the user should use UYVY instead. I
> suggested to add only one format to mt9m111 so far, just because this is
> the easiest as a bug-fix. But if you prefer, you can add all four, yes.
Right, so be it for the 4 formats.
> Still, I would really prefer to see the version described above - add more
> formats to mt9m111 and fix pxa270 to claim the correct format and print a
> warning for YUYV. This shouldn't be much more difficult to make than the
> proposed patch, and it will be correct. I made enough bad experiences with
> "temporary fixes" to try to avoid them as much as possible:-)
If you wish so. I'll watch you pushing the fix in the stable branch to see how
you convince people that changing the pxa camera driver is only a "fix" and not
an evolution :) Too bad for a quick working fix.
Cheers.
--
Robert
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next prev parent reply other threads:[~2008-11-03 20:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 22:25 [PATCH] mt9m111: Fix YUYV format for pxa-camera Antonio Ospite
2008-10-31 17:21 ` Robert Jarzmik
2008-10-31 17:40 ` Guennadi Liakhovetski
2008-10-31 18:04 ` Robert Jarzmik
2008-10-31 17:45 ` Antonio Ospite
2008-11-02 21:15 ` Guennadi Liakhovetski
2008-11-03 17:23 ` Robert Jarzmik
2008-11-03 19:09 ` Guennadi Liakhovetski
2008-11-03 20:19 ` Robert Jarzmik [this message]
2008-11-03 20:52 ` Guennadi Liakhovetski
2008-11-03 22:26 ` Guennadi Liakhovetski
2008-11-03 22:31 ` Robert Jarzmik
2008-11-04 14:42 ` Guennadi Liakhovetski
2008-11-04 17:21 ` Antonio Ospite
2008-11-04 21:57 ` Robert Jarzmik
2008-11-04 21:59 ` [PATCH] Add new pixel format VYUY 16 bits wide Robert Jarzmik
2008-11-04 21:59 ` [PATCH] mt9m111: add all yuv format combinations Robert Jarzmik
2008-11-04 22:40 ` Guennadi Liakhovetski
2008-11-05 22:04 ` Robert Jarzmik
2008-11-05 22:37 ` Guennadi Liakhovetski
2008-12-01 13:59 ` Guennadi Liakhovetski
2008-12-01 18:30 ` Robert Jarzmik
2008-11-04 22:43 ` [PATCH] Add new pixel format VYUY 16 bits wide Guennadi Liakhovetski
2008-11-05 7:19 ` 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=87mygg4l5l.fsf@free.fr \
--to=robert.jarzmik@free.fr \
--cc=g.liakhovetski@gmx.de \
--cc=video4linux-list@redhat.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: 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