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: EFI through virtualization?
Date: Sat, 7 Feb 2009 21:48:49 +0100	[thread overview]
Message-ID: <20090207204849.GI988@thorin> (raw)
In-Reply-To: <9f50a7a00901112110g7b7efac7p51435322a07c8045@mail.gmail.com>

On Sun, Jan 11, 2009 at 11:10:25PM -0600, Jerone Young wrote:
> You guys wouldn't happen to know any good ways to test out EFI through
> virtualization. I see some Qemu stuff that is rather old. But I'm not too
> trusting of it's funcationality now. I'd like to play around and test/debug
> some of the grub2 efi support, without having to buy a Mac. Any ideas?

I wouldn't be overly concerned about hacking on EFI unless you're going to
use it yourself.  Keep in mind that EFI is a proprietary system (even moreso
than BIOS).  It's good that EFI users are able to run GRUB on it, and that
GRUB works well for them, but we shouldn't consider EFI one of our first
priorities IMO.

The FSF is actively endoring free firmware like coreboot instead:

  http://www.fsf.org/campaigns/free-bios.html

  (note this text also mentions EFI)

I'm not a GRUB maintainer, but being a GNU project I think our priority after
i386/BIOS should be supporting coreboot.  I expect the maintainers would agree
with that.

That said, it's your time not mine.

-- 
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-02-07 20:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-12  5:10 EFI through virtualization? Jerone Young
2009-02-07 20:48 ` 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=20090207204849.GI988@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.