From: Matt Fleming <matt@console-pimps.org>
To: Darren Hart <dvhart@linux.intel.com>
Cc: "koen@dominion.thruhere.net" <koen@dominion.thruhere.net>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/3] classes: Add gummiboot class
Date: Wed, 12 Mar 2014 09:39:42 +0000 [thread overview]
Message-ID: <20140312093942.GD5834@console-pimps.org> (raw)
In-Reply-To: <CF44C1BC.76A1B%dvhart@linux.intel.com>
On Tue, 11 Mar, at 01:38:08PM, Darren Hart wrote:
>
> I'm surprised gummiboot requires STUB... Since STUB is there to allow the
> kernel to be booted directly, no bootloader required. I guess gummiboot is
> slightly less than a boot loader :-)
Gummiboot is an EFI application loader.
Since CONFIG_EFI_STUB sticks a PE/COFF header at the front of the
bzImage, it appears as an EFI application which gummiboot knows how to
load and run. This is also the reason you can execute the bzImage from
the EFI shell (or Boot Manager).
--
Matt Fleming, Intel Open Source Technology Center
prev parent reply other threads:[~2014-03-12 9:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 18:15 [PATCH 0/3] Add gummiboot boot manager alongside grub-efi Stefan Stanacar
2014-03-06 18:15 ` [PATCH 1/3] recipes-bsp: Add gummiboot and gnu-efi recipes Stefan Stanacar
2014-03-06 22:27 ` Darren Hart
2014-03-09 8:00 ` Saul Wold
2014-03-09 15:34 ` Stanacar, StefanX
2014-03-06 18:15 ` [PATCH 2/3] bootimg/grub-efi.bbclass: allow using a different class for EFI images Stefan Stanacar
2014-03-06 22:31 ` Darren Hart
2014-03-06 18:15 ` [PATCH 3/3] classes: Add gummiboot class Stefan Stanacar
2014-03-06 22:36 ` Darren Hart
2014-03-07 9:57 ` Stanacar, StefanX
2014-03-11 21:38 ` Darren Hart
2014-03-12 6:18 ` Koen Kooi
2014-03-12 10:04 ` Stanacar, StefanX
2014-03-12 9:39 ` Matt Fleming [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=20140312093942.GD5834@console-pimps.org \
--to=matt@console-pimps.org \
--cc=dvhart@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox