From: Lee Revell <rlrevell@joe-job.com>
To: ddstreet@ieee.org
Cc: David Brownell <david-b@pacbell.net>,
linux-usb-devel@lists.sourceforge.net,
Alan Stern <stern@rowland.harvard.edu>,
Bodo Eggert <7eggert@gmx.de>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: EHCI TT bandwidth (was Re: [PATCH] USB_BANDWIDTH documentation change)
Date: Thu, 29 Dec 2005 15:05:39 -0500 [thread overview]
Message-ID: <1135886739.6804.4.camel@mindpipe> (raw)
In-Reply-To: <Pine.LNX.4.51.0512291433090.27091@dylan.root.cx>
On Thu, 2005-12-29 at 14:41 -0500, Dan Streetman wrote:
> On Tue, 27 Dec 2005, David Brownell wrote:
>
> >(*) The issues folk have mentioned with bandwidth reservation for
> > EHCI are more "full and low speed devcies can't use all the
> > available transaction translator bandwidth" than anything else.
>
> The patches I just sent to the linux-usb-devel list (couple days ago) take
> care of those scheduling restrictions...do you have any comments on them?
> It would be great to get them in the kernel so EHCI can fully schedule any
> lowspeed or fullspeed buses that it manages. I even put the changes
> inside a kernel CONFIG option so people can test out the patches fully
> before replacing the old model.
>
How do I test them? Should this make USB audio work with
CONFIG_USB_BANDWIDTH?
Lee
next prev parent reply other threads:[~2005-12-29 19:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-26 10:25 [PATCH] USB_BANDWIDTH documentation change Bodo Eggert
2005-12-26 15:06 ` Lee Revell
2005-12-26 21:49 ` Bodo Eggert
2005-12-26 22:35 ` Alan Stern
2005-12-27 4:17 ` Greg KH
2005-12-27 17:02 ` [linux-usb-devel] " David Brownell
2005-12-27 16:57 ` David Brownell
2005-12-29 19:41 ` EHCI TT bandwidth (was Re: [PATCH] USB_BANDWIDTH documentation change) Dan Streetman
2005-12-29 20:05 ` Lee Revell [this message]
2005-12-30 19:13 ` [linux-usb-devel] " Dan Streetman
2005-12-30 19:16 ` Lee Revell
2005-12-29 20:12 ` David Brownell
2005-12-30 0:56 ` Dan Streetman
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=1135886739.6804.4.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=7eggert@gmx.de \
--cc=david-b@pacbell.net \
--cc=ddstreet@ieee.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.