From: "Daniel Glöckner" <daniel-gl@gmx.net>
To: Florian Boor <florian.boor@kernelconcepts.de>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: MT9M131 on I.MX6DL CSI color issue
Date: Sat, 20 Jan 2018 16:02:05 +0100 [thread overview]
Message-ID: <20180120150204.GA17833@minime.bse> (raw)
In-Reply-To: <4407aea6-4a7e-a637-40ae-3b25f43b81e5@kernelconcepts.de>
Hello Florian,
On Thu, Jan 18, 2018 at 05:31:43PM +0100, Florian Boor wrote:
> > But that does not explain the wraparounds. Can you rule out that the
> > data lines have been connected in the wrong order?
>
> According to the schematics and camera documentation I have the order of the
> data lines is correct. I checked one more time... but I'm not sure if the
> configuration of the parallel camera input is perfectly right.
>
> The hardware uses CSI0 data lines 12 to 19 and so I used the configuration
> from the SabreLite board:
The VM-009 has 10 data lines. Do you use a board designed by Phytec?
If not, did you connect the lower or the upper 8 data lines to the i.MX6?
Using the upper 8 data lines is correct.
I'm asking because the raw frames I asked for off list* contain only odd
bytes except for some null bytes. And for all components they exceed the
standard value range (Y 16-235, Cb/Cr 16-240).
Have you ever tried to capture images in one of the RGB formats?
Best regards,
Daniel
*)
http://www.kernelconcepts.de/~florian/frame.raw
http://www.kernelconcepts.de/~florian/frame2.raw
next prev parent reply other threads:[~2018-01-20 15:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 0:16 MT9M131 on I.MX6DL CSI color issue Florian Boor
2018-01-12 9:58 ` Anatolij Gustschin
2018-01-12 10:06 ` Anatolij Gustschin
2018-01-15 10:40 ` Florian Boor
2018-01-17 10:31 ` Daniel Glöckner
2018-01-17 12:58 ` Florian Boor
2018-01-18 4:03 ` Daniel Glöckner
2018-01-18 16:31 ` Florian Boor
2018-01-20 15:02 ` Daniel Glöckner [this message]
2018-01-22 14:52 ` Florian Boor
2018-01-30 17:13 ` Florian Boor
2018-01-12 14:59 ` Nicolas Dufresne
2018-01-15 12:49 ` Philipp Zabel
2018-01-15 14:41 ` Florian Boor
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=20180120150204.GA17833@minime.bse \
--to=daniel-gl@gmx.net \
--cc=florian.boor@kernelconcepts.de \
--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