All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] change --enable-efiemu to --enable-efiemu64
Date: Sat, 18 Jul 2009 17:59:56 -0400	[thread overview]
Message-ID: <1247954396.3416.62.camel@mj> (raw)
In-Reply-To: <20090718183255.GF8867@thorin>

On Sat, 2009-07-18 at 20:32 +0200, Robert Millan wrote:
> On Fri, Jul 17, 2009 at 06:15:57PM +0200, Vladimir 'phcoder' Serbinenko wrote:
> > Like previously discussed efiemu32 can always be compiled hence this patch
> 
> This does a few more things than just toggle compile options.  Could you
> split the patch?

I second that.

Also, we need to look at things from the users' point of view.  Users
don't know what efiemu64 is and why it's so special that they are told
about it at the of the configure output.  Why it is more important that
efiemu32?  Why is efiemu64 only needed on the i386-pc platform?

I believe efiemu64 is only more important from the implementation point
of view, as it requires an additional test to be passed.  But most users
won't need efiemu64 at all.

If we add efiemu compilation to the x86_64-efi support, efiemu32 will be
special.  So it would be better to report something like "efiemu support
- 32-bit and 64-bit" if we care to report.

I suggest that you google for "The Paradox of Choice".  Sure, there are
difference between end users and those compiling GRUB from the sources,
but you'll get the idea.  Sometimes we should make the choice.

-- 
Regards,
Pavel Roskin



  reply	other threads:[~2009-07-18 22:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-17 16:15 [PATCH] change --enable-efiemu to --enable-efiemu64 Vladimir 'phcoder' Serbinenko
2009-07-18 18:32 ` Robert Millan
2009-07-18 21:59   ` Pavel Roskin [this message]
2009-08-28 15:48     ` 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=1247954396.3416.62.camel@mj \
    --to=proski@gnu.org \
    --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.