From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: video4linux-list@redhat.com
Subject: Re: [RFC] soc_camera: endianness between camera and its host
Date: Sun, 03 Aug 2008 01:38:42 +0200 [thread overview]
Message-ID: <873alnt2bh.fsf@free.fr> (raw)
In-Reply-To: <Pine.LNX.4.64.0808022146090.27474@axis700.grange> (Guennadi Liakhovetski's message of "Sat\, 2 Aug 2008 22\:09\:50 +0200 \(CEST\)")
Guennadi Liakhovetski <g.liakhovetski@gmx.de> writes:
> On Sat, 2 Aug 2008, Robert Jarzmik wrote:
>
>> Modern camera chips provide ways to invert their data output, as well in colors
>> swap as in byte order. To be more precise, the one I know (mt9m111) enables :
>
> To me these look like just different pixel formats:
Ah, they look like, but there aren't.
Let me explain the subtle part of it by an example on mio a701 phone :
- mt9m111 is connected to a pxa272 cpu through an 8bit bus
- when I select RGB565 as a pixel format, the pxa cpu expects the bits in a
very precise order :
- have a look at PXA Developper Manual, chapter 27.4.5.2.1, table 27-10. The
order the bytes are comming on the bus is important, because of the
"interpretation" the PXA does, to reorder and store them in memory.
=> the chip must send the bytes in that order
- if you pay attention closely, you'll notice the pxa doesn't expect RGB but
inverted BGR.
- have a look at Micron MT9M111 specification, table 5, page 14. You'll see
what they consider as RGB565.
>> - swapping first and second byte in RGB formats
>
> hm, no idea about this one
Explanation above. Have a look at the 2 specification, and the tables I
mentionned. It will be far more clearer.
> So, I don't see at first any relation to host's endianness. You just
> define respective formats in cameras array of struct
> soc_camera_data_format.
That would be true if the host didn't interpret and reorder the bytes, which pxa
does.
> Isn't using the existing pixel format negotiation procedure eough?
If you still think that after looking at the tables, well .. we'll discuss
further. Maybe there's something I don't see ... You tell me your opinion once
you had looked at the tables.
You have all my code now, so you know what I'm facing here :)
--
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-08-02 23:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-02 10:58 [RFC] soc_camera: endianness between camera and its host Robert Jarzmik
2008-08-02 20:09 ` Guennadi Liakhovetski
2008-08-02 23:38 ` Robert Jarzmik [this message]
2008-08-12 14:59 ` Guennadi Liakhovetski
2008-08-13 8:37 ` robert.jarzmik
2008-08-13 9:10 ` Guennadi Liakhovetski
2008-08-13 10:03 ` robert.jarzmik
2008-08-13 11:35 ` [PATCH] mt9m111: style cleanup Guennadi Liakhovetski
2008-08-13 16:38 ` Robert Jarzmik
2008-08-13 16:47 ` Guennadi Liakhovetski
2008-08-13 16:54 ` Robert Jarzmik
2008-08-13 17:12 ` Guennadi Liakhovetski
2008-08-13 17:20 ` Robert Jarzmik
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=873alnt2bh.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