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] fix building bug with --enable-grub-emu-usb
Date: Sun, 21 Jun 2009 13:38:29 +0200	[thread overview]
Message-ID: <20090621113829.GG27710@thorin> (raw)
In-Reply-To: <1245426366.2820.2.camel@mj>

On Fri, Jun 19, 2009 at 11:46:06AM -0400, Pavel Roskin wrote:
> 
> Generally, please think how to reduce complexity, not how to add to it.
> Complex systems are harder to maintain.

In general, I completely agree with this.

However grub-emu has very special requirements that could make it desireable
sometimes.  Its purpose is to emulate GRUB as faithfully as possible to
uncover bugs so in general we want to use interfaces as lower as possible
_but_ it's sometimes useful to be able to isolate those bugs, which makes
options to choose between higher or lower interfaces also desireable.

For example, should we use our USB drivers against libusb, or should we
ditch libusb and use our *HCI controllers against libpci?  Should we use
our gfxterm against SDL, or should we use our own hardware drivers to
access the hardware (sort of) directly like X does?

I think we need some balance here, and decide on a case by case basis.

Anyway, given that grub-emu is a debugging/development tool, I'm not sure
it's that useful to export those flags to autoconf.  We could just live
with #ifdefs in the code IMHO.  Distributors are going to ship whatever we
choose as default for grub-emu anyway.

-- 
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."



  parent reply	other threads:[~2009-06-21 11:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-17 13:27 [PATCH] fix building bug with --enable-grub-emu-usb Vladimir 'phcoder' Serbinenko
2009-06-19 15:46 ` Pavel Roskin
2009-06-19 16:03   ` Vladimir 'phcoder' Serbinenko
2009-06-21 11:38   ` Robert Millan [this message]
2009-06-21 12:34     ` Vladimir 'phcoder' Serbinenko
2009-07-16 15:38       ` Vladimir 'phcoder' Serbinenko

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=20090621113829.GG27710@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.