From: Michael Brown <mbrown@fensystems.co.uk>
To: Matt Fleming <matt@console-pimps.org>, "H. Peter Anvin" <hpa@zytor.com>
Cc: Yinghai Lu <yinghai@kernel.org>,
Matt Fleming <matt.fleming@intel.com>,
Ingo Molnar <mingo@redhat.com>,
linux-efi@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Leif Lindholm <leif.lindholm@linaro.org>
Subject: Re: [PATCH] x86, eboot: Support initrd loaded above 4G
Date: Wed, 16 Jul 2014 15:45:15 +0100 [thread overview]
Message-ID: <53C68FFB.1090301@fensystems.co.uk> (raw)
In-Reply-To: <20140716143409.GC32039@console-pimps.org>
On 16/07/14 15:34, Matt Fleming wrote:
> On Tue, 15 Jul, at 08:44:34AM, H. Peter Anvin wrote:
>> Do we know what the Windows bootloader does? I thought it did use the
>> EFI File Protocol?
>
> Good question. I'm not sure what the answer is, I'll try and find some
> time to take a look.
I'm in the middle of related work at the moment: trying to persuade UEFI
WinPE to load its files from the virtual file system exposed by iPXE.
I'll let you know what I find.
Michael
prev parent reply other threads:[~2014-07-16 14:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-14 19:23 [PATCH] x86, eboot: Support initrd loaded above 4G Yinghai Lu
2014-06-18 14:28 ` Matt Fleming
[not found] ` <20140618142819.GN24049-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
2014-07-09 18:26 ` Matt Fleming
[not found] ` <20140709182651.GB15932-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
2014-07-10 18:00 ` Yinghai Lu
[not found] ` <CAE9FiQVP6d5GhFBBmX5HDo0w0oKJSizdKvepq5t6vhGNj=W9sg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-07-11 7:40 ` Matt Fleming
2014-07-15 15:10 ` Matt Fleming
[not found] ` <20140715151025.GB32039-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
2014-07-15 15:24 ` Michael Brown
2014-07-15 15:44 ` H. Peter Anvin
[not found] ` <53C54C62.8070403-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
2014-07-16 14:34 ` Matt Fleming
2014-07-16 14:45 ` Michael Brown [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=53C68FFB.1090301@fensystems.co.uk \
--to=mbrown@fensystems.co.uk \
--cc=ard.biesheuvel@linaro.org \
--cc=hpa@zytor.com \
--cc=leif.lindholm@linaro.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=matt@console-pimps.org \
--cc=mingo@redhat.com \
--cc=yinghai@kernel.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