On Fri, 2015-03-27 at 13:43 +0100, Daniel Kiper wrote:
> On Fri, Mar 27, 2015 at 12:10:56PM +, Jan Beulich wrote:
> > >>> On 27.03.15 at 13:00, wrote:
> > > Additionally, efi_start()
> > > is architecture independent and efi_multiboot2() is x86 only and it should
> > > live in x86 files.
> >
>
On Fri, Mar 27, 2015 at 12:10:56PM +, Jan Beulich wrote:
> >>> On 27.03.15 at 13:00, wrote:
> > Additionally, efi_start()
> > is architecture independent and efi_multiboot2() is x86 only and it should
> > live in x86 files.
>
> Is that really the case? Looking at the grub2 sources I see suppor
>>> On 27.03.15 at 13:00, wrote:
> Additionally, efi_start()
> is architecture independent and efi_multiboot2() is x86 only and it should
> live in x86 files.
Is that really the case? Looking at the grub2 sources I see support
for other than x86...
Jan
_
On Mon, Mar 02, 2015 at 04:45:47PM +, Jan Beulich wrote:
> >>> On 30.01.15 at 18:54, wrote:
> > ..which gets memory map and calls ExitBootServices(). We need this
> > to support multiboot2 protocol on EFI platforms.
>
> Patches from 9 up to here all make sense on the basis that patch 18
> does
>>> On 30.01.15 at 18:54, wrote:
> ..which gets memory map and calls ExitBootServices(). We need this
> to support multiboot2 protocol on EFI platforms.
Patches from 9 up to here all make sense on the basis that patch 18
does and assuming that you really need all this code moved out to
separate f
..which gets memory map and calls ExitBootServices(). We need this
to support multiboot2 protocol on EFI platforms.
Signed-off-by: Daniel Kiper
---
xen/common/efi/boot.c | 79 +++--
1 file changed, 44 insertions(+), 35 deletions(-)
diff --git a/xen/
