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 platform and multiboot kernel
Date: Thu, 19 Jun 2008 00:23:13 +0200	[thread overview]
Message-ID: <20080618222313.GC24751@thorin> (raw)
In-Reply-To: <200806181959.22611.okuji@enbug.org>

On Wed, Jun 18, 2008 at 07:59:22PM +0200, Yoshinori K. Okuji wrote:
> On Wednesday 18 June 2008 08:27:09 Bean wrote:
> > On Wed, Jun 18, 2008 at 4:32 AM, David Holloway <daveh@dholloway.com> wrote:
> > > I've just edumacated myself about how the platforms are defined.
> > >
> > > Let me get this straight, the efi platform does not yet support loading a
> > > multiboot kernel?
> > >
> > > I'm working with embedded kernels here, not just Linux.
> >
> > Hi,
> >
> > It's not difficult to add multiboot support, but the question is, can
> > they support efi ? In linux, we can pass the efi system table using
> > boot parameter, but there is no such thing in multiboot, so the kernel
> > need to be able to access hardware directly after taking over.
> 
> Note that the Multiboot Specificatin 2 is designed to be capable of supporting 
> a wide range of platforms. All you must do is define the spec for EFI (and 
> implement it).

Wouldn't it be better to make it firmware-agnostic?  Then loadees can choose
to either be firmware-specific or (better, IMHO) use standalone drivers like
Linux and most kernels do.

-- 
Robert Millan

<GPLv2> I know my rights; I want my phone call!
<DRM> What good is a phone call… if you are unable to speak?
(as seen on /.)



      reply	other threads:[~2008-06-18 22:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200806171725.m5HHPQfx078913@shoebox.dholloway.com>
2008-06-17 20:32 ` efi platform and multiboot kernel David Holloway
2008-06-18  6:27   ` Bean
2008-06-18  6:43     ` Andrei E. Warkentin
2008-06-18  7:02       ` Bean
2008-06-18 17:59     ` Yoshinori K. Okuji
2008-06-18 22:23       ` 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=20080618222313.GC24751@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.