All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] reset USB controller
Date: Tue, 1 Sep 2009 13:33:24 +0200	[thread overview]
Message-ID: <20090901113324.GA25290@thorin> (raw)
In-Reply-To: <4A9BD1F3.6000008@peda.net>

On Mon, Aug 31, 2009 at 04:36:51PM +0300, Mikko Rantalainen wrote:
> >> 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.

Working around broken BIOS or hardware can be ok.  It's putting burden on the
user what sounds problematic.

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."



      reply	other threads:[~2009-09-01 11:33 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
2009-09-01 11:33       ` Robert Millan [this message]

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=20090901113324.GA25290@thorin \
    --to=rmh@aybabtu.com \
    --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.