From: Lamarque Vieira Souza <lamarque@gmail.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: video4linux-list@redhat.com
Subject: Re: Skype and libv4
Date: Thu, 26 Mar 2009 10:36:56 -0300 [thread overview]
Message-ID: <200903261036.57317.lamarque@gmail.com> (raw)
In-Reply-To: <49CB4D4E.6030901@redhat.com>
Em Thursday 26 March 2009, Hans de Goede escreveu:
> Hi all,
>
> Not quite, the correct behaviour is:
> "If the field value is set to an unsupported value, then set the field
> value to *a* value that the driver accepts"
Now I get it. This webcam only accepts V4L2_FIELD_NONE, so commenting that
part of try_fmt makes it compliant with v4l2 standard. Thank you for helping
me with this. The zr364xx's maintainer contacted me yesterday, he is busy
theses days, when he has more time he is going to take a look at my changes.
With lucky the changes will be in 2.6.30. At least 2.6.29 sets the
compat_ioctl32 automatically for all drivers, in 2.6.28.8 I had to set it in
the driver to make Skype and mplayer (32-bit) work, one less change for the
driver :-)
> This takes in to account certain devices can support multiple field types,
> which is the whole purpose of the field value.
>
> And yes unfortunately many many v4l drivers have various bugs in their
> implementation, in some cases I do work around driver bugs in libv4l, but
> it this case that would hurt proper use of the field value, and that is not
> acceptable, so fixing the driver is the only solution.
Have you tried to contact the drivers' maintainers for fixing those bugs?
> Note, that the v4l2 API is pretty well documented, and the correct
> behaviour as I describe it can be found in the docs too:
> http://www.linuxtv.org/downloads/video4linux/API/V4L2_API/spec/r10944.htm
>
> And the "Return Value" section, note how EINVAL is only supposed to be
> returned up on an invalid, or unsupported type value. And also from the
> description: "Drivers should not return an error code unless the input is
> ambiguous"
--
Lamarque V. Souza
http://www.geographicguide.com/brazil.htm
Linux User #57137 - http://counter.li.org/
--
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:[~2009-03-26 13:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 20:08 Skype and libv4l Lamarque Vieira Souza
2009-03-24 9:59 ` Hans de Goede
2009-03-24 16:11 ` Lamarque Vieira Souza
2009-03-24 18:42 ` Lamarque Vieira Souza
2009-03-24 18:58 ` Markus Rechberger
2009-03-24 18:59 ` Markus Rechberger
2009-03-24 19:05 ` Lamarque Vieira Souza
2009-03-24 20:51 ` Theodoros V. Kalamatianos
2009-03-24 21:10 ` Lamarque Vieira Souza
2009-03-24 22:09 ` Skype and libv4 Lamarque Vieira Souza
2009-03-24 22:29 ` Lamarque Vieira Souza
2009-03-25 9:03 ` Hans de Goede
2009-03-25 14:17 ` Lamarque Vieira Souza
[not found] ` <49CB4D4E.6030901@redhat.com>
2009-03-26 13:36 ` Lamarque Vieira Souza [this message]
[not found] <20090326160017.048668E03F1@hormel.redhat.com>
2009-03-26 16:42 ` dean
2009-03-27 1:31 ` Lamarque Vieira Souza
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=200903261036.57317.lamarque@gmail.com \
--to=lamarque@gmail.com \
--cc=hdegoede@redhat.com \
--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