From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: grub-devel@gnu.org
Cc: summer-of-code@gnu.org, Jeroen Dekkers <jeroen@vrijschrift.org>,
xiongyi <xiongyi04@gmail.com>
Subject: Re: Question about the GNU Grub ideas
Date: Fri, 23 Mar 2007 00:44:16 +0100 [thread overview]
Message-ID: <200703230044.16884.okuji@enbug.org> (raw)
In-Reply-To: <873b3wlwq4.wl@dekkers.cx>
On Thursday 22 March 2007 23:49, Jeroen Dekkers wrote:
> > I am a potential student applicant for the "Google-summer -of -code"
> > program. And I am strongly interested in the GNU Grub project, especially
> > for the porting grubs to the EFI-based PC platform idea. But there are
> > few messages or information about EFI porting for grub2. So I have some
> > questions about this idea.
>
> I don't have any experience with EFI, but as far as I know GRUB2
> already boots on intel macs and other EFI-based x86 machines. Although
> it probably still needs a lot of work, that isn't going to be enough
> for a Summer of Code project.
Why not enough? EFI has a significant amount of share in the market, and I see
nothing bad with working on EFI stuff.
I have already written the status in the wiki:
http://grub.enbug.org/TestingOnEFI
In addition, we need Multiboot support on EFI as well.
> 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.
Definitely. You can use emulators for development, but you need real hardware
at some point. Note that the payment from SoC is good enough to buy a Mac
Mini, for example.
Okuji
next prev parent reply other threads:[~2007-03-22 23:46 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
2007-03-22 23:44 ` Yoshinori K. Okuji [this message]
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=200703230044.16884.okuji@enbug.org \
--to=okuji@enbug.org \
--cc=grub-devel@gnu.org \
--cc=jeroen@vrijschrift.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.