From: Lee Revell <rlrevell@joe-job.com>
To: Markus Rechberger <mrechberger@gmail.com>
Cc: Linux and Kernel Video <video4linux-list@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: usb bandwidth allocation issue using 2 pvr devices (em28xx driver) v4l2
Date: Fri, 03 Feb 2006 01:21:01 -0500 [thread overview]
Message-ID: <1138947662.15691.241.camel@mindpipe> (raw)
In-Reply-To: <d9def9db0602022149o1561e1b7v9c191c873d5add46@mail.gmail.com>
On Fri, 2006-02-03 at 06:49 +0100, Markus Rechberger wrote:
> Hi!
>
> this should be addressed to USB subsystem developers, I also
> reproduced this issue.
> The problem is the isochronous transfer in em28xx-core.c I'm quite
> sure it's correct and the bug is somewhere deeper in the USB
> subsystem.
Is USB bandwidth checking enabled? It's known to be broken, and should
be disabled by default...
Lee
prev parent reply other threads:[~2006-02-03 6:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c967fb330602022139o77fe09d1k7149648b1afdc695@mail.gmail.com>
2006-02-03 5:49 ` usb bandwidth allocation issue using 2 pvr devices (em28xx driver) v4l2 Markus Rechberger
2006-02-03 6:21 ` Lee Revell [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=1138947662.15691.241.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mrechberger@gmail.com \
--cc=video4linux-list@redhat.com \
/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