[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131022153258.GA12260@srcf.ucam.org>
Date: Tue, 22 Oct 2013 16:32:58 +0100
From: Matthew Garrett <mjg59@...f.ucam.org>
To: "Woodhouse, David" <david.woodhouse@...el.com>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
Jan Beulich <JBeulich@...e.com>,
Ian Campbell <ian.campbell@...rix.com>,
"ross.philipson@...rix.com" <ross.philipson@...rix.com>,
"stefano.stabellini@...citrix.com" <stefano.stabellini@...citrix.com>,
"grub-devel@....org" <grub-devel@....org>,
"Maliszewski, Richard L" <richard.l.maliszewski@...el.com>,
"xen-devel@...ts.xen.org" <xen-devel@...ts.xen.org>,
"boris.ostrovsky@...cle.com" <boris.ostrovsky@...cle.com>,
Daniel Kiper <daniel.kiper@...cle.com>,
Peter Jones <pjones@...hat.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"keir@....org" <keir@....org>
Subject: Re: EFI and multiboot2 devlopment work for Xen
On Tue, Oct 22, 2013 at 03:25:39PM +0000, Woodhouse, David wrote:
> Oh, ignore that. You want the *actual* PE executable entry point, as it
> would get invoked by a real UEFI firmware.
There are two problems with this:
1) The kernel will only boot if it's signed with a key in db, not a key
in MOK.
2) grub will read the kernel, but the kernel will have to read the
initramfs using EFI calls. That means your initramfs must be on a FAT
partition.
If you're happy with those limitations then just use the chainloader
command. If you're not, use the linuxefi command.
--
Matthew Garrett | mjg59@...f.ucam.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists