From: Michael Brown <mbrown@fensystems.co.uk>
To: Matt Fleming <matt@console-pimps.org>, Yinghai Lu <yinghai@kernel.org>
Cc: Matt Fleming <matt.fleming@intel.com>,
"H. Peter Anvin" <hpa@zytor.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: Tue, 15 Jul 2014 16:24:21 +0100 [thread overview]
Message-ID: <53C547A5.3030500@fensystems.co.uk> (raw)
In-Reply-To: <20140715151025.GB32039@console-pimps.org>
On 15/07/14 16:10, Matt Fleming wrote:
> Going forward, I suspect any attempts to use the EFI File Protocol are
> going to result in this kind of breakage, and that the only thing that
> can be relied upon is the Disk I/O Protocol.
>
> But doing Disk I/O would necessitate adding the in-kernel FAT driver to
> the EFI boot stub, which is a scary idea (though not without merit).
Booting via iPXE will give you an EFI_SIMPLE_FILE_SYSTEM_PROTOCOL
(providing access to the initrd previously downloaded by iPXE). It will
also give you a dummy disk I/O protocol which always return EFI_NO_MEDIA.
In those circumstances, only the EFI_SIMPLE_FILE_SYSTEM_PROTOCOL will work.
Michael
next prev parent reply other threads:[~2014-07-15 15:34 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
2014-07-09 18:26 ` Matt Fleming
2014-07-10 18:00 ` Yinghai Lu
2014-07-11 7:40 ` Matt Fleming
2014-07-15 15:10 ` Matt Fleming
2014-07-15 15:24 ` Michael Brown [this message]
2014-07-15 15:44 ` H. Peter Anvin
2014-07-16 14:34 ` Matt Fleming
2014-07-16 14:45 ` Michael Brown
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=53C547A5.3030500@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