From: David Brownell <david-b@pacbell.net>
To: Lee Revell <rlrevell@joe-job.com>
Cc: kus Kusche Klaus <kus@keba.com>,
stern@rowland.harvard.edu, linux-usb-users@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.11, USB: High latency?
Date: Wed, 30 Mar 2005 17:40:49 -0800 [thread overview]
Message-ID: <200503301740.49647.david-b@pacbell.net> (raw)
In-Reply-To: <1112232746.19975.41.camel@mindpipe>
On Wednesday 30 March 2005 5:32 pm, Lee Revell wrote:
> On Wed, 2005-03-30 at 17:28 -0800, David Brownell wrote:
> > On Wednesday 30 March 2005 4:51 pm, Lee Revell wrote:
> > >
> > > This is the exact configuration of one of the users who reported the
> > > problem on LAU. Got a pointer to the patch? And what's the issue with
> > > IN transfers?
> >
> > This is what Greg just posted (and Linus merged into BK, so it'll be
> > in BK snapshots starting tomorrow):
> >
> > http://marc.theaimsgroup.com/?l=linux-usb-devel&m=111221966815043&w=2
> >
> > The issue with IN transfers is that microframe scheduling is ... tricky.
> > ...
>
> Thanks for the explanation. I found this patch, and sent the link to
> the LAU posters with the problem.
>
> There are apparently many users affected (some gave up and went back to
> 2.4), so there's good opportunity for testing.
Yes. That's why I was particularly glad to see the patches from Karsten;
they were the first ones that actually got "it works for me now!!" reports.
With luck, all full speed ISO-OUT transfers will now work through EHCI.
Even through the funky multi-TT hubs from Cypress. My main question is
whether this is also true of the TDI (nee ARC) EHCI silicon that's being
embedded in various non-PCI chips.
This all seems off-topic for latency though. :)
- Dave
> > I'd like to see all that split ISO stuff working with EHCI, but someone
> > else is going to have to do most of the work. Once it's working we can
> > take the CONFIG_EXPERIMENTAL off, which will remove another source of
> > errors. :)
>
> Thanks again for your help, I'll report any interesting results.
>
> Lee
>
>
next prev parent reply other threads:[~2005-03-31 1:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-30 22:57 2.6.11, USB: High latency? David Brownell
2005-03-31 0:43 ` Lee Revell
2005-03-31 1:13 ` David Brownell
2005-03-31 1:21 ` Lee Revell
2005-03-31 1:32 ` David Brownell
2005-03-31 0:51 ` Lee Revell
2005-03-31 1:28 ` David Brownell
2005-03-31 1:32 ` Lee Revell
2005-03-31 1:40 ` David Brownell [this message]
2005-03-31 1:44 ` Lee Revell
2005-03-31 1:39 ` Lee Revell
-- strict thread matches above, loose matches on Subject: below --
2005-04-04 8:03 kus Kusche Klaus
2005-04-04 8:36 ` Ingo Molnar
2005-04-04 19:40 ` Alan Stern
2005-04-01 13:16 kus Kusche Klaus
2005-04-01 13:41 ` Ingo Molnar
2005-04-01 6:46 kus Kusche Klaus
2005-04-01 17:20 ` Alan Stern
2005-03-31 12:12 kus Kusche Klaus
2005-03-31 11:15 kus Kusche Klaus
2005-03-31 16:48 ` Alan Stern
2005-03-30 13:51 kus Kusche Klaus
2005-03-30 15:55 ` Alan Stern
2005-03-30 21:28 ` Lee Revell
2005-03-31 11:30 ` Ingo Molnar
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=200503301740.49647.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=kus@keba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-users@lists.sourceforge.net \
--cc=rlrevell@joe-job.com \
--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