From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] linux-yocto: add to qemuppc64 to bb file
Date: Tue, 16 Sep 2014 10:03:36 -0500 [thread overview]
Message-ID: <54185148.6080909@windriver.com> (raw)
In-Reply-To: <541700DA.90803@gmail.com>
On 9/15/14, 10:08 AM, akuster808 wrote:
>
>
> On 09/15/2014 06:11 AM, Bruce Ashfield wrote:
>> On 14-09-12 10:49 PM, Armin Kuster wrote:
>>> Not sure if this this is the correct process.
>>
>> I'll grab the patch and carry it here, and update the SRCREVs at the
>> same time as the other BSPs.
>
> Great, thanks.
>
>>
>> As for adding qemuppc64 fully to the supported set of emulated BSPs
>> for 1.7, that's Richard's call (and I haven't checked to see if the
>> other patches were merged).
>
> Being this late in the 1.7 schedule, I would advise targeting such a
> claim until 1.8. I was surprised by the number for warnings and errors
> a limited world build (meta-networking) burped up considering ppc64 is
> already supported by a few BSP's.
What I've seen is PPC64 (userspace) isn't used much.. most folks are using PPC32
userspace w/ a PPC64 kernel.. (and the occasional large memory application.)
So I'm not surprised there are issues with meta-networking and other components
not being well tested on PPC64...
--Mark
> - Armin
>>
>> Bruce
>>
>>>
>>> Signed-off-by: Armin Kuster <akuster808@gmail.com>
>>> ---
>>> meta/recipes-kernel/linux/linux-yocto_3.14.bb | 4 +++-
>>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/meta/recipes-kernel/linux/linux-yocto_3.14.bb
>>> b/meta/recipes-kernel/linux/linux-yocto_3.14.bb
>>> index e06b191..dfe1de0 100644
>>> --- a/meta/recipes-kernel/linux/linux-yocto_3.14.bb
>>> +++ b/meta/recipes-kernel/linux/linux-yocto_3.14.bb
>>> @@ -6,6 +6,7 @@ require recipes-kernel/linux/linux-yocto.inc
>>> KBRANCH_qemuarm ?= "standard/arm-versatile-926ejs"
>>> KBRANCH_qemumips ?= "standard/mti-malta32"
>>> KBRANCH_qemuppc ?= "standard/qemuppc"
>>> +KBRANCH_qemuppc64 ?= "standard/qemuppc"
>>> KBRANCH_qemux86 ?= "standard/common-pc/base"
>>> KBRANCH_qemux86-64 ?= "standard/common-pc-64/base"
>>> KBRANCH_qemumips64 ?= "standard/mti-malta64"
>>> @@ -13,6 +14,7 @@ KBRANCH_qemumips64 ?= "standard/mti-malta64"
>>> SRCREV_machine_qemuarm ?= "c32a2e1190325f685a61196f38fc03ceff2645bf"
>>> SRCREV_machine_qemumips ?= "1ff50c529b49ceb55a670258f7cb8233c8006c6c"
>>> SRCREV_machine_qemuppc ?= "12e9828a5b78891374375233b4075f682b9fbd0e"
>>> +SRCREV_machine_qemuppc64 ?= "12e9828a5b78891374375233b4075f682b9fbd0e"
>>> SRCREV_machine_qemux86 ?= "58d49fe770ad642e2bc0616159195ba837dc513b"
>>> SRCREV_machine_qemux86-64 ?= "b85edae6fd61ceadfc08099608e8ac90aa4c5c33"
>>> SRCREV_machine_qemumips64 ?= "dcd579737386fca4d7bcf224bc118b14eb3c1d55"
>>> @@ -27,7 +29,7 @@ PV = "${LINUX_VERSION}+git${SRCPV}"
>>>
>>> KMETA = "meta"
>>>
>>> -COMPATIBLE_MACHINE =
>>> "qemuarm|qemux86|qemuppc|qemumips|qemumips64|qemux86-64"
>>> +COMPATIBLE_MACHINE =
>>> "qemuarm|qemux86|qemuppc|qemuppc64|qemumips|qemumips64|qemux86-64"
>>>
>>> # Functionality flags
>>> KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc"
>>>
>>
prev parent reply other threads:[~2014-09-16 15:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-13 2:49 [PATCH] linux-yocto: add to qemuppc64 to bb file Armin Kuster
2014-09-15 13:11 ` Bruce Ashfield
2014-09-15 15:08 ` akuster808
2014-09-16 15:03 ` Mark Hatle [this message]
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=54185148.6080909@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.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 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.