From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Bastien Nocera <hadess@hadess.net>
Cc: linux-media@vger.kernel.org
Subject: Re: NTSC/PAL resolution support for "EasyCap" device
Date: Fri, 03 Jun 2016 01:37:18 +0300 [thread overview]
Message-ID: <2081548.sYXtIeXGjI@avalon> (raw)
In-Reply-To: <1464691129.3878.59.camel@hadess.net>
Hi Bastien,
(CC'ing the linux-media mailing list)
On Tuesday 31 May 2016 12:38:49 Bastien Nocera wrote:
> Hey,
>
> I saw your commits to add quirks for Arkmicro "webcams". I recently
> bought a dirt cheap "EasyCap" device on eBay, but it only seems to
> support 640x480 instead of the native "NRSC" resolution as mentioned on
> the device's box.
>
> $ v4l2-ctl --list-formats-ext -d /dev/video0
> ioctl: VIDIOC_ENUM_FMT
> Index : 0
> Type : Video Capture
> Pixel Format: 'MJPG' (compressed)
> Name : Motion-JPEG
> Size: Discrete 640x480
> Interval: Discrete 0.017s (60.000 fps)
> Interval: Discrete 0.033s (30.000 fps)
> Interval: Discrete 0.067s (15.000 fps)
> Interval: Discrete 0.200s (5.000 fps)
> Size: Discrete 352x288
> Interval: Discrete 0.017s (60.000 fps)
> Interval: Discrete 0.033s (30.000 fps)
> Interval: Discrete 0.067s (15.000 fps)
> Interval: Discrete 0.200s (5.000 fps)
>
> Device is:
> Bus 003 Device 066: ID 18ec:5850 Arkmicro Technologies Inc.
>
> In your professional opinion, should I try using UVC_QUIRK_PROBE_DEF
> or UVC_QUIRK_PROBE_MINMAX as a quirk for this device? Is there a stand-
> alone driver somewhere that I can use for testing (rather than
> recompiling a whole kernel)?
Those quirks will not affect the available resolutions.
UVC devices expose a list of resolutions they support through the USB
descriptors, and the uvcvideo device merely uses that list to expose supported
resolutions to userspace.
If the device doesn't expose resolutions other than the above two, the box
could be lying, or the device could use non-standard extensions to UVC to
support additional resolutions. The first step would be to try the camera in a
Windows machine to see if additional resolutions are available (without
installing any additional device-specific software).
> Let me know if you prefer that I send this to the media list.
Done :-)
--
Regards,
Laurent Pinchart
next parent reply other threads:[~2016-06-02 22:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1464691129.3878.59.camel@hadess.net>
2016-06-02 22:37 ` Laurent Pinchart [this message]
2016-06-03 10:53 ` NTSC/PAL resolution support for "EasyCap" device Bastien Nocera
2016-06-03 11:08 ` Laurent Pinchart
2016-06-03 11:35 ` Bastien Nocera
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=2081548.sYXtIeXGjI@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=hadess@hadess.net \
--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