From: leonardo.sandoval.gonzalez@linux.intel.com
To: openembedded-core@lists.openembedded.org
Cc: matt.fleming@intel.com, ricardo.neri@intel.com
Subject: [PATCH V2 0/2] Add UEFI firmware for qemux86*
Date: Wed, 8 Jul 2015 08:20:25 +0000 [thread overview]
Message-ID: <cover.1436343270.git.leonardo.sandoval.gonzalez@linux.intel.com> (raw)
From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
These two patches include:
1. Recipe: Including the OVMF recipe (taken from luv-yocto repository) into OE-Core
2. Boot script: Instrumenting runqemu to include OECORE_MACHINE_SYSROOT,
so the OVMF BIOS can be found.
[YOCTO #5654]
The following changes since commit 0aaa67a790ab211b35eed58173efa115ceb6e243:
oeqa/bbtests: Fix to ensure DL_DIR is set (2015-07-08 13:09:28 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib lsandov1/efi-qemux86
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=lsandov1/efi-qemux86
Leonardo Sandoval (2):
ovmf: Recipe taken from luv-yocto repository
runqemu: Define OECORE_MACHINE_SYSROOT on setup_sysroot
...s-Force-tools-variables-to-host-toolchain.patch | 50 ++++++++++++++++++
meta/recipes-core/ovmf/ovmf_git.bb | 61 ++++++++++++++++++++++
scripts/runqemu | 13 ++++-
3 files changed, 123 insertions(+), 1 deletion(-)
create mode 100644 meta/recipes-core/ovmf/ovmf/0001-BaseTools-Force-tools-variables-to-host-toolchain.patch
create mode 100644 meta/recipes-core/ovmf/ovmf_git.bb
--
1.8.4.5
next reply other threads:[~2015-07-08 16:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 8:20 leonardo.sandoval.gonzalez [this message]
2015-07-08 8:20 ` [PATCH V2 1/2] ovmf: Recipe taken from luv-yocto repository leonardo.sandoval.gonzalez
2015-07-08 16:34 ` Richard Purdie
[not found] ` <1436373958.2639.44.camel@ranerica-desk01>
2015-07-08 17:09 ` Leonardo Sandoval
2015-07-08 20:11 ` Richard Purdie
2015-07-08 8:20 ` [PATCH V2 2/2] runqemu: Define OECORE_MACHINE_SYSROOT on setup_sysroot leonardo.sandoval.gonzalez
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=cover.1436343270.git.leonardo.sandoval.gonzalez@linux.intel.com \
--to=leonardo.sandoval.gonzalez@linux.intel.com \
--cc=matt.fleming@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ricardo.neri@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox