public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "christophe barbé" <christophe.barbe.ml@online.fr>
To: "Guus Sliepen" <guus@warande3094.warande.uu.nl>,
	lkml <linux-kernel@vger.kernel.org>,
	"christophe barbé" <christophe.barbe@ufies.org>
Subject: Re: usb-ohci, ov511, video4linux
Date: Sun, 20 Jan 2002 12:08:37 -0500	[thread overview]
Message-ID: <20020120170837.GD2873@online.fr> (raw)
In-Reply-To: <20020120154119.GB2873@online.fr> <20020120162258.GC16166@sliepen.warande.net>
In-Reply-To: <20020120162258.GC16166@sliepen.warande.net>

[-- Attachment #1: Type: text/plain, Size: 1705 bytes --]

On Sun, Jan 20, 2002 at 05:22:58PM +0100, Guus Sliepen wrote:
> On Sun, Jan 20, 2002 at 10:41:19AM -0500, christophe barbé wrote:
> 
> > The Xawtv outputs are interesting :
> > 
> > # xawtv
> > This is xawtv-3.68, running on Linux/i586 (2.4.17)
> > /dev/video0 [v4l]: no overlay support
> 
> That's normal.
> 
> > v4l-conf had some trouble, trying to continue anyway
> 
> That too, because of the earlier warning about overlay.
> 
> > v4l: timeout (got SIGALRM), hardware/driver problems?
> > ioctl: VIDIOCSYNC(0): Appel système interrompu
> > v4l: timeout (got SIGALRM), hardware/driver problems?
> > ioctl: VIDIOCSYNC(1): Appel système interrompu
> 
> xawtv has a very short timeout when it tries to grab frames. It really
> was made for TV cards, not webcams. You can either change xawtv's
> libng/grab-v4l.c and edit the line containing #define SYNC_TIMEOUT, or
> use a program like gqcam that is written especially for slow USB
> webcams.
> 
> The problems with the other USB devices might be caused by the fact that
> USB webcams will use all the available bandwidth.

I have the same problem with gqcam, camstream and gnomemeeting.
With xawtv and the debug option, the problem disapears. Perhaps the
timeout is increased in this case. I will check the code.

The problem with the usb mouse is there with or without webcam.

Christophe

> 
> -- 
> Met vriendelijke groet / with kind regards,
>   Guus Sliepen <guus@sliepen.warande.net>



-- 
Christophe Barbé <christophe.barbe@ufies.org>
GnuPG FingerPrint: E0F6 FADF 2A5C F072 6AF8  F67A 8F45 2F1E D72C B41E

Dogs come when they're called;
cats take a message and get back to you later. --Mary Bly

[-- Attachment #2: Type: application/pgp-signature, Size: 241 bytes --]

  reply	other threads:[~2002-01-20 17:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-20 15:41 usb-ohci, ov511, video4linux christophe barbé
2002-01-20 16:22 ` Guus Sliepen
2002-01-20 17:08   ` christophe barbé [this message]
2002-01-20 22:54     ` Greg KH
2002-01-20 23:04       ` christophe barbé

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=20020120170837.GD2873@online.fr \
    --to=christophe.barbe.ml@online.fr \
    --cc=christophe.barbe@ufies.org \
    --cc=guus@warande3094.warande.uu.nl \
    --cc=linux-kernel@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