Linux-Media Archive on lore.kernel.org
 help / color / Atom feed
From: Gregor Jasny <gjasny@googlemail.com>
To: folkert@vanheusden.com, 929262@bugs.debian.org,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	Hans Verkuil <hverkuil@xs4all.nl>
Subject: Re: Bug#929262: libv4l-dev: pac207 cam(s) give frame decode errors
Date: Mon, 20 May 2019 13:38:56 +0200
Message-ID: <c2d8869f-4ca5-7f70-1c0e-44d4c1e094f4@googlemail.com> (raw)
In-Reply-To: <155834073601.757.12828508994068038463.reportbug@scrollert>

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?

Thanks,
Gregor

       reply index

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <155834073601.757.12828508994068038463.reportbug@scrollert>
2019-05-20 11:38 ` Gregor Jasny [this message]
2019-05-20 11:55   ` Hans Verkuil
2019-05-20 19:23     ` folkert

Reply instructions:

You may reply publically 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=c2d8869f-4ca5-7f70-1c0e-44d4c1e094f4@googlemail.com \
    --to=gjasny@googlemail.com \
    --cc=929262@bugs.debian.org \
    --cc=folkert@vanheusden.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

Linux-Media Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-media/0 linux-media/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-media linux-media/ https://lore.kernel.org/linux-media \
		linux-media@vger.kernel.org linux-media@archiver.kernel.org
	public-inbox-index linux-media


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-media


AGPL code for this site: git clone https://public-inbox.org/ public-inbox