From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
"Flanagan, Elizabeth" <elizabeth.flanagan@intel.com>,
yocto-builds <yocto-builds@yoctoproject.org>,
"saul.wold" <saul.wold@intel.com>,
Denys Dmytriyenko <denys@ti.com>,
"Hart, Darren" <darren.hart@intel.com>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: meta-yocto-bsp changes and 3.14
Date: Fri, 28 Mar 2014 15:58:08 -0400 [thread overview]
Message-ID: <5335D450.1030007@windriver.com> (raw)
In-Reply-To: <1396031047.14790.24.camel@ted>
[-- Attachment #1: Type: text/plain, Size: 2362 bytes --]
On 14-03-28 02:24 PM, Richard Purdie wrote:
> I've merged Bruce's 3.14 patches into master-next. With the yocto-bsp
> parts that I could pull together, there seemed to be some pieces
> missing, specifically:
>
> * the yocto-linux-dev.bbappend was underpopulated
> * the yocto-linux-3.14.bbappend was missing
> * no removal of beagleboard
> * no addition to the README for beaglebone
> * local.conf.sample needs updates
> * missing edgerouter configuration in linux-yocto*
> * should we be removing a mips BSP?
> * need a layer version bump so beth can handle this on the autobuilder
After suffering through two rounds of the entire kernel being fetched,
I've confirmed that the bbappend I've been using works for the reference
BSPs on 3.14.
As I mentioned before, my plan was to leave the untested reference BSPs
on 3.10 (particularly the FSL board) and update them once I get confirmation
that they work with 3.14.
I hadn't planned on adding the linux-yocto-dev.bbappend to meta-yocto-bsps,
since the hardware reference boards (unlike qemu) have a greater carrying
cost in terms of testing. So I keep that bbappend slightly out of
sight. At this point, it shouldn't be needed since all the boards
that support 3.14, set that explicitly in their config files.
As we rambled on in the thread, I was looking for a parking lot for
the retiring BSPs that work in 1.6, with the 3.10 kernel, but are not
the first choice. I won't fight to hard from it, and we can simply
pull them out of the 3.10 bbappend if there's no better option.
Attached is the bbappend that I used for testing. If it matches yours
we are good to go.
Bruce
>
> I added commits for some of these, the 3.14 kernel bbappend is missing
> SRCREVs though for example. The state of where I got to is:
>
> http://git.yoctoproject.org/cgit.cgi/meta-yocto/log/?h=master-next
>
> Beth: Your AR is to figure out the autobuilder side of this and build
> the two new replacement BSPs (beaglebone and edgerouter) instead of the
> old ones. When that and the current build on the AB is done, can we run
> a build of master-next please?
>
> Denys: I'm hoping you can help out with the README
>
> Bruce: can you look at the linux-yocto-* changes, particularly the 3.14
> SRCREVs and that linux-yocto-dev looks right?
>
> Cheers,
>
> Richard
>
>
[-- Attachment #2: 0001-meta-yocto-bsp-populate-3.14-bbappend.patch --]
[-- Type: text/x-patch, Size: 1766 bytes --]
From 9648840031b6dc441137b7c8e9d03e5f466821ac Mon Sep 17 00:00:00 2001
From: Bruce Ashfield <bruce.ashfield@windriver.com>
Date: Fri, 28 Mar 2014 15:49:47 -0400
Subject: [PATCH] meta-yocto-bsp: populate 3.14 bbappend
The 3.14 kernel supports the generic-x86, edgerouter and beaglebone black.
All other reference BSPs stay in the 3.10 kernel until boot and regression
testing can be performed.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
---
.../recipes-kernel/linux/linux-yocto_3.14.bbappend | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
create mode 100644 meta-yocto-bsp/recipes-kernel/linux/linux-yocto_3.14.bbappend
diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_3.14.bbappend b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_3.14.bbappend
new file mode 100644
index 000000000000..a1ed1210681f
--- /dev/null
+++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_3.14.bbappend
@@ -0,0 +1,17 @@
+KBRANCH_genericx86 = "standard/common-pc/base"
+KBRANCH_genericx86-64 = "standard/common-pc-64/base"
+KBRANCH_edgerouter = "standard/edgerouter"
+KBRANCH_beaglebone = "standard/beaglebone"
+
+KMACHINE_genericx86 ?= "common-pc"
+KMACHINE_genericx86-64 ?= "common-pc-64"
+
+SRCREV_machine_genericx86 ?= "fecc3fd7d31bd93766ff4f0431fecdbbfa4c3a7c"
+SRCREV_machine_genericx86-64 ?= "fecc3fd7d31bd93766ff4f0431fecdbbfa4c3a7c"
+SRCREV_machine_edgerouter ?= "fecc3fd7d31bd93766ff4f0431fecdbbfa4c3a7c"
+SRCREV_machine_beaglebone ?= "58b6d33dd898f901afbed10cfdec96b9d3148a00"
+
+COMPATIBLE_MACHINE_genericx86 = "genericx86"
+COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
+COMPATIBLE_MACHINE_edgerouter = "edgerouter"
+COMPATIBLE_MACHINE_beaglebone = "beaglebone"
--
1.8.1.2
next prev parent reply other threads:[~2014-03-28 19:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 18:24 meta-yocto-bsp changes and 3.14 Richard Purdie
2014-03-28 18:27 ` Bruce Ashfield
2014-03-28 18:28 ` Bruce Ashfield
2014-03-28 18:34 ` Richard Purdie
2014-03-28 18:38 ` Bruce Ashfield
[not found] ` <CF5B1473.7DC1D%darren.hart@intel.com>
2014-03-28 18:59 ` Bruce Ashfield
[not found] ` <CF5B160D.7DC33%darren.hart@intel.com>
2014-03-28 19:08 ` Bruce Ashfield
2014-03-28 19:12 ` Denys Dmytriyenko
2014-03-28 19:14 ` Bruce Ashfield
[not found] ` <CF5B18D7.7DC4F%darren.hart@intel.com>
2014-03-28 19:27 ` Bruce Ashfield
[not found] ` <CF5B2B7A.7DCA2%darren.hart@intel.com>
2014-03-28 20:41 ` Bruce Ashfield
[not found] ` <20140328183036.GG12929@edge>
2014-03-28 18:32 ` Bruce Ashfield
2014-03-28 18:38 ` Denys Dmytriyenko
2014-03-28 19:48 ` Flanagan, Elizabeth
2014-03-28 19:58 ` Bruce Ashfield [this message]
2014-03-29 23:12 ` Richard Purdie
2014-03-30 12:37 ` Richard Purdie
2014-03-30 19:22 ` Bruce Ashfield
2014-03-31 14:55 ` Denys Dmytriyenko
2014-03-31 15:07 ` Denys Dmytriyenko
2014-03-30 14:46 ` 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=5335D450.1030007@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=darren.hart@intel.com \
--cc=denys@ti.com \
--cc=elizabeth.flanagan@intel.com \
--cc=poky@yoctoproject.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=saul.wold@intel.com \
--cc=yocto-builds@yoctoproject.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.