From: Andy Walls <awalls@md.metrocast.net>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media@vger.kernel.org
Subject: Re: v4l2-compliance utility
Date: Fri, 21 Jan 2011 18:35:19 -0500 [thread overview]
Message-ID: <1295652919.2474.14.camel@localhost> (raw)
In-Reply-To: <201101212337.54213.hverkuil@xs4all.nl>
On Fri, 2011-01-21 at 23:37 +0100, Hans Verkuil wrote:
> Hi all,
>
> As you may have seen I have been adding a lot of tests to the v4l2-compliance
> utility in v4l-utils lately. It is now getting to the state that is becomes
> quite useful even though there is no full coverage yet.
>
> Currently the following ioctls are being tested:
Hans,
This is a great thing to have. Thanks!
> Also tested is whether you can open device nodes multiple times.
>
> These tests are pretty exhaustive and more strict than the spec itself.
OK, so multiple open is not strictly required by the spec, IIRC. If you
check the ivtv /dev/radio node, it does not allow multiple open, IIRC,
so it should not get OK for that test.
I also think during the subdev conversion, some of the less popular ivtv
cards with GPIO controlled radio audio may have been broken (and still
not fixed yet :( ), but working for the PVR-150, PVR-500, etc..
The DEBUG ioctl()s can be compiled out too.
So for someone making decisions based on the output of this tool:
1. if something comes back as "Not supported", that still means the
driver is API specification compliant, right?
2. could it be the case that this compliance tool will be sensitive to
the driver/hardware combination and not the driver alone?
Regards,
Andy
next prev parent reply other threads:[~2011-01-21 23:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 22:37 v4l2-compliance utility Hans Verkuil
2011-01-21 23:35 ` Andy Walls [this message]
2011-01-22 8:52 ` Hans Verkuil
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=1295652919.2474.14.camel@localhost \
--to=awalls@md.metrocast.net \
--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 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.