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
On 07/15/2014 08:10 AM, 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.
Do we know what the Windows bootloader does? I thought it
On Thu, 10 Jul, at 11:00:06AM, Yinghai Lu wrote:
Oh, no.
so efi could allocate buffer above 4g but can not access it?
I'm not exactly sure what's wrong with the buffer - whether it's a case
of not being able to access it properly or somehing buggy in the EFI
code for reading files. No fault
On Wed, Jul 9, 2014 at 11:26 AM, Matt Fleming m...@console-pimps.org wrote:
On Wed, 18 Jun, at 03:28:19PM, Matt Fleming wrote:
On Sat, 14 Jun, at 12:23:41PM, Yinghai Lu wrote:
For boot efi kernel directly without bootloader.
If the kernel support XLF_CAN_BE_LOADED_ABOVE_4G, we should
not
On Wed, 18 Jun, at 03:28:19PM, Matt Fleming wrote:
On Sat, 14 Jun, at 12:23:41PM, Yinghai Lu wrote:
For boot efi kernel directly without bootloader.
If the kernel support XLF_CAN_BE_LOADED_ABOVE_4G, we should
not limit initrd under hdr-initrd_add_max.
Signed-off-by: Yinghai Lu
On Sat, 14 Jun, at 12:23:41PM, Yinghai Lu wrote:
For boot efi kernel directly without bootloader.
If the kernel support XLF_CAN_BE_LOADED_ABOVE_4G, we should
not limit initrd under hdr-initrd_add_max.
Signed-off-by: Yinghai Lu ying...@kernel.org
---
arch/x86/boot/compressed/eboot.c |
For boot efi kernel directly without bootloader.
If the kernel support XLF_CAN_BE_LOADED_ABOVE_4G, we should
not limit initrd under hdr-initrd_add_max.
Signed-off-by: Yinghai Lu ying...@kernel.org
---
arch/x86/boot/compressed/eboot.c | 14 +++---
1 file changed, 11 insertions(+), 3
