All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tristan Gingold <tgingold@free.fr>
To: The development of GRUB 2 <grub-devel@gnu.org>
Cc: summer-of-code@gnu.org, xiongyi <xiongyi04@gmail.com>
Subject: Re: Question about the GNU Grub ideas
Date: Fri, 23 Mar 2007 00:32:12 +0100	[thread overview]
Message-ID: <20070322233212.GC2498@saphi> (raw)
In-Reply-To: <873b3wlwq4.wl@dekkers.cx>

On Thu, Mar 22, 2007 at 11:49:55PM +0100, Jeroen Dekkers wrote:
> At Wed, 21 Mar 2007 14:58:54 -0800,
> xiongyi wrote:
[...]
> > 2.	The goal of grub2 for efi support is the same as the one of elilo,
> > namely an efi OS Loader (also an efi application, for example elilo.efi file
> > in the elilo project). Is that right?
>  
> Yes, the purpose is to load GRUB on EFI hardware so that GRUB can do
> all the things it normally does when you load it from standard x86
> BIOS.
Compared to elilo, grub2 can't boot from network.

> > 3.	There is a real EFI platform in my lab, but I will graduate and
> > leave that lab in this June. Accordingly, I have some considerations about
> > the development platform and environment. If the efi feature of grub2 is
> > only an efi OS loader, whether the EDK open source project can serve as the
> > development and debug platform. 
> 
> My experience is that while you can develop and test on such things,
> real hardware has subtle differences most of the time and you always
> need hardware to test whether it really works.
You may use qemu.

Tristan



  reply	other threads:[~2007-03-22 23:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4600d7ad.0fbdf68c.519b.057c@mx.google.com>
2007-03-22 22:49 ` Question about the GNU Grub ideas Jeroen Dekkers
2007-03-22 23:32   ` Tristan Gingold [this message]
2007-03-22 23:44   ` Yoshinori K. Okuji
2007-03-23  0:22     ` Jeroen Dekkers
2007-03-23  0:34       ` Yoshinori K. Okuji

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=20070322233212.GC2498@saphi \
    --to=tgingold@free.fr \
    --cc=grub-devel@gnu.org \
    --cc=summer-of-code@gnu.org \
    --cc=xiongyi04@gmail.com \
    /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.