public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean <knife@toaster.net>
To: bifferos <bifferos@yahoo.co.uk>
Cc: linux-media@vger.kernel.org
Subject: Re: libv4l2: error dequeuing buf: Input/output error
Date: Sun, 15 Nov 2009 18:31:36 -0800	[thread overview]
Message-ID: <4B00B988.4090401@toaster.net> (raw)
In-Reply-To: <865524.48833.qm@web27006.mail.ukl.yahoo.com>

There have been some improvements to gspca_main and gspca_pac207 
recently, as well as pac207 specific improvements in libv4l2. Are you 
using the latest v4l-dvb and libv4l2? I get some slowdown halfway when 
using capture-example.c and it seems to improve when I use the latest 
v4l-dvb and libv4l2 from mercurial. http://linuxtv.org/hg/v4l-dvb

Sean

bifferos wrote:
> Hi all,
>
> Can anyone give any clue as to why I might get this error 
> when capturing from a PAC207 webcam?  It happens after a 6-7 
> second delay when capturing.
>
> I've seen this with 2.6.30.1, 2.6.30.5 and 2.6.32-rc7, however 
> I can run the same camera on another (much faster) system using 
> the same kernel(s) and same gspca driver and it works fine, 
> making me think this is a timing issue.
>
> I'm testing with the v4lgrab.c program, compiled statically 
> against libv4l2.  A quick google indicates I'm not the only
> one encountering the problem. 
>
> thanks,
> Biff.
>
>
>       
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>   

      reply	other threads:[~2009-11-16  2:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-15 21:08 libv4l2: error dequeuing buf: Input/output error bifferos
2009-11-16  2:31 ` Sean [this message]

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=4B00B988.4090401@toaster.net \
    --to=knife@toaster.net \
    --cc=bifferos@yahoo.co.uk \
    --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