From: Mikko Rantalainen <mikko.rantalainen@peda.net>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] reset USB controller
Date: Mon, 31 Aug 2009 16:36:51 +0300 [thread overview]
Message-ID: <4A9BD1F3.6000008@peda.net> (raw)
In-Reply-To: <d7ead6de0908281341q24625c95g26cc2f6748f5356b@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1778 bytes --]
Vladimir 'phcoder' Serbinenko wrote:
> On Thu, Jul 16, 2009 at 5:56 PM, Robert Millan<rmh@aybabtu.com> wrote:
>> On Wed, Jul 15, 2009 at 10:51:55PM +0200, Vladimir 'phcoder' Serbinenko wrote:
>>> Hello, some BIOSes don't conform semaphore specification about handing
>>> over the control on UHCI and/or EHCI controller. Most OS cope with it
>>> by taking ownership regardless after some timeout. This however
Please, notice that the EHCI specification does not not specify the
required timeout. Especially, there's no timeout after which the forced
taking of ownership is safe.
See http://bugzilla.kernel.org/show_bug.cgi?id=12148 for further discussion.
Notice that once mainstream grub deals with USB keyboards without BIOS
support, the obvious fix is to disable the (buggy) USB legacy support in
the BIOS.
The other obvious fix would be to upgrade to non-buggy BIOS version but
unless your BIOS vendor fixes the issue, that's not really an option.
>> Is there some way we can make this simpler without compromising on boot
>> speed? Adding more setup burden to the user should be the last ressort
>> IMO.
>>
> [...]
> Another usage is if OS doesn't deal with situation correctly.
> [...]
> If you consider this patch too hackish it can stay in my repo and
> people who really need can be said to use my repo or external module.
> If you consider this tweak possibility reasonable we can merge it
I don't know if the code quality is up to the requirements for getting
in the official trunk but I don't think that any method to deal with
broken BIOS or hardware cannot be too hackish. If the hardware (and this
includes the firmware) is broken and there's some hack that can make it
usable, just apply the hack. IMHO.
--
Mikko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-08-31 13:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 20:51 [PATCH] reset USB controller Vladimir 'phcoder' Serbinenko
2009-07-15 20:53 ` Vladimir 'phcoder' Serbinenko
2009-07-16 15:56 ` Robert Millan
2009-08-28 20:41 ` Vladimir 'phcoder' Serbinenko
2009-08-31 13:36 ` Mikko Rantalainen [this message]
2009-09-01 11:33 ` Robert Millan
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=4A9BD1F3.6000008@peda.net \
--to=mikko.rantalainen@peda.net \
--cc=grub-devel@gnu.org \
/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.