Linux Media Controller development
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: New ctrl framework also enumerates classes
Date: Mon, 11 Jul 2011 16:31:04 +0200	[thread overview]
Message-ID: <4E1B0928.6080300@redhat.com> (raw)
In-Reply-To: <201107040830.58788.hverkuil@xs4all.nl>

Hi,

On 07/04/2011 08:30 AM, Hans Verkuil wrote:
> On Monday, July 04, 2011 08:23:10 Hans de Goede wrote:
>> Hi All,
>>
>> One last thing before I really leave on vacation which just popped
>> in my mind as something which I had not mentioned yet.
>>
>> The new ctrl framework also enumerates classes when enumerating
>> ctrls with the next flag. I wonder if this is intentional?
>
> It's absolutely intentional. It's needed to produce the headers of the
> tabs in e.g. qv4l2. It's been part of the spec for several years now.
>
>> IOW if this is a feature or a bug?
>>
>> Either way this confuses various userspace apps, gtk-v4l prints
>> warnings about an unknown control type,
>
> It should just skip such types.
>
>> and v4l2ucp gets a very
>> messed up UI because of this change. Thus unless there are
>> really strong reasons to do this, I suggest we skip classes
>> when enumerating controls.
>
> Those apps should be fixed. If apps see an unknown type, then they should
> always just skip such controls (and later add support for it, of course).

Ok, I will fix those apps (for gtk-v4l I'm involved upstream, for v4l2ucp
I'll fix it for Fedora and submit a patch upstream).

Regards,

Hans

      reply	other threads:[~2011-07-11 14:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-04  6:23 New ctrl framework also enumerates classes Hans de Goede
2011-07-04  6:30 ` Hans Verkuil
2011-07-11 14:31   ` Hans de Goede [this message]

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=4E1B0928.6080300@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=hverkuil@xs4all.nl \
    --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