From: Matthieu CASTET <matthieu.castet@parrot.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: video4linux-list@redhat.com
Subject: Re: soc-camera : add new flags
Date: Thu, 18 Dec 2008 14:13:55 +0100 [thread overview]
Message-ID: <494A4C93.4040202@parrot.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0812181219100.5510@axis700.grange>
Guennadi Liakhovetski a écrit :
> On Thu, 18 Dec 2008, Matthieu CASTET wrote:
>
>> Hi,
>>
>> I am trying to use soc-camera for our camera IP.
>>
>> Our IP allow to chose if the synchronization is done according to ITU-R
>> BT601 or ITU-R BT656.
>> Can new flag be added to negotiate the synchronization standard between
>> host and sensor.
>
> Yes, sure, send a patch. Just add required
> SOCAM_SYNC_{GATED,NONGATED,BT601,BT656} (or whatever you'd like to call
> them) flags, and extend soc_camera_bus_param_compatible() to verify them.
>
Ok
>> Our IP also allow to select if the data on the bus is transmitted on the
>> CbYCrY order or YCbYCr order.
>> Can new flag be added to negotiate the synchronization standard between
>> host and sensor.
>
> Different statement but the same question? If you wanted to ask about
> colour format then just use different YUYV / UYVY / ... fourcc codes.
How do you differentiate color format of the bus and the color format
output by v4l ?
In our case the bus format can be YUYV or UYVY, but the host camera IP
can only output YUV422P/YUV420/YVU420.
Matthieu
--
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-12-18 13:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 9:17 soc-camera : add new flags Matthieu CASTET
2008-12-18 11:26 ` Guennadi Liakhovetski
2008-12-18 13:13 ` Matthieu CASTET [this message]
2008-12-18 13:40 ` Guennadi Liakhovetski
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=494A4C93.4040202@parrot.com \
--to=matthieu.castet@parrot.com \
--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 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.