From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: "Neri, Ricardo" <ricardo.neri@intel.com>,
"richard.purdie@linuxfoundation.org"
<richard.purdie@linuxfoundation.org>
Cc: "Fleming, Matt" <matt.fleming@intel.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH V2 1/2] ovmf: Recipe taken from luv-yocto repository
Date: Wed, 08 Jul 2015 12:09:16 -0500 [thread overview]
Message-ID: <559D593C.4010600@linux.intel.com> (raw)
In-Reply-To: <1436373958.2639.44.camel@ranerica-desk01>
The new set of patches are failing so I will send a V3! The reason is
that the ovmf source code has ^M line endings and the .patch I send does
not, so when bitbake is trying to patch, there are patch errors.
On 07/08/2015 11:46 AM, Neri, Ricardo wrote:
> On Wed, 2015-07-08 at 17:34 +0100, Richard Purdie wrote:
>> Sorry, I didn't spot this before.
>>
>> Does OE-Core have iasl?
>>
>> Does this recipe not need iasl-native in the target case too?
>
> We also have those recipes in our meta-luv layer.
>
What does this mean? Do we need to add it also? It is not under OE-Core
but I did not face any error when compiling the ovmf recipe under poky.
> Thanks and BR,
> Ricardo
>
next prev parent reply other threads:[~2015-07-08 17:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 8:20 [PATCH V2 0/2] Add UEFI firmware for qemux86* leonardo.sandoval.gonzalez
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 [this message]
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=559D593C.4010600@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 \
--cc=richard.purdie@linuxfoundation.org \
/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