Re: [PATCH 2/5] x86_32: boot, extract efi_pe_entry from startup_32

2017-06-05 Thread Matt Fleming
On Wed, 31 May, at 10:12:40AM, Jiri Slaby wrote: > efi_pe_entry body is somehow squashed into startup_32. In the old days, > we forced startup_32 to start at offset 0x00 and efi_pe_entry to start > at 0x10. But this requirement was removed in 99f857db8857 ("x86, build: > Dynamically find entry

Re: [PATCH 2/5] x86_32: boot, extract efi_pe_entry from startup_32

2017-06-05 Thread Matt Fleming
On Wed, 31 May, at 10:12:40AM, Jiri Slaby wrote: > efi_pe_entry body is somehow squashed into startup_32. In the old days, > we forced startup_32 to start at offset 0x00 and efi_pe_entry to start > at 0x10. But this requirement was removed in 99f857db8857 ("x86, build: > Dynamically find entry

[PATCH 2/5] x86_32: boot, extract efi_pe_entry from startup_32

2017-05-31 Thread Jiri Slaby
efi_pe_entry body is somehow squashed into startup_32. In the old days, we forced startup_32 to start at offset 0x00 and efi_pe_entry to start at 0x10. But this requirement was removed in 99f857db8857 ("x86, build: Dynamically find entry points in compressed startup code") long time ago. The way

[PATCH 2/5] x86_32: boot, extract efi_pe_entry from startup_32

2017-05-31 Thread Jiri Slaby
efi_pe_entry body is somehow squashed into startup_32. In the old days, we forced startup_32 to start at offset 0x00 and efi_pe_entry to start at 0x10. But this requirement was removed in 99f857db8857 ("x86, build: Dynamically find entry points in compressed startup code") long time ago. The way