From: David Brownell <david-b@pacbell.net>
To: Gary_Lerhaupt@Dell.com
Cc: linux-usb-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, Stuart_Hayes@Dell.com
Subject: Re: [linux-usb-devel] [PATCH] proper bios handoff in ehci-hcd
Date: Tue, 15 Jun 2004 06:57:29 -0700 [thread overview]
Message-ID: <40CF0049.2010307@pacbell.net> (raw)
In-Reply-To: <FD3BA83843210C4BA9E414B0C56A5E5C07DD91@ausx2kmpc104.aus.amer.dell.com>
Gary_Lerhaupt@Dell.com wrote:
> Stuart Hayes here at Dell has identified this or/and mix-up in the
> ehci-hcd driver. Because of this, ehci-hcd is not properly released by
> BIOSes supporting full 2.0 and port behavior can then become erratic.
Good patch, it should be merged. That handoff code actually
predates general availability of BIOSes handling _any_ EHCI
controllers, and your patch resolves a problem I'd seen on a
newish board but hadn't yet had time to track down (beyond
knowing that broken BIOS handoff was the issue).
Thanks to you and Stuart!
- Dave
next prev parent reply other threads:[~2004-06-15 13:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-14 20:30 [PATCH] proper bios handoff in ehci-hcd Gary_Lerhaupt
2004-06-15 13:57 ` David Brownell [this message]
2004-07-13 5:30 ` Will Beers
[not found] ` <200407130744.22920.andjoh@rydsbo.net>
2004-07-13 6:16 ` Will Beers
2004-07-13 18:07 ` [linux-usb-devel] " Olaf Hering
2004-07-13 20:26 ` David Brownell
2004-07-13 20:44 ` Will Beers
2004-07-13 21:11 ` David Brownell
2004-07-13 21:24 ` Will Beers
2004-07-13 21:35 ` David Brownell
2004-07-13 21:43 ` Will Beers
2004-07-13 21:31 ` Will Beers
-- strict thread matches above, loose matches on Subject: below --
2004-07-13 20:52 Stuart_Hayes
2004-07-13 21:56 ` Pete Zaitcev
2004-07-13 23:04 ` David Brownell
2004-07-15 9:37 ` Olaf Hering
2004-08-05 13:39 ` Olaf Hering
2004-08-05 15:49 ` David Brownell
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=40CF0049.2010307@pacbell.net \
--to=david-b@pacbell.net \
--cc=Gary_Lerhaupt@Dell.com \
--cc=Stuart_Hayes@Dell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/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.