From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/3] x86: qemu: efi: Add two boards for EFI 32-bit and 64-bit payload
Date: Wed, 24 Aug 2016 06:54:14 -0600 [thread overview]
Message-ID: <CAPnjgZ2ocjSFFJMfKDdZxV99Ah9pN1hi5FBoOatfW+NyWrgYSg@mail.gmail.com> (raw)
In-Reply-To: <1472031083-20720-3-git-send-email-bmeng.cn@gmail.com>
On 24 August 2016 at 03:31, Bin Meng <bmeng.cn@gmail.com> wrote:
> This introduces two board defconfig files for generating EFI 32-bit
> and 64-bit payloads, to run on QEMU x86 target.
>
> With these in place, hopefully buildman will catch any build error
> with EFI payload support on x86.
>
> Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
>
> ---
>
> configs/qemu-x86_efi_payload32_defconfig | 48 +++++++++++++++++++++++++++++++
> configs/qemu-x86_efi_payload64_defconfig | 49 ++++++++++++++++++++++++++++++++
> 2 files changed, 97 insertions(+)
> create mode 100644 configs/qemu-x86_efi_payload32_defconfig
> create mode 100644 configs/qemu-x86_efi_payload64_defconfig
Great!
Reviewed-by: Simon Glass <sjg@chromium.org>
By the way I am working on initial 64-bit support and hope to have
patches out in 2-3 weeks. I've run out of time for now unfortunately.
- Simon
next prev parent reply other threads:[~2016-08-24 12:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 9:31 [U-Boot] [PATCH 1/3] x86: efi: payload: Make efi payload build again Bin Meng
2016-08-24 9:31 ` [U-Boot] [PATCH 2/3] x86: efi: payload: Correct BITS_PER_LONG to 32 Bin Meng
2016-08-24 12:53 ` Simon Glass
2016-08-25 2:56 ` Bin Meng
2016-08-24 9:31 ` [U-Boot] [PATCH 3/3] x86: qemu: efi: Add two boards for EFI 32-bit and 64-bit payload Bin Meng
2016-08-24 12:54 ` Simon Glass [this message]
2016-08-24 12:53 ` [U-Boot] [PATCH 1/3] x86: efi: payload: Make efi payload build again Simon Glass
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=CAPnjgZ2ocjSFFJMfKDdZxV99Ah9pN1hi5FBoOatfW+NyWrgYSg@mail.gmail.com \
--to=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.