From: David Brownell <david-b@pacbell.net>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: Stuart_Hayes@Dell.com, whbeers@mbio.ncsu.edu, olh@suse.de,
Gary_Lerhaupt@Dell.com, linux-usb-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] [PATCH] proper bios handoff in ehci-hcd
Date: Tue, 13 Jul 2004 16:04:31 -0700 [thread overview]
Message-ID: <40F46A7F.5000703@pacbell.net> (raw)
In-Reply-To: <20040713145628.27ae43e7@lembas.zaitcev.lan>
Pete Zaitcev wrote:
> I hit regressions when we implemented the proper handoff as requested
> by Stuart @Dell, so I think for the moment the right thing would be this:
>
> --- linux-2.4.21-15.18.EL/drivers/usb/host/ehci-hcd.c 2004-07-01
> 08:07:56.000000000 -0700
> +++ linux-2.4.21-15.18-usb/drivers/usb/host/ehci-hcd.c 2004-07-08
> 15:15:05.944863675 -0700
> @@ -302,7 +302,8 @@
> if (cap & (1 << 16)) {
> ehci_err (ehci, "BIOS handoff failed (%d, %04x)\n",
> where, cap);
> - return 1;
> + pci_write_config_dword (ehci->hcd.pdev, where, 0);
> + return 0;
> }
> ehci_dbg (ehci, "BIOS handoff succeeded\n");
> }
>
> Essentially, here I insist on doing the right thing with cap|=(1<<24),
> which fixes Dell boxes which implement proper handoff, but then if we
> time out as on Thinkpads, write zero as the old code did (probably
> pointless, but just to be safe) and continue.
I'd rather not change the config space again ... that's clearly wrong.
Or is there some policy about what sorts of BIOS bugs we should assume?
Instead, how about: (a) longer timeout, 5 seconds to match OHCI's
absurdly long default there; (b) change that "handoff failed" message
to add "continuing anyway"; and (c) return 0 as you do, which I'm
expecting is the key part of that patch.
That'll evidently work for Will, as well as correctly functioning hardware
with EHCI-aware BIOS (the Dell boxes and the AMI BIOS box I tested) also
the classic EHCI-unaware BIOS setups.
- Dave
next prev parent reply other threads:[~2004-07-13 23:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-13 20:52 [linux-usb-devel] [PATCH] proper bios handoff in ehci-hcd Stuart_Hayes
2004-07-13 21:56 ` Pete Zaitcev
2004-07-13 23:04 ` David Brownell [this message]
2004-07-15 9:37 ` Olaf Hering
2004-08-05 13:39 ` Olaf Hering
2004-08-05 15:49 ` David Brownell
-- strict thread matches above, loose matches on Subject: below --
2004-06-14 20:30 Gary_Lerhaupt
2004-06-15 13:57 ` [linux-usb-devel] " David Brownell
2004-07-13 18:07 ` 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
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=40F46A7F.5000703@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 \
--cc=olh@suse.de \
--cc=whbeers@mbio.ncsu.edu \
--cc=zaitcev@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