From: Olaf Hering <olh@suse.de>
To: David Brownell <david-b@pacbell.net>
Cc: Pete Zaitcev <zaitcev@redhat.com>,
Stuart_Hayes@Dell.com, whbeers@mbio.ncsu.edu,
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: Thu, 5 Aug 2004 15:39:14 +0200 [thread overview]
Message-ID: <20040805133914.GA8844@suse.de> (raw)
In-Reply-To: <20040715093704.GA30351@suse.de>
On Thu, Jul 15, Olaf Hering wrote:
> On Tue, Jul 13, David Brownell wrote:
>
> > 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.
David, what is the status with this bios problem?
Can a patch like this patch go in?
What could we lose if the error is ignored?
> diff -purN linux-2.6.8-rc1-bk3.bios-handoff/drivers/usb/host/ehci-hcd.c linux-2.6.8-rc1-bk3/drivers/usb/host/ehci-hcd.c
> --- linux-2.6.8-rc1-bk3.bios-handoff/drivers/usb/host/ehci-hcd.c 2004-07-15 11:24:14.000000000 +0200
> +++ linux-2.6.8-rc1-bk3/drivers/usb/host/ehci-hcd.c 2004-07-15 11:32:28.463930957 +0200
> @@ -303,9 +303,11 @@ static int bios_handoff (struct ehci_hcd
> pci_read_config_dword(pdev, where, &cap);
> } while ((cap & (1 << 16)) && msec);
> if (cap & (1 << 16)) {
> - ehci_err (ehci, "BIOS handoff failed (%d, %04x)\n",
> + ehci_err (ehci, "BIOS handoff failed (%d, %04x)\n"
> + " Devices connected to this controller will not work correctly.\n"
> + " Complain to your BIOS vendor.\n", /* Really! */
> where, cap);
> - return 1;
> + return 0;
> }
> ehci_dbg (ehci, "BIOS handoff succeeded\n");
> }
--
USB is for mice, FireWire is for men!
sUse lINUX ag, nÜRNBERG
next prev parent reply other threads:[~2004-08-05 13:43 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
2004-07-15 9:37 ` Olaf Hering
2004-08-05 13:39 ` Olaf Hering [this message]
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=20040805133914.GA8844@suse.de \
--to=olh@suse.de \
--cc=Gary_Lerhaupt@Dell.com \
--cc=Stuart_Hayes@Dell.com \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--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