From: "Vesa Jääskeläinen" <chaac@nic.fi>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Idea: move grub-emu to a separate platform
Date: Sat, 28 Mar 2009 09:08:44 +0200 [thread overview]
Message-ID: <49CDCCFC.5060909@nic.fi> (raw)
In-Reply-To: <ca0f59980903272336v45779452pa84bc8603f7d294@mail.gmail.com>
Bean wrote:
> Hi,
>
> Currently, the grub-emu is in every rmk files, but I don't see the
> difference between grub-emu in i386-pc, i386-coreboot or i386-efi. In
> fact, grub-emu runs inside the host os, it can't access firmware
> facility anyway. One quick fix to move grub-emu to i386.rmk, but we
> could also put it in a new platform altogether, something like
> i386-host.
>
> The advantage of using a separate platform is that we could now use
> modules like the other platform, instead of embedding all source files
> in grub-emu. For example, whenever we add a new command, we need to
> modify the source list of grub-emu. But if we build i386-host like
> other platform, we only need to change common.rmk.
>
> What's more, i386-host is not just a testing tool, it could be a real
> boot loader. kboot provides a minimum linux environment. We could use
> i386-host as a front end, and use kexec to launch additional boot
> files.
>
I think I have from time to time proposed this too :) So I am all for it :)
But my point was more to cleanup makefiles in sensible way and then on
PC to allow more advanced automated (module) testing.
next prev parent reply other threads:[~2009-03-28 7:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-28 6:36 Idea: move grub-emu to a separate platform Bean
2009-03-28 7:08 ` Vesa Jääskeläinen [this message]
2009-03-28 13:42 ` Robert Millan
2009-03-28 22:08 ` David Miller
2009-03-28 13:43 ` Robert Millan
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=49CDCCFC.5060909@nic.fi \
--to=chaac@nic.fi \
--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.