Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/3] linux-yocto/4.19: introduce qemuriscv64 and qemuarma15 BSP definitions
Date: Sat, 12 Jan 2019 13:44:08 -0500	[thread overview]
Message-ID: <230139f6-ad04-7033-5da8-3617b8a7a6a9@windriver.com> (raw)
In-Reply-To: <CAMKF1sokO=RakSBuZy-o4cMBB5EYzDrEJ+R7ZtfzyddNaxqKQw@mail.gmail.com>

On 2019-01-12 1:34 p.m., Khem Raj wrote:
> On Sat, Jan 12, 2019 at 10:14 AM Bruce Ashfield
> <bruce.ashfield@windriver.com> wrote:
>>
>> Incorporating the BSP definitions for two new qemu targets.
>>
>> Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
>> Signed-off-by: Jon Mason <jdmason@kudzu.us>
>> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
>> ---
>>   meta/recipes-kernel/linux/linux-yocto-rt_4.19.bb   |  4 ++--
>>   meta/recipes-kernel/linux/linux-yocto-tiny_4.19.bb |  6 +++---
>>   meta/recipes-kernel/linux/linux-yocto_4.19.bb      | 18 +++++++++---------
>>   3 files changed, 14 insertions(+), 14 deletions(-)
>>
>> diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.19.bb b/meta/recipes-kernel/linux/linux-yocto-rt_4.19.bb
>> index cdcdff2e1746..f823683526ee 100644
>> --- a/meta/recipes-kernel/linux/linux-yocto-rt_4.19.bb
>> +++ b/meta/recipes-kernel/linux/linux-yocto-rt_4.19.bb
>> @@ -11,8 +11,8 @@ python () {
>>           raise bb.parse.SkipRecipe("Set PREFERRED_PROVIDER_virtual/kernel to linux-yocto-rt to enable it")
>>   }
>>
>> -SRCREV_machine ?= "bd456d13d8bea4c416209a59f9e0bf50f8511c47"
>> -SRCREV_meta ?= "ced14887c323f1cb6b3befe2b29e471e8fee1bc6"
>> +SRCREV_machine ?= "78404e3a73613f8e07c276e55112989f897cdd04"
>> +SRCREV_meta ?= "096c8bd3bd11801f95683bbe4bcc885a2318f51d"
>>
>>   SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \
>>              git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.19;destsuffix=${KMETA}"
>> diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.19.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_4.19.bb
>> index 89c4b9f14d4c..0a79f442a075 100644
>> --- a/meta/recipes-kernel/linux/linux-yocto-tiny_4.19.bb
>> +++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.19.bb
>> @@ -15,9 +15,9 @@ DEPENDS += "openssl-native util-linux-native"
>>   KMETA = "kernel-meta"
>>   KCONF_BSP_AUDIT_LEVEL = "2"
>>
>> -SRCREV_machine_qemuarm ?= "b8f2e8e00f8ddbdf5d7d7614c14eab52f8ee9275"
>> -SRCREV_machine ?= "e727c70583a78cf1dc53e8e219722e2f9d1bc858"
>> -SRCREV_meta ?= "ced14887c323f1cb6b3befe2b29e471e8fee1bc6"
>> +SRCREV_machine_qemuarm ?= "2594d14d76ae2c49ad43b626662fe53da807ddca"
>> +SRCREV_machine ?= "1114697c04b9699112e78dd8fc6ec849609ca1cb"
>> +SRCREV_meta ?= "096c8bd3bd11801f95683bbe4bcc885a2318f51d"
>>
>>   PV = "${LINUX_VERSION}+git${SRCPV}"
>>
>> diff --git a/meta/recipes-kernel/linux/linux-yocto_4.19.bb b/meta/recipes-kernel/linux/linux-yocto_4.19.bb
>> index bf4fec71d86c..f410cc8cdb31 100644
>> --- a/meta/recipes-kernel/linux/linux-yocto_4.19.bb
>> +++ b/meta/recipes-kernel/linux/linux-yocto_4.19.bb
>> @@ -11,15 +11,15 @@ KBRANCH_qemux86  ?= "v4.19/standard/base"
>>   KBRANCH_qemux86-64 ?= "v4.19/standard/base"
>>   KBRANCH_qemumips64 ?= "v4.19/standard/mti-malta64"
>>
>> -SRCREV_machine_qemuarm ?= "ec8e55a97ad8a88107c5af069ece1b7f203f4ac4"
>> -SRCREV_machine_qemuarm64 ?= "e727c70583a78cf1dc53e8e219722e2f9d1bc858"
>> -SRCREV_machine_qemumips ?= "3b5fba0207a870c1de76c5dd80d8d3c0e42aa1cf"
>> -SRCREV_machine_qemuppc ?= "e727c70583a78cf1dc53e8e219722e2f9d1bc858"
>> -SRCREV_machine_qemux86 ?= "e727c70583a78cf1dc53e8e219722e2f9d1bc858"
>> -SRCREV_machine_qemux86-64 ?= "e727c70583a78cf1dc53e8e219722e2f9d1bc858"
>> -SRCREV_machine_qemumips64 ?= "d21ff98864241c971c7a42a3c4f1eb940b9b8855"
>> -SRCREV_machine ?= "e727c70583a78cf1dc53e8e219722e2f9d1bc858"
>> -SRCREV_meta ?= "ced14887c323f1cb6b3befe2b29e471e8fee1bc6"
>> +SRCREV_machine_qemuarm ?= "8b378ac8aca51207085c8df616a6fe56af19f0b4"
>> +SRCREV_machine_qemuarm64 ?= "1114697c04b9699112e78dd8fc6ec849609ca1cb"
>> +SRCREV_machine_qemumips ?= "58f59c2213a657515a158379db153ad618986235"
>> +SRCREV_machine_qemuppc ?= "1114697c04b9699112e78dd8fc6ec849609ca1cb"
>> +SRCREV_machine_qemux86 ?= "1114697c04b9699112e78dd8fc6ec849609ca1cb"
>> +SRCREV_machine_qemux86-64 ?= "1114697c04b9699112e78dd8fc6ec849609ca1cb"
>> +SRCREV_machine_qemumips64 ?= "6f56a58c214379efe8949da6921b1c00c2af353a"
>> +SRCREV_machine ?= "1114697c04b9699112e78dd8fc6ec849609ca1cb"
>> +SRCREV_meta ?= "096c8bd3bd11801f95683bbe4bcc885a2318f51d"
> 
> Dont we need qemuriscv64 locks here too ?

Not until the machine is in oe-core and there's something I can test.
Right now, it is just the meta-data.

Bruce

> 
>>
>>   SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;name=machine;branch=${KBRANCH}; \
>>              git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.19;destsuffix=${KMETA}"
>> --
>> 2.5.0
>>
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core



  reply	other threads:[~2019-01-12 18:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-12 18:12 [PATCH 0/3] linux-yocto: consolidated pull request Bruce Ashfield
2019-01-12 18:12 ` [PATCH 1/3] linux-yocto/4.19: introduce qemuriscv64 and qemuarma15 BSP definitions Bruce Ashfield
2019-01-12 18:34   ` Khem Raj
2019-01-12 18:44     ` Bruce Ashfield [this message]
2019-01-12 20:17       ` Khem Raj
2019-01-13 17:24         ` Alistair Francis
2019-01-13 18:30           ` Khem Raj
2019-01-12 18:12 ` [PATCH 2/3] linux-yocto/4.19: update to v4.19.14 Bruce Ashfield
2019-01-12 18:12 ` [PATCH 3/3] linux-yocto-dev: bump to v5.0-rc Bruce Ashfield

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=230139f6-ad04-7033-5da8-3617b8a7a6a9@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.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