From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bin Meng <bmeng.cn@gmail.com>
Date: Mon, 11 Jun 2018 23:53:34 +0800
Subject: [U-Boot] [PATCH 00/18] x86: efi: Fixes and enhancements to
 application and payload support
In-Reply-To: <CAPnjgZ2n=m3=CoOXwqi6ydmtdSXiegvYk4RJtD4XkeOrZ9Fk8Q@mail.gmail.com>
References: <1528637118-32739-1-git-send-email-bmeng.cn@gmail.com>
 <CAPnjgZ2n=m3=CoOXwqi6ydmtdSXiegvYk4RJtD4XkeOrZ9Fk8Q@mail.gmail.com>
Message-ID: <CAEUhbmVZ2GwgKe6SbUceXwK-SXAv_dma4tNDYuDTF=Jdo1PTsQ@mail.gmail.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

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