Message ID | 1528637118-32739-1-git-send-email-bmeng.cn@gmail.com |
---|---|
Headers | show |
Series | x86: efi: Fixes and enhancements to application and payload support | expand |
Hi Bin, On 10 June 2018 at 05:24, Bin Meng <bmeng.cn@gmail.com> wrote: > Unfortunately the EFI x86 application and payload support have been > broken for quite a while. This series addresses various bug fixes, > plus several enhancements like toolchain compatibility (eg: kernel.org > i386-linux-gcc), introduction of generic EFI payload which can run > on any x86 board, and a EFI framebuffer driver for the payload. > > This series is available at u-boot-x86/efi-working for testing. I wonder if it is possible to put qemu testing of the EFI stuff into travis? Also, are the problems only with the i386 compiler, or are things truly broken everywhere? Regards, Simon
Hi Simon, On Mon, Jun 11, 2018 at 10:53 PM, Simon Glass <sjg@chromium.org> wrote: > Hi Bin, > > On 10 June 2018 at 05:24, Bin Meng <bmeng.cn@gmail.com> wrote: >> Unfortunately the EFI x86 application and payload support have been >> broken for quite a while. This series addresses various bug fixes, >> plus several enhancements like toolchain compatibility (eg: kernel.org >> i386-linux-gcc), introduction of generic EFI payload which can run >> on any x86 board, and a EFI framebuffer driver for the payload. >> >> This series is available at u-boot-x86/efi-working for testing. > > I wonder if it is possible to put qemu testing of the EFI stuff into travis? I will take a look. > > Also, are the problems only with the i386 compiler, or are things > truly broken everywhere? > Current mainline status of the EFI stuff is: 1. EFI application does not boot 2. EFI 32-bit payload boots fine 3. EFI 64-bit payload does not boot 4. i386-linux-gcc compiler does not build EFI 64-bit payload, but can build 32-bit payload and application 5. x86_64-linux-gcc compiler can build everything Regards, Bin
Hi Bin, On 11 June 2018 at 09:53, Bin Meng <bmeng.cn@gmail.com> wrote: > > Hi Simon, > > On Mon, Jun 11, 2018 at 10:53 PM, Simon Glass <sjg@chromium.org> wrote: > > Hi Bin, > > > > On 10 June 2018 at 05:24, Bin Meng <bmeng.cn@gmail.com> wrote: > >> Unfortunately the EFI x86 application and payload support have been > >> broken for quite a while. This series addresses various bug fixes, > >> plus several enhancements like toolchain compatibility (eg: kernel.org > >> i386-linux-gcc), introduction of generic EFI payload which can run > >> on any x86 board, and a EFI framebuffer driver for the payload. > >> > >> This series is available at u-boot-x86/efi-working for testing. > > > > I wonder if it is possible to put qemu testing of the EFI stuff into travis? > > I will take a look. > > > > > Also, are the problems only with the i386 compiler, or are things > > truly broken everywhere? > > > > Current mainline status of the EFI stuff is: > > 1. EFI application does not boot > 2. EFI 32-bit payload boots fine > 3. EFI 64-bit payload does not boot > 4. i386-linux-gcc compiler does not build EFI 64-bit payload, but can > build 32-bit payload and application > 5. x86_64-linux-gcc compiler can build everything OK great, thank you. Re (1) it seems a bit tricky since as you say it is a shared library. I suppose we could get a list of unresolved symbols and check them against a whitelist. Or statically link the efi app just for testing purposes. Regards, Simon