From: Patrick Ohly <patrick.ohly@intel.com>
To: Fathi Boudra <fathi.boudra@linaro.org>
Cc: meta-luv <luv@lists.01.org>,
"Neri, Ricardo" <ricardo.neri@intel.com>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/9] iasl: move from meta-luv to OE-core
Date: Wed, 21 Dec 2016 16:38:34 +0100 [thread overview]
Message-ID: <1482334714.6937.34.camel@intel.com> (raw)
In-Reply-To: <CAGNsrLBx=+yvgDAsaqz8mYm30WG0TVEV3eR2PNMj+VHK4ceSOw@mail.gmail.com>
On Wed, 2016-12-21 at 16:11 +0200, Fathi Boudra wrote:
> On 21 December 2016 at 15:11, Patrick Ohly <patrick.ohly@intel.com> wrote:
> > iasl is also provided by the meta-oe layer's acpica recipe. iasl is a
> > bit simpler and thus seems more suitable for OE-core.
>
> Simpler in what sense?
Less code to compile, which might matter for people who just want a
working UEFI for qemu and nothing else. I haven't measured the
difference, though.
> acpica recipe is trivial and provide fully acpica tools.
> Would you mind to import meta-oe acpica recipe instead of providing a
> reduced set of acpica for not much benefit?
I don't have a strong opinion about this and would be fine with moving
acpica to OE-core instead, too.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next prev parent reply other threads:[~2016-12-21 15:38 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-21 13:11 [PATCH 0/9] UEFI + Secure Boot + qemu Patrick Ohly
2016-12-21 13:11 ` [PATCH 1/9] ovmf: move from meta-luv to OE-core Patrick Ohly
2016-12-28 2:58 ` Ricardo Neri
2016-12-21 13:11 ` [PATCH 2/9] iasl: " Patrick Ohly
2016-12-21 14:11 ` Fathi Boudra
2016-12-21 15:38 ` Patrick Ohly [this message]
2016-12-21 18:17 ` Fathi Boudra
2016-12-28 3:08 ` Ricardo Neri
2016-12-21 13:11 ` [PATCH 3/9] ovmf: explicitly depend on nasm-native Patrick Ohly
[not found] ` <1482893989.106950.45.camel@ranerica-desktop>
2017-01-04 12:56 ` Patrick Ohly
2016-12-21 13:11 ` [PATCH 4/9] ovmf: deploy firmware in image directory Patrick Ohly
2016-12-28 3:12 ` Ricardo Neri
2016-12-28 21:38 ` Ricardo Neri
2016-12-28 23:25 ` Ricardo Neri
2017-01-04 10:01 ` Patrick Ohly
2017-01-10 3:50 ` Ricardo Neri
2017-01-10 7:32 ` Patrick Ohly
2016-12-21 13:11 ` [PATCH 5/9] ovmf_git.bb: enable parallel compilation Patrick Ohly
2016-12-28 3:17 ` Ricardo Neri
2016-12-21 13:11 ` [PATCH 6/9] ovmf_git.bb: enable Secure Boot Patrick Ohly
2016-12-28 22:54 ` Ricardo Neri
2017-01-04 10:10 ` Patrick Ohly
2017-01-10 3:51 ` Ricardo Neri
2016-12-21 13:11 ` [PATCH 7/9] runqemu: let command line parameters override defaults Patrick Ohly
2016-12-21 13:11 ` [PATCH 8/9] runqemu: support UEFI with OVMF firmware Patrick Ohly
2016-12-28 23:33 ` Ricardo Neri
2017-01-04 9:43 ` Patrick Ohly
2017-01-10 3:50 ` Ricardo Neri
2017-01-10 7:29 ` Patrick Ohly
2016-12-21 13:11 ` [PATCH 9/9] ovmf: build image which enrolls standard keys Patrick Ohly
2016-12-21 14:19 ` [PATCH 0/9] UEFI + Secure Boot + qemu Fathi Boudra
2016-12-28 2:56 ` Ricardo Neri
2016-12-28 19:27 ` Patrick Ohly
2016-12-28 23:26 ` Ricardo Neri
2016-12-28 2:55 ` Ricardo Neri
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=1482334714.6937.34.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=fathi.boudra@linaro.org \
--cc=luv@lists.01.org \
--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