public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	linux-usb-devel@lists.sourceforge.net
Subject: Re: [linux-usb-devel] CONFIG_USB_BANDWIDTH broken
Date: Sun, 25 Dec 2005 23:17:17 -0500	[thread overview]
Message-ID: <1135570637.8293.26.camel@mindpipe> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0512252253350.15623-100000@netrider.rowland.org>

On Sun, 2005-12-25 at 22:58 -0500, Alan Stern wrote:
> On Sun, 25 Dec 2005, Lee Revell wrote:
> 
> > CONFIG_USB_BANDWIDTH breaks USB audio.  This has been a problem for at
> > least 6 months.
> > 
> > Typical bug report:
> > 
> > https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1642
> > 
> > (search bug tracker for CONFIG_USB_BANDWIDTH to see many more)
> > 
> > Is anyone working on fixing this?
> 
> The bug reports don't mention which USB host controller driver was being 
> used.
> 
> 	With ohci-hcd, bandwidth enforcement works okay.
> 
> 	With ehci-hcd, there are problems involved with scheduling
> 	periodic transfers to a full-speed device connected through
> 	a high-speed hub.  These problems are slowly being fixed.
> 
> 	With uhci-hcd, bandwidth enforcement has never worked.  New
> 	changes to the driver (accepted just a few days ago) will
> 	permit this to be fixed eventually.  It might take a few months
> 	(plus the time required for the changes to be added to the
> 	official distribution kernel).

Thanks, I'll try to get this info from the users.

So the solution for now is to educate users not to use it (and
especially, distros not to enable it).

Lee


  reply	other threads:[~2005-12-26  4:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-26  1:48 CONFIG_USB_BANDWIDTH broken Lee Revell
2005-12-26  3:58 ` [linux-usb-devel] " Alan Stern
2005-12-26  4:17   ` Lee Revell [this message]
2005-12-26  4:18     ` Alan Stern

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=1135570637.8293.26.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=stern@rowland.harvard.edu \
    /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