From: Hans Verkuil <hverkuil@xs4all.nl>
To: Gregor Jasny <gjasny@googlemail.com>,
folkert@vanheusden.com, 929262@bugs.debian.org,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: Bug#929262: libv4l-dev: pac207 cam(s) give frame decode errors
Date: Mon, 20 May 2019 13:55:35 +0200 [thread overview]
Message-ID: <d5e3d25f-4df3-9aee-a212-4ad64d3c1fd7@xs4all.nl> (raw)
In-Reply-To: <c2d8869f-4ca5-7f70-1c0e-44d4c1e094f4@googlemail.com>
On 5/20/19 1:38 PM, Gregor Jasny wrote:
> Hello,
>
> On 20.05.19 10:25, folkert@vanheusden.com wrote:
>> Trying to get a pac207 camera to work with constatus.
>>
>> 2019-05-20 10:22:34.864900 INFO constatus [1-1] source v4l2 thread started
>> libv4l2: error got 4 consecutive frame decode errors, last error: v4l-convert: error unknown pac207 row header: 0x0000
>> 2019-05-20 10:22:35.597949 ERROR cs:src_v4l2 [1-1] VIDIOC_DQBUF failed: Input/output error
>> ioctl(VIDIOC_QBUF) failed
>> errno: 22 (Invalid argument)
>>
>> To verify that it is not a constatus-problem I also tried a raspberry-pi camera via its video4linux-interface and that works fine.
>
> According to the Linux Kernel Maintainers file the device driver is
> maintained by Hans, which I CC'ed on this bug report:
>
> GSPCA PAC207 SONIXB SUBDRIVER
> M: Hans Verkuil <hverkuil@xs4all.nl>
> L: linux-media@vger.kernel.org
> T: git git://linuxtv.org/media_tree.git
> S: Odd Fixes
> F: drivers/media/usb/gspca/pac207.c
>
> Did your camera ever work on another Kernel, CPU architecture, or
> v4l-utils version? Do you have anything suspicious in dmesg output?
I strongly recommend that you buy a new webcam. This is ancient hardware.
Even the cheapest UVC webcams you can buy today will have far better
quality than a pac207. If you really, really need this to work, then I
need the full dmesg output and you also need to check if you can reproduce
this issue with the v4l2-ctl command:
v4l2-ctl -d /dev/videoX --stream-mmap
(it keeps capturing frames until you press ctrl-X)
I should have one of these webcams, but won't be able to test until next
week.
Regards,
Hans
next prev parent reply other threads:[~2019-05-20 11:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <155834073601.757.12828508994068038463.reportbug@scrollert>
2019-05-20 11:38 ` Bug#929262: libv4l-dev: pac207 cam(s) give frame decode errors Gregor Jasny
2019-05-20 11:55 ` Hans Verkuil [this message]
2019-05-20 19:23 ` folkert
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=d5e3d25f-4df3-9aee-a212-4ad64d3c1fd7@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=929262@bugs.debian.org \
--cc=folkert@vanheusden.com \
--cc=gjasny@googlemail.com \
--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;
as well as URLs for NNTP newsgroup(s).