[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1382455358.18283.31.camel@hastur.hellion.org.uk>
Date: Tue, 22 Oct 2013 16:22:38 +0100
From: Ian Campbell <ian.campbell@...rix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
CC: <grub-devel@....org>, <keir@....org>, <david.woodhouse@...el.com>,
<stefano.stabellini@...citrix.com>,
Daniel Kiper <daniel.kiper@...cle.com>,
<linux-kernel@...r.kernel.org>, <xen-devel@...ts.xen.org>,
Jan Beulich <JBeulich@...e.com>,
Peter Jones <pjones@...hat.com>, <ross.philipson@...rix.com>,
<boris.ostrovsky@...cle.com>, <richard.l.maliszewski@...el.com>
Subject: Re: [Xen-devel] EFI and multiboot2 devlopment work for Xen
On Tue, 2013-10-22 at 15:24 +0100, Ian Campbell wrote:
> On Tue, 2013-10-22 at 10:09 -0400, Konrad Rzeszutek Wilk wrote:
>
> > So it can be booted the same way as xen.efi. But my understanding is
> > that folks prefer a bootloader instead of loading the bzImage in an
> > NVRAM of a platform with pre-set parameters. Hence that mechanism
> > is not used by the majority of users.
>
> My understanding is that they prefer a bootloader which can launch Linux
> as a PE/COFF image, i.e. the linuxefi thing.
What I'm trying to say here is that from the xen.efi or linux.efi point
of view it can't tell if it was launched directly from the EFI shell or
by some intermediate bootloader (i.e. by grub2's linuxefi command).
Ian.
--
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