From: Michael Trimarchi <michael@panicking.kicks-ass.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Antonio Ospite <ospite@studenti.unina.it>,
linux-media@vger.kernel.org,
Jean-Francois Moine <moinejf@free.fr>
Subject: Re: [RFC, PATCH] gspca: implement vidioc_enum_frameintervals
Date: Thu, 19 Nov 2009 10:00:21 +0100 [thread overview]
Message-ID: <4B050925.4000006@panicking.kicks-ass.org> (raw)
In-Reply-To: <4B04FCF6.2060505@redhat.com>
Hans de Goede wrote:
> Hi,
>
> On 11/17/2009 11:41 AM, Antonio Ospite wrote:
>> Hi,
>>
>> gspca does not implement vidioc_enum_frameintervals yet, so even if a
>> camera can support multiple frame rates (or frame intervals) there is
>> still no way to enumerate them from userspace.
>>
>> The following is just a quick and dirty implementation to show the
>> problem and to have something to base the discussion on. In the patch
>> there is also a working example of use with the ov534 subdriver.
>>
>> Someone with a better knowledge of gspca and v4l internals can suggest
>> better solutions.
>>
>
>
> Does the ov534 driver actually support selecting a framerate from the
> list this patch adds, and does it then honor the selection ?
The ov534 is a bridge for different sensor like ov538 so it support different
frame rate, depends on the sensor too.
Michael
next prev parent reply other threads:[~2009-11-19 9:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 10:41 [RFC, PATCH] gspca: implement vidioc_enum_frameintervals Antonio Ospite
2009-11-17 10:57 ` Michael Trimarchi
2009-11-19 8:08 ` Hans de Goede
2009-11-19 9:00 ` Michael Trimarchi [this message]
2009-11-19 9:27 ` Hans de Goede
2009-11-19 10:37 ` Antonio Ospite
2009-11-19 11:11 ` Hans de Goede
2009-11-19 11:48 ` Jean-Francois Moine
2009-12-01 15:39 ` [PATCH] " Antonio Ospite
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=4B050925.4000006@panicking.kicks-ass.org \
--to=michael@panicking.kicks-ass.org \
--cc=hdegoede@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=moinejf@free.fr \
--cc=ospite@studenti.unina.it \
/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