linux-yocto: 3.4, 3.8, 3.10 AND 3.14 updates
cover linux-yocto: 3.4, 3.8, 3.10 AND 3.14 updates
Richard/Saul,
Here are the udpates to the various kernels that have been soaked and tested long enough to head into the main trees.
3.4:
- minor configuration updates for the monhonpeak
3.10:
- BSP configuration updates
- korg stable integrations
- build fixes
3.8:
- removal
3.14:
- versioned 3.14 recipes
- libc-headers update to 3.14, removal of old libc-headers recipes
The obvious changes to take note of are introduction of the 3.14 versioned recipes, and libc-headers. Since Linus decided to do a -rc8, we decided to not wait for the full release to put out the 3.14 versioned recipes and libc-headers updates.
In particular with the 3.14 libc-headers, I've made it look like the 3.14 release headers with the recipe name, but within the recipe I have some forcing to 3.14-rc8. When the release tarball is availble, I'll follow up with changes to the recipe itself.
This is the same tree that has been soaking via linux-yocto-dev, with an update to -rc8. Build and boot testing has been completed on all targets, as has the building of packages known to be sensitive to kernel version changes (core-image-kernel-dev). You already have the perf fixes, so nothing to send there.
3.4 and 3.10 are ready immediately for merge, the 3.14 related changes feel free to soak them until the full release .. or if they pass MUT, we can go ahead and merge.
Thanks to Darren, Tom, Nitin and everyone else that has been testing the changes, and reporting issues.
Cheers,
Bruce
The following changes since commit 5eceedf0326abaee632b32c7cb7ec74e6ba2d6d7:
ocf-linux: remove recipe (2014-03-27 15:46:52 +0000)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (13):
linux-yocto/3.10: intel-core*/common configuration updates linux-yocto/3.4: update mohonpeak.cfg for SATA, SMBus, LPC, WDT,
crypto & highmem64g
linux-yocto/3.10: update EFI configuration linux-yocto/3.10: update to v3.10.33 linux-yocto/3.10: add valleyisland io linux-yocto/3.10: update to v3.10.34 linux-yocto/3.10: update intel common meta data linux-yocto/3.10: fix drm build failure linux-yocto/3.8: remove versioned recipes linux-yocto/3.14: introduce versioned recipes
linux-libc-headers: add 3.14 libc headers
libc-headers: set TC default to 3.14
linux-libc-headers: remove 3.10 recipe
meta/conf/distro/include/tcmode-default.inc | 2 +-
...1-ptrace.h-remove-ptrace_peeksiginfo_args.patch | 50 ------------------
...lude-asm-byteorder.h-in-linux-raid-md_p.h.patch | 34 -------------
...efile.headersinst-install-headers-from-sc.patch | 59 ----------------------
.../linux-libc-headers/linux-libc-headers_3.10.bb | 11 ----
.../linux-libc-headers/linux-libc-headers_3.14.bb | 13 +++++
meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 8 +--
meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-rt_3.8.bb | 30 -----------
meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 6 +--
meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb | 21 ++++++++
meta/recipes-kernel/linux/linux-yocto-tiny_3.4.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-tiny_3.8.bb | 26 ----------
meta/recipes-kernel/linux/linux-yocto_3.10.bb | 18 +++----
.../{linux-yocto_3.8.bb => linux-yocto_3.14.bb} | 24 ++++-----
meta/recipes-kernel/linux/linux-yocto_3.4.bb | 2 +-
16 files changed, 65 insertions(+), 243 deletions(-)
delete mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers/0001-ptrace.h-remove-ptrace_peeksiginfo_args.patch
delete mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers/UAPI-include-asm-byteorder.h-in-linux-raid-md_p.h.patch
delete mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers/scripts-Makefile.headersinst-install-headers-from-sc.patch
delete mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
create mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.14.bb
delete mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.8.bb
create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb
delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.8.bb
rename meta/recipes-kernel/linux/{linux-yocto_3.8.bb => linux-yocto_3.14.bb} (52%)Signature · 1 line
1.8.1.2
PATCH 1/13 linux-yocto/3.10: intel-core*/common configuration updates
Importing the following configuration changes to support the latest intel common BSPs:
6e0e756d5137 intel-common: Remove GMA500 support 226c3b7a2b82 intel-core*: Add baytrail soc support 25df7acf2cc4 baytrail: Add feature/soc/baytrail 8715856ab617 meta: input: add CONFIG_INPUT dependency
--- meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 2 +- meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 2 +- meta/recipes-kernel/linux/linux-yocto_3.10.bb | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)
meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb +1 -1
@@ -5,7 +5,7 @@ KBRANCH_qemuppc = "standard/preempt-rt/qemuppc" SRCREV_machine ?= "5f466af88f885705efe0f018c027b2631f6724e4" SRCREV_machine_qemuppc ?= "e497cba7496e4ae6fc4d018bce57695a61766d22" -SRCREV_meta ?= "7b3b87d4d5e4c41c235da13aaa9f45d5d338e2c6" +SRCREV_meta ?= "6e0e756d51372c8b176c5d1e6f786545bceed351" SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.10.git;bareclone=1;branch=${KBRANCH},meta;name=machine,meta"
meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb +1 -1
@@ -10,7 +10,7 @@ LINUX_VERSION ?= "3.10.32" KMETA = "meta" SRCREV_machine ?= "78afd3095c9b37efbbfbfdc25eb3833ef3c6a718" -SRCREV_meta ?= "7b3b87d4d5e4c41c235da13aaa9f45d5d338e2c6" +SRCREV_meta ?= "6e0e756d51372c8b176c5d1e6f786545bceed351" PV = "${LINUX_VERSION}+git${SRCPV}"
meta/recipes-kernel/linux/linux-yocto_3.10.bb +1 -1
@@ -18,7 +18,7 @@ SRCREV_machine_qemux86 ?= "78afd3095c9b37efbbfbfdc25eb3833ef3c6a718" SRCREV_machine_qemux86-64 ?= "78afd3095c9b37efbbfbfdc25eb3833ef3c6a718" SRCREV_machine_qemumips64 ?= "3e1899546c014808fed8d336b777bf8d81f50d7b" SRCREV_machine ?= "78afd3095c9b37efbbfbfdc25eb3833ef3c6a718" -SRCREV_meta ?= "7b3b87d4d5e4c41c235da13aaa9f45d5d338e2c6" +SRCREV_meta ?= "6e0e756d51372c8b176c5d1e6f786545bceed351" SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.10.git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta"
Signature · 1 line
1.8.1.2
PATCH 2/13 linux-yocto/3.4: update mohonpeak.cfg for SATA, SMBus, LPC, WDT, crypto & highmem64g
In reply to Bruce AshfieldUpdating the meta SRCREV with the latest configuration updates.
--- meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb | 2 +- meta/recipes-kernel/linux/linux-yocto-tiny_3.4.bb | 2 +- meta/recipes-kernel/linux/linux-yocto_3.4.bb | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)
meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb +1 -1
@@ -10,7 +10,7 @@ KMETA = "meta" SRCREV_machine ?= "74369c14c79dbb546ce1e387b1363e808ea4f5b1" SRCREV_machine_qemuppc ?= "71694a302cda24cc8a7c5f772e8306111ffcfb6c" -SRCREV_meta ?= "8e88bf72b72afb3b638e751ea2a5c89394cc196b" +SRCREV_meta ?= "ef4cd500d4b64680f7a319d399b8a12f9ecc9fe6" PR = "${INC_PR}.1" PV = "${LINUX_VERSION}+git${SRCPV}"
meta/recipes-kernel/linux/linux-yocto-tiny_3.4.bb +1 -1
@@ -13,7 +13,7 @@ LINUX_VERSION ?= "3.4.82" KMETA = "meta" SRCREV_machine ?= "c29f5c8952c0f3ef27773d78e5cc64e437a357cb" -SRCREV_meta ?= "8e88bf72b72afb3b638e751ea2a5c89394cc196b" +SRCREV_meta ?= "ef4cd500d4b64680f7a319d399b8a12f9ecc9fe6" PR = "${INC_PR}.1" PV = "${LINUX_VERSION}+git${SRCPV}"
meta/recipes-kernel/linux/linux-yocto_3.4.bb +1 -1
@@ -17,7 +17,7 @@ SRCREV_machine_qemuppc ?= "85868d48f06911b7dddaf0180af96c8f2e874922" SRCREV_machine_qemux86 ?= "c29f5c8952c0f3ef27773d78e5cc64e437a357cb" SRCREV_machine_qemux86-64 ?= "c29f5c8952c0f3ef27773d78e5cc64e437a357cb" SRCREV_machine ?= "c29f5c8952c0f3ef27773d78e5cc64e437a357cb" -SRCREV_meta ?= "8e88bf72b72afb3b638e751ea2a5c89394cc196b" +SRCREV_meta ?= "ef4cd500d4b64680f7a319d399b8a12f9ecc9fe6" SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.4.git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta"
Signature · 1 line
1.8.1.2
PATCH 3/13 linux-yocto/3.10: update EFI configuration
In reply to Bruce AshfieldImporting the following two meta data changes for EFI configuration:
284e9589436a meta: efi.cfg/efi-ext.cfg: add EFIVAR_FS to default efi fragment 0a8c4971e2d9 meta: update efi config fragment to include EFI_STUB by default
--- meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 2 +- meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 2 +- meta/recipes-kernel/linux/linux-yocto_3.10.bb | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)
meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb +1 -1
@@ -5,7 +5,7 @@ KBRANCH_qemuppc = "standard/preempt-rt/qemuppc" SRCREV_machine ?= "5f466af88f885705efe0f018c027b2631f6724e4" SRCREV_machine_qemuppc ?= "e497cba7496e4ae6fc4d018bce57695a61766d22" -SRCREV_meta ?= "6e0e756d51372c8b176c5d1e6f786545bceed351" +SRCREV_meta ?= "284e9589436a5b199cf44b7261640c944558a35e" SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.10.git;bareclone=1;branch=${KBRANCH},meta;name=machine,meta"
meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb +1 -1
@@ -10,7 +10,7 @@ LINUX_VERSION ?= "3.10.32" KMETA = "meta" SRCREV_machine ?= "78afd3095c9b37efbbfbfdc25eb3833ef3c6a718" -SRCREV_meta ?= "6e0e756d51372c8b176c5d1e6f786545bceed351" +SRCREV_meta ?= "284e9589436a5b199cf44b7261640c944558a35e" PV = "${LINUX_VERSION}+git${SRCPV}"
meta/recipes-kernel/linux/linux-yocto_3.10.bb +1 -1
@@ -18,7 +18,7 @@ SRCREV_machine_qemux86 ?= "78afd3095c9b37efbbfbfdc25eb3833ef3c6a718" SRCREV_machine_qemux86-64 ?= "78afd3095c9b37efbbfbfdc25eb3833ef3c6a718" SRCREV_machine_qemumips64 ?= "3e1899546c014808fed8d336b777bf8d81f50d7b" SRCREV_machine ?= "78afd3095c9b37efbbfbfdc25eb3833ef3c6a718" -SRCREV_meta ?= "6e0e756d51372c8b176c5d1e6f786545bceed351" +SRCREV_meta ?= "284e9589436a5b199cf44b7261640c944558a35e" SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.10.git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta"
Signature · 1 line
1.8.1.2
PATCH 4/13 linux-yocto/3.10: update to v3.10.33
In reply to Bruce AshfieldUpdating to the latest -stable release.
--- meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 6 +++--- meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 4 ++-- meta/recipes-kernel/linux/linux-yocto_3.10.bb | 16 ++++++++-------- 3 files changed, 13 insertions(+), 13 deletions(-)
meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb +3 -3
@@ -3,13 +3,13 @@ require recipes-kernel/linux/linux-yocto.inc KBRANCH = "standard/preempt-rt/base" KBRANCH_qemuppc = "standard/preempt-rt/qemuppc" -SRCREV_machine ?= "5f466af88f885705efe0f018c027b2631f6724e4" -SRCREV_machine_qemuppc ?= "e497cba7496e4ae6fc4d018bce57695a61766d22" +SRCREV_machine ?= "adc7322e1696fd53f1915c40c87c98cf5c98ebf0" +SRCREV_machine_qemuppc ?= "1d6cce881e4fefb5d5e0691da62d8f71f51e342c" SRCREV_meta ?= "284e9589436a5b199cf44b7261640c944558a35e" SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.10.git;bareclone=1;branch=${KBRANCH},meta;name=machine,meta" -LINUX_VERSION ?= "3.10.32" +LINUX_VERSION ?= "3.10.33" PV = "${LINUX_VERSION}+git${SRCPV}"
meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb +2 -2
@@ -5,11 +5,11 @@ KBRANCH = "${KBRANCH_DEFAULT}" LINUX_KERNEL_TYPE = "tiny" KCONFIG_MODE = "--allnoconfig" -LINUX_VERSION ?= "3.10.32" +LINUX_VERSION ?= "3.10.33" KMETA = "meta" -SRCREV_machine ?= "78afd3095c9b37efbbfbfdc25eb3833ef3c6a718" +SRCREV_machine ?= "21df0c8486e129a4087970a07b423c533ae05de7" SRCREV_meta ?= "284e9589436a5b199cf44b7261640c944558a35e" PV = "${LINUX_VERSION}+git${SRCPV}"
meta/recipes-kernel/linux/linux-yocto_3.10.bb +8 -8
@@ -11,18 +11,18 @@ KBRANCH_qemux86 = "standard/common-pc/base" KBRANCH_qemux86-64 = "standard/common-pc-64/base" KBRANCH_qemumips64 = "standard/mti-malta64" -SRCREV_machine_qemuarm ?= "c295c53987007a5d0c87cc9b23125e9ff85900bd" -SRCREV_machine_qemumips ?= "2833be8c96671b24a203a5dc45a21c38d5d841c3" -SRCREV_machine_qemuppc ?= "cf413ddca8b974a473b72635e1499223a02d7949" -SRCREV_machine_qemux86 ?= "78afd3095c9b37efbbfbfdc25eb3833ef3c6a718" -SRCREV_machine_qemux86-64 ?= "78afd3095c9b37efbbfbfdc25eb3833ef3c6a718" -SRCREV_machine_qemumips64 ?= "3e1899546c014808fed8d336b777bf8d81f50d7b" -SRCREV_machine ?= "78afd3095c9b37efbbfbfdc25eb3833ef3c6a718" +SRCREV_machine_qemuarm ?= "670a1d401ace1c5894a87466e5136ed60cf66966" +SRCREV_machine_qemumips ?= "45fc480deb2f4e5b42265c59fa4bec784e995294" +SRCREV_machine_qemuppc ?= "ac1c54b68ee44c00906933547b310652fd725d4b" +SRCREV_machine_qemux86 ?= "21df0c8486e129a4087970a07b423c533ae05de7" +SRCREV_machine_qemux86-64 ?= "21df0c8486e129a4087970a07b423c533ae05de7" +SRCREV_machine_qemumips64 ?= "31139804e58e049e696fa49175544a43c40b3506" +SRCREV_machine ?= "21df0c8486e129a4087970a07b423c533ae05de7" SRCREV_meta ?= "284e9589436a5b199cf44b7261640c944558a35e" SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.10.git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta" -LINUX_VERSION ?= "3.10.32" +LINUX_VERSION ?= "3.10.33" PV = "${LINUX_VERSION}+git${SRCPV}"
Signature · 1 line
1.8.1.2
PATCH 5/13 linux-yocto/3.10: add valleyisland io
In reply to Bruce AshfieldUpdating the 3.10 meta SRCREV to include the valleyisland IO .scc and configuration files.
--- meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 2 +- meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 2 +- meta/recipes-kernel/linux/linux-yocto_3.10.bb | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)
meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb +1 -1
@@ -5,7 +5,7 @@ KBRANCH_qemuppc = "standard/preempt-rt/qemuppc" SRCREV_machine ?= "adc7322e1696fd53f1915c40c87c98cf5c98ebf0" SRCREV_machine_qemuppc ?= "1d6cce881e4fefb5d5e0691da62d8f71f51e342c" -SRCREV_meta ?= "284e9589436a5b199cf44b7261640c944558a35e" +SRCREV_meta ?= "99c503a92885060bebf2bba6747735e8e9346a40" SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.10.git;bareclone=1;branch=${KBRANCH},meta;name=machine,meta"
meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb +1 -1
@@ -10,7 +10,7 @@ LINUX_VERSION ?= "3.10.33" KMETA = "meta" SRCREV_machine ?= "21df0c8486e129a4087970a07b423c533ae05de7" -SRCREV_meta ?= "284e9589436a5b199cf44b7261640c944558a35e" +SRCREV_meta ?= "99c503a92885060bebf2bba6747735e8e9346a40" PV = "${LINUX_VERSION}+git${SRCPV}"
meta/recipes-kernel/linux/linux-yocto_3.10.bb +1 -1
@@ -18,7 +18,7 @@ SRCREV_machine_qemux86 ?= "21df0c8486e129a4087970a07b423c533ae05de7" SRCREV_machine_qemux86-64 ?= "21df0c8486e129a4087970a07b423c533ae05de7" SRCREV_machine_qemumips64 ?= "31139804e58e049e696fa49175544a43c40b3506" SRCREV_machine ?= "21df0c8486e129a4087970a07b423c533ae05de7" -SRCREV_meta ?= "284e9589436a5b199cf44b7261640c944558a35e" +SRCREV_meta ?= "99c503a92885060bebf2bba6747735e8e9346a40" SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.10.git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta"
Signature · 1 line
1.8.1.2
PATCH 6/13 linux-yocto/3.10: update to v3.10.34
In reply to Bruce AshfieldUpdating to the latest korg -stable release.
--- meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 8 ++++---- meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 6 +++--- meta/recipes-kernel/linux/linux-yocto_3.10.bb | 18 +++++++++--------- 3 files changed, 16 insertions(+), 16 deletions(-)
meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb +4 -4
@@ -3,13 +3,13 @@ require recipes-kernel/linux/linux-yocto.inc KBRANCH = "standard/preempt-rt/base" KBRANCH_qemuppc = "standard/preempt-rt/qemuppc" -SRCREV_machine ?= "adc7322e1696fd53f1915c40c87c98cf5c98ebf0" -SRCREV_machine_qemuppc ?= "1d6cce881e4fefb5d5e0691da62d8f71f51e342c" -SRCREV_meta ?= "99c503a92885060bebf2bba6747735e8e9346a40" +SRCREV_machine ?= "f121a3aa028df37b8050779adaa239d29aaa2edd" +SRCREV_machine_qemuppc ?= "7172d3cbc73584e724b61ef5d13fc3519720f4c0" +SRCREV_meta ?= "cce9fc32c10dc875bf1ae0a4a86fe3ce79138f5a" SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.10.git;bareclone=1;branch=${KBRANCH},meta;name=machine,meta" -LINUX_VERSION ?= "3.10.33" +LINUX_VERSION ?= "3.10.34" PV = "${LINUX_VERSION}+git${SRCPV}"
meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb +3 -3
@@ -5,12 +5,12 @@ KBRANCH = "${KBRANCH_DEFAULT}" LINUX_KERNEL_TYPE = "tiny" KCONFIG_MODE = "--allnoconfig" -LINUX_VERSION ?= "3.10.33" +LINUX_VERSION ?= "3.10.34" KMETA = "meta" -SRCREV_machine ?= "21df0c8486e129a4087970a07b423c533ae05de7" -SRCREV_meta ?= "99c503a92885060bebf2bba6747735e8e9346a40" +SRCREV_machine ?= "2ee37bfe732c73f7d39af55875ce8d30b282471c" +SRCREV_meta ?= "cce9fc32c10dc875bf1ae0a4a86fe3ce79138f5a" PV = "${LINUX_VERSION}+git${SRCPV}"
meta/recipes-kernel/linux/linux-yocto_3.10.bb +9 -9
@@ -11,18 +11,18 @@ KBRANCH_qemux86 = "standard/common-pc/base" KBRANCH_qemux86-64 = "standard/common-pc-64/base" KBRANCH_qemumips64 = "standard/mti-malta64" -SRCREV_machine_qemuarm ?= "670a1d401ace1c5894a87466e5136ed60cf66966" -SRCREV_machine_qemumips ?= "45fc480deb2f4e5b42265c59fa4bec784e995294" -SRCREV_machine_qemuppc ?= "ac1c54b68ee44c00906933547b310652fd725d4b" -SRCREV_machine_qemux86 ?= "21df0c8486e129a4087970a07b423c533ae05de7" -SRCREV_machine_qemux86-64 ?= "21df0c8486e129a4087970a07b423c533ae05de7" -SRCREV_machine_qemumips64 ?= "31139804e58e049e696fa49175544a43c40b3506" -SRCREV_machine ?= "21df0c8486e129a4087970a07b423c533ae05de7" -SRCREV_meta ?= "99c503a92885060bebf2bba6747735e8e9346a40" +SRCREV_machine_qemuarm ?= "e18e8c2c7cad913a25342f9f860eeeefce24b8aa" +SRCREV_machine_qemumips ?= "6f191aaecfdbebda450cec4a1f30fb0d1a2ed889" +SRCREV_machine_qemuppc ?= "ba2e16160c7f910de432511ca0008101a7b2263b" +SRCREV_machine_qemux86 ?= "2ee37bfe732c73f7d39af55875ce8d30b282471c" +SRCREV_machine_qemux86-64 ?= "2ee37bfe732c73f7d39af55875ce8d30b282471c" +SRCREV_machine_qemumips64 ?= "e05f0378e9c21d689eed8aacb306d2c1a044e0d0" +SRCREV_machine ?= "2ee37bfe732c73f7d39af55875ce8d30b282471c" +SRCREV_meta ?= "cce9fc32c10dc875bf1ae0a4a86fe3ce79138f5a" SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.10.git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta" -LINUX_VERSION ?= "3.10.33" +LINUX_VERSION ?= "3.10.34" PV = "${LINUX_VERSION}+git${SRCPV}"
Signature · 1 line
1.8.1.2
PATCH 7/13 linux-yocto/3.10: update intel common meta data
In reply to Bruce AshfieldBumping the meta branch SRCREV for the following two commits:
df3aa753c882 intel-common: Add media-all to the standard builds 4b0d57269dae intel-common: Add mohonpeak BSP
--- meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 2 +- meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 2 +- meta/recipes-kernel/linux/linux-yocto_3.10.bb | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)
meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb +1 -1
@@ -5,7 +5,7 @@ KBRANCH_qemuppc = "standard/preempt-rt/qemuppc" SRCREV_machine ?= "f121a3aa028df37b8050779adaa239d29aaa2edd" SRCREV_machine_qemuppc ?= "7172d3cbc73584e724b61ef5d13fc3519720f4c0" -SRCREV_meta ?= "cce9fc32c10dc875bf1ae0a4a86fe3ce79138f5a" +SRCREV_meta ?= "df3aa753c8826127fb5ad811d56d57168551d6e4" SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.10.git;bareclone=1;branch=${KBRANCH},meta;name=machine,meta"
meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb +1 -1
@@ -10,7 +10,7 @@ LINUX_VERSION ?= "3.10.34" KMETA = "meta" SRCREV_machine ?= "2ee37bfe732c73f7d39af55875ce8d30b282471c" -SRCREV_meta ?= "cce9fc32c10dc875bf1ae0a4a86fe3ce79138f5a" +SRCREV_meta ?= "df3aa753c8826127fb5ad811d56d57168551d6e4" PV = "${LINUX_VERSION}+git${SRCPV}"
meta/recipes-kernel/linux/linux-yocto_3.10.bb +1 -1
@@ -18,7 +18,7 @@ SRCREV_machine_qemux86 ?= "2ee37bfe732c73f7d39af55875ce8d30b282471c" SRCREV_machine_qemux86-64 ?= "2ee37bfe732c73f7d39af55875ce8d30b282471c" SRCREV_machine_qemumips64 ?= "e05f0378e9c21d689eed8aacb306d2c1a044e0d0" SRCREV_machine ?= "2ee37bfe732c73f7d39af55875ce8d30b282471c" -SRCREV_meta ?= "cce9fc32c10dc875bf1ae0a4a86fe3ce79138f5a" +SRCREV_meta ?= "df3aa753c8826127fb5ad811d56d57168551d6e4" SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.10.git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta"
Signature · 1 line
1.8.1.2
PATCH 8/13 linux-yocto/3.10: fix drm build failure
In reply to Bruce AshfieldAndrea Adami reported the following build failure:
.../drm/drm_mm.h:105:2: error: implicit declaration of function
'BUG_ON' [-Werror=implicit-function-declaration]
| BUG_ON(!hole_node->hole_follows);
| ^
| CC drivers/pci/setup-res.o
| CC drivers/gpu/drm/i915/i915_drv.o
| cc1: some warnings being treated as errors
| make[6]: *** [drivers/gpu/drm/ttm/ttm_agp_backend.o] Error 1
| make[5]: *** [drivers/gpu/drm/ttm] Error 2Cherry picking mainline commit 86e81f0e6 [drm/mm: include required headers in drm_mm.h] fixes the build problems.
--- meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 4 ++-- meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 2 +- meta/recipes-kernel/linux/linux-yocto_3.10.bb | 14 +++++++------- 3 files changed, 10 insertions(+), 10 deletions(-)
meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb +2 -2
@@ -3,8 +3,8 @@ require recipes-kernel/linux/linux-yocto.inc KBRANCH = "standard/preempt-rt/base" KBRANCH_qemuppc = "standard/preempt-rt/qemuppc" -SRCREV_machine ?= "f121a3aa028df37b8050779adaa239d29aaa2edd" -SRCREV_machine_qemuppc ?= "7172d3cbc73584e724b61ef5d13fc3519720f4c0" +SRCREV_machine ?= "f4351616572c6ad5a8b71b1becf02c3e779b85b8" +SRCREV_machine_qemuppc ?= "a6dfc85e99633d739068a03d2551e39847628551" SRCREV_meta ?= "df3aa753c8826127fb5ad811d56d57168551d6e4" SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.10.git;bareclone=1;branch=${KBRANCH},meta;name=machine,meta"
meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb +1 -1
@@ -9,7 +9,7 @@ LINUX_VERSION ?= "3.10.34" KMETA = "meta" -SRCREV_machine ?= "2ee37bfe732c73f7d39af55875ce8d30b282471c" +SRCREV_machine ?= "c7739be126930006e3bfbdb2fb070a967abc5e09" SRCREV_meta ?= "df3aa753c8826127fb5ad811d56d57168551d6e4" PV = "${LINUX_VERSION}+git${SRCPV}"
meta/recipes-kernel/linux/linux-yocto_3.10.bb +7 -7
@@ -11,13 +11,13 @@ KBRANCH_qemux86 = "standard/common-pc/base" KBRANCH_qemux86-64 = "standard/common-pc-64/base" KBRANCH_qemumips64 = "standard/mti-malta64" -SRCREV_machine_qemuarm ?= "e18e8c2c7cad913a25342f9f860eeeefce24b8aa" -SRCREV_machine_qemumips ?= "6f191aaecfdbebda450cec4a1f30fb0d1a2ed889" -SRCREV_machine_qemuppc ?= "ba2e16160c7f910de432511ca0008101a7b2263b" -SRCREV_machine_qemux86 ?= "2ee37bfe732c73f7d39af55875ce8d30b282471c" -SRCREV_machine_qemux86-64 ?= "2ee37bfe732c73f7d39af55875ce8d30b282471c" -SRCREV_machine_qemumips64 ?= "e05f0378e9c21d689eed8aacb306d2c1a044e0d0" -SRCREV_machine ?= "2ee37bfe732c73f7d39af55875ce8d30b282471c" +SRCREV_machine_qemuarm ?= "0e99eabbe5b3bec853ace496f94612bc37800260" +SRCREV_machine_qemumips ?= "b6b20f49e9a169a0672b7cc2d7b93d6652ca7873" +SRCREV_machine_qemuppc ?= "d71b782615b802c78e1586494b94dd40531775c8" +SRCREV_machine_qemux86 ?= "c7739be126930006e3bfbdb2fb070a967abc5e09" +SRCREV_machine_qemux86-64 ?= "c7739be126930006e3bfbdb2fb070a967abc5e09" +SRCREV_machine_qemumips64 ?= "88abb1eb327f4e3c711d19a228cb153fdd9b3506" +SRCREV_machine ?= "c7739be126930006e3bfbdb2fb070a967abc5e09" SRCREV_meta ?= "df3aa753c8826127fb5ad811d56d57168551d6e4" SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.10.git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta"
Signature · 1 line
1.8.1.2
PATCH 9/13 linux-yocto/3.8: remove versioned recipes
In reply to Bruce AshfieldYocto 1.6 will support the LTSI 3.4/3.10 kernels and the 3.14 kernel. As such, we remove the 3.8 linux-yocto recipes to keep our number of supported kernels at three.
--- meta/recipes-kernel/linux/linux-yocto-rt_3.8.bb | 30 ----------------- meta/recipes-kernel/linux/linux-yocto-tiny_3.8.bb | 26 --------------- meta/recipes-kernel/linux/linux-yocto_3.8.bb | 39 ----------------------- 3 files changed, 95 deletions(-) delete mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.8.bb delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.8.bb delete mode 100644 meta/recipes-kernel/linux/linux-yocto_3.8.bb
meta/recipes-kernel/linux/linux-yocto-rt_3.8.bb deleted +0 -30
@@ -1,30 +0,0 @@ -require recipes-kernel/linux/linux-yocto.inc - -KBRANCH = "standard/preempt-rt/base" -KBRANCH_qemuppc = "standard/preempt-rt/qemuppc" - -LINUX_VERSION ?= "3.8.13" -LINUX_KERNEL_TYPE = "preempt-rt" - -KMETA = "meta" - -SRCREV_machine ?= "4fb187301ca153d496b2a96293dffde34d3b1a56" -SRCREV_machine_qemuppc ?= "547c4ea570933ab7ece9f10d2c46875b460cd337" -SRCREV_meta ?= "19e686b473ebf018c56c9eb839f5fbd88ecd9a5a" - -PR = "${INC_PR}.1" -PV = "${LINUX_VERSION}+git${SRCPV}" - -SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.8.git;bareclone=1;branch=${KBRANCH},meta;name=machine,meta" - -# Omit broken machines from COMPATIBLE_MACHINE -# qemuppc hangs at boot -# qemumips panics at boot -COMPATIBLE_MACHINE = "(qemux86|qemux86-64|qemuarm)" - -# Functionality flags -KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc features/taskstats/taskstats.scc" -KERNEL_FEATURES_append = " ${KERNEL_EXTRA_FEATURES}" -KERNEL_FEATURES_append_qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc" -KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc" -KERNEL_FEATURES_append = " ${@bb.utils.contains("TUNE_FEATURES", "mx32", " cfg/x32.scc", "" ,d)}"
meta/recipes-kernel/linux/linux-yocto-tiny_3.8.bb deleted +0 -26
@@ -1,26 +0,0 @@ -require recipes-kernel/linux/linux-yocto.inc - -# We need lzma (as CONFIG_KERNEL_LZMA=y) -DEPENDS += "xz-native" - -KBRANCH_DEFAULT = "standard/tiny/base" -KBRANCH = "${KBRANCH_DEFAULT}" -LINUX_KERNEL_TYPE = "tiny" -KCONFIG_MODE = "--allnoconfig" - -LINUX_VERSION ?= "3.8.13" - -KMETA = "meta" - -SRCREV_machine ?= "f20047520a57322f05d95a18a5fbd082fb15cb87" -SRCREV_meta ?= "19e686b473ebf018c56c9eb839f5fbd88ecd9a5a" - -PR = "${INC_PR}.1" -PV = "${LINUX_VERSION}+git${SRCPV}" - -SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.8.git;bareclone=1;branch=${KBRANCH},meta;name=machine,meta" - -COMPATIBLE_MACHINE = "(qemux86)" - -# Functionality flags -KERNEL_FEATURES = ""
meta/recipes-kernel/linux/linux-yocto_3.8.bb deleted +0 -39
@@ -1,39 +0,0 @@ -require recipes-kernel/linux/linux-yocto.inc - -KBRANCH_DEFAULT = "standard/base" -KBRANCH = "${KBRANCH_DEFAULT}" - -# board specific branches -KBRANCH_qemuarm = "standard/arm-versatile-926ejs" -KBRANCH_qemumips = "standard/mti-malta32" -KBRANCH_qemuppc = "standard/qemuppc" -KBRANCH_qemux86 = "standard/common-pc/base" -KBRANCH_qemux86-64 = "standard/common-pc-64/base" -KBRANCH_qemumips64 = "standard/mti-malta64" - -SRCREV_machine_qemuarm ?= "aa76cc28408376814752bd36fb0dcf0e25aa5ba3" -SRCREV_machine_qemumips ?= "aa0affda03c955678b26b2fb586f1d9505127871" -SRCREV_machine_qemumips64 ?= "077bff22c9951db6b35470ba17b1df2f2a91fefb" -SRCREV_machine_qemuppc ?= "698eada61d9385b42dd117858b943655b565084b" -SRCREV_machine_qemux86 ?= "f20047520a57322f05d95a18a5fbd082fb15cb87" -SRCREV_machine_qemux86-64 ?= "f20047520a57322f05d95a18a5fbd082fb15cb87" -SRCREV_machine ?= "f20047520a57322f05d95a18a5fbd082fb15cb87" -SRCREV_meta ?= "19e686b473ebf018c56c9eb839f5fbd88ecd9a5a" - -SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.8.git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta" - -LINUX_VERSION ?= "3.8.13" - -PR = "${INC_PR}.2" -PV = "${LINUX_VERSION}+git${SRCPV}" - -KMETA = "meta" - -COMPATIBLE_MACHINE = "qemuarm|qemux86|qemuppc|qemumips|qemumips64|qemux86-64" - -# Functionality flags -KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc" -KERNEL_FEATURES_append = " ${KERNEL_EXTRA_FEATURES}" -KERNEL_FEATURES_append_qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc" -KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc" -KERNEL_FEATURES_append = " ${@bb.utils.contains("TUNE_FEATURES", "mx32", " cfg/x32.scc", "" ,d)}"
Signature · 1 line
1.8.1.2
PATCH 10/13 linux-yocto/3.14: introduce versioned recipes
In reply to Bruce AshfieldThe release kernel for Yocto 1.5 is the 3.14 kernel, so we introduce the versioned recipes here.
--- meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb | 21 ++++++++++++ meta/recipes-kernel/linux/linux-yocto_3.14.bb | 37 ++++++++++++++++++++++ 2 files changed, 58 insertions(+) create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.14.bb
meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb new file +21 -0
@@ -0,0 +1,21 @@ +require recipes-kernel/linux/linux-yocto.inc + +KBRANCH = "standard/tiny/base" +LINUX_KERNEL_TYPE = "tiny" +KCONFIG_MODE = "--allnoconfig" + +LINUX_VERSION ?= "3.14-rc8" + +KMETA = "meta" + +SRCREV_machine ?= "fecc3fd7d31bd93766ff4f0431fecdbbfa4c3a7c" +SRCREV_meta ?= "3689f99f4d2a051e8d3ff72345a67d4d04a88020" + +PV = "${LINUX_VERSION}+git${SRCPV}" + +SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.14.git;bareclone=1;branch=${KBRANCH},meta;name=machine,meta" + +COMPATIBLE_MACHINE = "(qemux86)" + +# Functionality flags +KERNEL_FEATURES = ""
meta/recipes-kernel/linux/linux-yocto_3.14.bb new file +37 -0
@@ -0,0 +1,37 @@ +require recipes-kernel/linux/linux-yocto.inc + +KBRANCH = "standard/base" + +# board specific branches +KBRANCH_qemuarm = "standard/arm-versatile-926ejs" +KBRANCH_qemumips = "standard/mti-malta32" +KBRANCH_qemuppc = "standard/qemuppc" +KBRANCH_qemux86 = "standard/common-pc/base" +KBRANCH_qemux86-64 = "standard/common-pc-64/base" +KBRANCH_qemumips64 = "standard/mti-malta64" + +SRCREV_machine_qemuarm ?= "0654f2bd12d0297df0ee103192d218cb6ec7c6fe" +SRCREV_machine_qemumips ?= "7c62bc81b74205c6e09cca4997d28888aadbd507" +SRCREV_machine_qemuppc ?= "1e45bd09d77a7d98abb70a473184f176ee6130aa" +SRCREV_machine_qemux86 ?= "fecc3fd7d31bd93766ff4f0431fecdbbfa4c3a7c" +SRCREV_machine_qemux86-64 ?= "fecc3fd7d31bd93766ff4f0431fecdbbfa4c3a7c" +SRCREV_machine_qemumips64 ?= "b7834de6840292871f930ef0bd9a057b1dd4f676" +SRCREV_machine ?= "fecc3fd7d31bd93766ff4f0431fecdbbfa4c3a7c" +SRCREV_meta ?= "3689f99f4d2a051e8d3ff72345a67d4d04a88020" + +SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.14.git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta" + +LINUX_VERSION ?= "3.14-rc8" + +PV = "${LINUX_VERSION}+git${SRCPV}" + +KMETA = "meta" + +COMPATIBLE_MACHINE = "qemuarm|qemux86|qemuppc|qemumips|qemumips64|qemux86-64" + +# Functionality flags +KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc" +KERNEL_FEATURES_append = " ${KERNEL_EXTRA_FEATURES}" +KERNEL_FEATURES_append_qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc" +KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc" +KERNEL_FEATURES_append = " ${@bb.utils.contains("TUNE_FEATURES", "mx32", " cfg/x32.scc", "" ,d)}"
Signature · 1 line
1.8.1.2
Re: [PATCH 10/13] linux-yocto/3.14: introduce versioned recipes
Quoted 21 lines · Bruce Ashfield
The release kernel for Yocto 1.5 is the 3.14 kernel, so we introduce the versioned recipes here.
Signed-off-by Bruce Ashfield <[email protected]>--- meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb | 21 ++++++++++++ meta/recipes-kernel/linux/linux-yocto_3.14.bb | 37 ++++++++++++++++++++++ 2 files changed, 58 insertions(+) create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.14.bbmeta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb new file +4
-0@@ -0,0 +1,21 @@ +require recipes-kernel/linux/linux-yocto.inc + +KBRANCH = "standard/tiny/base" +LINUX_KERNEL_TYPE = "tiny"
meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb line 14
Quoted 10 lines
meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb new file +10
-0+KCONFIG_MODE = "--allnoconfig" + +LINUX_VERSION ?= "3.14-rc8" + +KMETA = "meta" + +SRCREV_machine ?= "fecc3fd7d31bd93766ff4f0431fecdbbfa4c3a7c" +SRCREV_meta ?= "3689f99f4d2a051e8d3ff72345a67d4d04a88020" + +PV = "${LINUX_VERSION}+git${SRCPV}"
I'm afraid we can't do this in such a simple way. The big issue is that according to our version comparison functions (in bitbake and in the package managers), "3.14-rc8" > "3.14". This will then break updates from package feeds.
The traditional way we've worked around this in times gone by is the rather ugly:
PV = "3.13+3.14-rc8+git${SRCPV}"
since in this case "3.14" > "3.13+3.14-rc8"
The better way to handle this would be "3.14~rc8" however not all of our package backends have support for "~" at this point so we can't do that. There is a long standing bug open about this.
The same issue also applies to the libc-headers recipe.
Cheers,
Richard
Re: [PATCH 10/13] linux-yocto/3.14: introduce versioned recipes
Quoted 43 lines · Richard Purdie
Quoted 21 lines · Bruce Ashfield
The release kernel for Yocto 1.5 is the 3.14 kernel, so we introduce the versioned recipes here.
Signed-off-by Bruce Ashfield <[email protected]>--- meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb | 21 ++++++++++++ meta/recipes-kernel/linux/linux-yocto_3.14.bb | 37 ++++++++++++++++++++++ 2 files changed, 58 insertions(+)create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.14.bb
meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb new file +4
-0@@ -0,0 +1,21 @@ +require recipes-kernel/linux/linux-yocto.inc + +KBRANCH = "standard/tiny/base" +LINUX_KERNEL_TYPE = "tiny"meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb line 14
Quoted 10 lines
meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb new file +10
-0+KCONFIG_MODE = "--allnoconfig" + +LINUX_VERSION ?= "3.14-rc8" + +KMETA = "meta" + +SRCREV_machine ?= "fecc3fd7d31bd93766ff4f0431fecdbbfa4c3a7c" +SRCREV_meta ?= "3689f99f4d2a051e8d3ff72345a67d4d04a88020" + +PV = "${LINUX_VERSION}+git${SRCPV}"I'm afraid we can't do this in such a simple way. The big issue is that according to our version comparison functions (in bitbake and in the package managers), "3.14-rc8" > "3.14". This will then break updates from package feeds.
The traditional way we've worked around this in times gone by is the rather ugly:
PV = "3.13+3.14-rc8+git${SRCPV}"
Quoted 7 lines
since in this case "3.14" > "3.13+3.14-rc8"
The better way to handle this would be "3.14~rc8" however not all of our package backends have support for "~" at this point so we can't do that. There is a long standing bug open about this.
The same issue also applies to the libc-headers recipe.
eeee. Since I don't do package feeds, it's never been a problem for me.
Wouldn't PE bump when I go to 3.14 work as well ? Or does that go away with the PR sever as well ?
I can muck with PV, or we can hold until Linus releases over the weekend, and I go with the released PVs.
What's your preference ?
Bruce
Quoted 6 lines
Cheers,
Richard
Re: [PATCH 10/13] linux-yocto/3.14: introduce versioned recipes
Quoted 50 lines · Bruce Ashfield
Quoted 49 lines · Richard Purdie
Quoted 21 lines · Bruce Ashfield
The release kernel for Yocto 1.5 is the 3.14 kernel, so we introduce the versioned recipes here.
Signed-off-by Bruce Ashfield <[email protected]>--- meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb | 21 ++++++++++++ meta/recipes-kernel/linux/linux-yocto_3.14.bb | 37 ++++++++++++++++++++++ 2 files changed, 58 insertions(+)create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.14.bb
meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb new file +4
-0@@ -0,0 +1,21 @@ +require recipes-kernel/linux/linux-yocto.inc + +KBRANCH = "standard/tiny/base" +LINUX_KERNEL_TYPE = "tiny"meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb line 14
Quoted 10 lines
meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb new file +10
-0+KCONFIG_MODE = "--allnoconfig" + +LINUX_VERSION ?= "3.14-rc8" + +KMETA = "meta" + +SRCREV_machine ?= "fecc3fd7d31bd93766ff4f0431fecdbbfa4c3a7c" +SRCREV_meta ?= "3689f99f4d2a051e8d3ff72345a67d4d04a88020" + +PV = "${LINUX_VERSION}+git${SRCPV}"I'm afraid we can't do this in such a simple way. The big issue is that according to our version comparison functions (in bitbake and in the package managers), "3.14-rc8" > "3.14". This will then break updates from package feeds.
The traditional way we've worked around this in times gone by is the rather ugly:
PV = "3.13+3.14-rc8+git${SRCPV}"
since in this case "3.14" > "3.13+3.14-rc8"
The better way to handle this would be "3.14~rc8" however not all of our package backends have support for "~" at this point so we can't do that. There is a long standing bug open about this.
Quoted 5 lines
Quoted 1 line
The same issue also applies to the libc-headers recipe.
eeee. Since I don't do package feeds, it's never been a problem for me.
Wouldn't PE bump when I go to 3.14 work as well ?
yes, but we were trying to use PE bumps only in cases where it's really needed, using sortable PV as RP suggested is IMHO better
Quoted 1 line
Or does that go away with the PR sever as well ?
no, sewer wont help
Quoted 19 lines
I can muck with PV, or we can hold until Linus releases over the weekend, and I go with the released PVs.
What's your preference ?
Bruce
Quoted 6 lines
Cheers,
Richard
Signature · 4 lines
_______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
Signature · 1 line
Martin 'JaMa' Jansa jabber: [email protected]
Re: [PATCH 10/13] linux-yocto/3.14: introduce versioned recipes
In reply to Bruce AshfieldQuoted 50 lines · Bruce Ashfield
Quoted 49 lines · Richard Purdie
Quoted 21 lines · Bruce Ashfield
The release kernel for Yocto 1.5 is the 3.14 kernel, so we introduce the versioned recipes here.
Signed-off-by Bruce Ashfield <[email protected]>--- meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb | 21 ++++++++++++ meta/recipes-kernel/linux/linux-yocto_3.14.bb | 37 ++++++++++++++++++++++ 2 files changed, 58 insertions(+)create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.14.bb
meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb new file +4
-0@@ -0,0 +1,21 @@ +require recipes-kernel/linux/linux-yocto.inc + +KBRANCH = "standard/tiny/base" +LINUX_KERNEL_TYPE = "tiny"meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb line 14
Quoted 10 lines
meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb new file +10
-0+KCONFIG_MODE = "--allnoconfig" + +LINUX_VERSION ?= "3.14-rc8" + +KMETA = "meta" + +SRCREV_machine ?= "fecc3fd7d31bd93766ff4f0431fecdbbfa4c3a7c" +SRCREV_meta ?= "3689f99f4d2a051e8d3ff72345a67d4d04a88020" + +PV = "${LINUX_VERSION}+git${SRCPV}"I'm afraid we can't do this in such a simple way. The big issue is that according to our version comparison functions (in bitbake and in the package managers), "3.14-rc8" > "3.14". This will then break updates from package feeds.
The traditional way we've worked around this in times gone by is the rather ugly:
PV = "3.13+3.14-rc8+git${SRCPV}"
since in this case "3.14" > "3.13+3.14-rc8"
The better way to handle this would be "3.14~rc8" however not all of our package backends have support for "~" at this point so we can't do that. There is a long standing bug open about this.
Quoted 6 lines
Quoted 1 line
The same issue also applies to the libc-headers recipe.
eeee. Since I don't do package feeds, it's never been a problem for me.
Wouldn't PE bump when I go to 3.14 work as well ? Or does that go away with the PR sever as well ?
A PE bump would work however we try not to use those, they're a last resort to correct things we can't otherwise fix. The PR server doesn't help here although in future I do hope we can teach it about PE too.
Quoted 4 lines
I can muck with PV, or we can hold until Linus releases over the weekend, and I go with the released PVs.
What's your preference ?
Might as well wait over the weekend. If Linus does go for a rc9, we'll need to merge a version with the modified PV though.
In the meantime I might pull this series into master-next for testing but it will not get added to master in its current form.
Cheers,
Richard
Re: [PATCH 10/13] linux-yocto/3.14: introduce versioned recipes
Quoted 62 lines · Richard Purdie
Quoted 50 lines · Bruce Ashfield
Quoted 49 lines · Richard Purdie
Quoted 21 lines · Bruce Ashfield
The release kernel for Yocto 1.5 is the 3.14 kernel, so we introduce the versioned recipes here.
Signed-off-by Bruce Ashfield <[email protected]>--- meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb | 21 ++++++++++++ meta/recipes-kernel/linux/linux-yocto_3.14.bb | 37 ++++++++++++++++++++++ 2 files changed, 58 insertions(+)create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.14.bb
meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb new file +4
-0@@ -0,0 +1,21 @@ +require recipes-kernel/linux/linux-yocto.inc + +KBRANCH = "standard/tiny/base" +LINUX_KERNEL_TYPE = "tiny"meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb line 14
Quoted 10 lines
meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb new file +10
-0+KCONFIG_MODE = "--allnoconfig" + +LINUX_VERSION ?= "3.14-rc8" + +KMETA = "meta" + +SRCREV_machine ?= "fecc3fd7d31bd93766ff4f0431fecdbbfa4c3a7c" +SRCREV_meta ?= "3689f99f4d2a051e8d3ff72345a67d4d04a88020" + +PV = "${LINUX_VERSION}+git${SRCPV}"I'm afraid we can't do this in such a simple way. The big issue is that according to our version comparison functions (in bitbake and in the package managers), "3.14-rc8" > "3.14". This will then break updates from package feeds.
The traditional way we've worked around this in times gone by is the rather ugly:
PV = "3.13+3.14-rc8+git${SRCPV}"
since in this case "3.14" > "3.13+3.14-rc8"
The better way to handle this would be "3.14~rc8" however not all of our package backends have support for "~" at this point so we can't do that. There is a long standing bug open about this.
Quoted 6 lines
Quoted 1 line
The same issue also applies to the libc-headers recipe.
eeee. Since I don't do package feeds, it's never been a problem for me.
Wouldn't PE bump when I go to 3.14 work as well ? Or does that go away with the PR sever as well ?
A PE bump would work however we try not to use those, they're a last resort to correct things we can't otherwise fix. The PR server doesn't help here although in future I do hope we can teach it about PE too.
Quoted 7 lines
Quoted 4 lines
I can muck with PV, or we can hold until Linus releases over the weekend, and I go with the released PVs.
What's your preference ?
Might as well wait over the weekend. If Linus does go for a rc9, we'll need to merge a version with the modified PV though.
Sounds good. I'm updating the PVs to the format you showed regardless. Might as well take a lesson from the comments in the review for next time, in particular since I'm going to split the versioned recipe a bit sooner for 1.7.
Cheers,
Bruce
Quoted 8 lines
In the meantime I might pull this series into master-next for testing but it will not get added to master in its current form.
Cheers,
Richard
Re: [PATCH 10/13] linux-yocto/3.14: introduce versioned recipes
In reply to Richard PurdieQuoted 65 lines · Richard Purdie
Quoted 50 lines · Bruce Ashfield
Quoted 49 lines · Richard Purdie
Quoted 21 lines · Bruce Ashfield
The release kernel for Yocto 1.5 is the 3.14 kernel, so we introduce the versioned recipes here.
Signed-off-by Bruce Ashfield <[email protected]>--- meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb | 21 ++++++++++++ meta/recipes-kernel/linux/linux-yocto_3.14.bb | 37 ++++++++++++++++++++++ 2 files changed, 58 insertions(+)create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.14.bb
meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb new file +4
-0@@ -0,0 +1,21 @@ +require recipes-kernel/linux/linux-yocto.inc + +KBRANCH = "standard/tiny/base" +LINUX_KERNEL_TYPE = "tiny"meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb line 14
Quoted 10 lines
meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb new file +10
-0+KCONFIG_MODE = "--allnoconfig" + +LINUX_VERSION ?= "3.14-rc8" + +KMETA = "meta" + +SRCREV_machine ?= "fecc3fd7d31bd93766ff4f0431fecdbbfa4c3a7c" +SRCREV_meta ?= "3689f99f4d2a051e8d3ff72345a67d4d04a88020" + +PV = "${LINUX_VERSION}+git${SRCPV}"I'm afraid we can't do this in such a simple way. The big issue is that according to our version comparison functions (in bitbake and in the package managers), "3.14-rc8" > "3.14". This will then break updates from package feeds.
The traditional way we've worked around this in times gone by is the rather ugly:
PV = "3.13+3.14-rc8+git${SRCPV}"
since in this case "3.14" > "3.13+3.14-rc8"
The better way to handle this would be "3.14~rc8" however not all of our package backends have support for "~" at this point so we can't do that. There is a long standing bug open about this.
Quoted 6 lines
Quoted 1 line
The same issue also applies to the libc-headers recipe.
eeee. Since I don't do package feeds, it's never been a problem for me.
Wouldn't PE bump when I go to 3.14 work as well ? Or does that go away with the PR sever as well ?
A PE bump would work however we try not to use those, they're a last resort to correct things we can't otherwise fix. The PR server doesn't help here although in future I do hope we can teach it about PE too.
Quoted 3 lines
I can muck with PV, or we can hold until Linus releases over the weekend, and I go with the released PVs.
Quoted 7 lines
Quoted 1 line
What's your preference ?
Might as well wait over the weekend. If Linus does go for a rc9, we'll need to merge a version with the modified PV though.
In the meantime I might pull this series into master-next for testing but it will not get added to master in its current form.
FWIW: I just fixed the PVs of libc-headers and linux-yocto_3.14 to be the 3.13+ variety.
All other comments are also incorporated and the branches repushed.
Outside of needing to override the TC libc headers default of 3.14 (that I left in, expecting the full update) in local.conf, all builds continue to work.
Bruce
Quoted 5 lines
Cheers,
Richard
PATCH 11/13 linux-libc-headers: add 3.14 libc headers
In reply to Bruce AshfieldIntroduce the 3.14 linux-libc-headers recipe, now that the 3.14 kernel is available, and the default for the qemu reference BSPs.
The three patches which were required for the previous 3.10 libc-headers are not required for 3.14 and can be ignored.
--- .../linux-libc-headers/linux-libc-headers_3.14.bb | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.14.bb
meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.14.bb new file +13 -0
@@ -0,0 +1,13 @@ +require linux-libc-headers.inc + +# The hardcoded -rc8 is temporary, we are pretending that 3.14-rc is the full 3.14 +# tree, to avoid needing to shuffle the recipe name when it releases. +FETCH_VER="3.14-rc8" + +S="${WORKDIR}/linux-${FETCH_VER}" +SRC_URI = "${KERNELORG_MIRROR}/linux/kernel/v3.x/testing/linux-${FETCH_VER}.tar.xz" + +SRC_URI[md5sum] = "f7295bcc13c47b6bee924dde5057f1e8" +SRC_URI[sha256sum] = "20b3a956e2b5b56b5addcf46a92722eb96830e2d24efe8ea11ce1ec4a1a874ba" + +
Signature · 1 line
1.8.1.2
PATCH 12/13 libc-headers: set TC default to 3.14
In reply to Bruce Ashfield--- meta/conf/distro/include/tcmode-default.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
meta/conf/distro/include/tcmode-default.inc +1 -1
@@ -22,7 +22,7 @@ SDKGCCVERSION ?= "${GCCVERSION}" BINUVERSION ?= "2.24" EGLIBCVERSION ?= "2.19" UCLIBCVERSION ?= "0.9.33+git%" -LINUXLIBCVERSION ?= "3.10" +LINUXLIBCVERSION ?= "3.14" PREFERRED_VERSION_gcc ?= "${GCCVERSION}" PREFERRED_VERSION_gcc-cross ?= "${GCCVERSION}"
Signature · 1 line
1.8.1.2
PATCH 13/13 linux-libc-headers: remove 3.10 recipe
In reply to Bruce Ashfield3.14 is now the reference for libc-headers. After building and booting 3.x based BSPs against the 3.14 headers, we can safely remove the old version and patches that are now part of the mainline kernel.
--- ...1-ptrace.h-remove-ptrace_peeksiginfo_args.patch | 50 ------------------ ...lude-asm-byteorder.h-in-linux-raid-md_p.h.patch | 34 ------------- ...efile.headersinst-install-headers-from-sc.patch | 59 ---------------------- .../linux-libc-headers/linux-libc-headers_3.10.bb | 11 ---- 4 files changed, 154 deletions(-) delete mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers/0001-ptrace.h-remove-ptrace_peeksiginfo_args.patch delete mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers/UAPI-include-asm-byteorder.h-in-linux-raid-md_p.h.patch delete mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers/scripts-Makefile.headersinst-install-headers-from-sc.patch delete mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
meta/recipes-kernel/linux-libc-headers/linux-libc-headers/0001-ptrace.h-remove-ptrace_peeksiginfo_args.patch deleted +0 -50
@@ -1,50 +0,0 @@ -From 7dddfb8fec5317ea16154d30e8e18b6559979b60 Mon Sep 17 00:00:00 2001 -From: Bruce Ashfield <[email protected]> -Date: Sun, 25 Aug 2013 22:51:07 -0400 -Subject: [PATCH] ptrace.h: remove ptrace_peeksiginfo_args - -The addition of ptrace_peeksiginfo_args to the uapi in kernel commit -84c751bd [ptrace: add ability to retrieve signals without removing from a queue (v4)] -means that existing applications using glibc versions that define ptrace_peeksiginfo_args -in sys/ptrace.h will get duplicate structure definitions like: - - | In file included from /poky-master/build/tmp/work/i586-poky-linux/strace/4.8-r0/strace-4.8/process.c:66:0: - | /poky-master/build/tmp/sysroots/qemux86/usr/include/linux/ptrace.h:58:8: error: redefinition of 'struct ptrace_peeksiginfo_args' - | struct ptrace_peeksiginfo_args { - | ^ - | In file included from /poky-master/build/tmp/work/i586-poky-linux/strace/4.8-r0/strace-4.8/defs.h:159:0, - | from /poky-master/build/tmp/work/i586-poky-linux/strace/4.8-r0/strace-4.8/process.c:37: - | /poky-master/build/tmp/sysroots/qemux86/usr/include/sys/ptrace.h:191:8: note: originally defined here - | struct ptrace_peeksiginfo_args - | ^ - | make[2]: *** [process.o] Error 1 - -Reverting to the previous status of not exporting this structure temporarily -fixes applications, until they can be adjusted to not mix sys/ptrace.h and -linux/ptrace.h includes. - -Signed-off-by: Bruce Ashfield <[email protected]> ---- - include/uapi/linux/ptrace.h | 6 ------ - 1 file changed, 6 deletions(-) - -diff --git a/include/uapi/linux/ptrace.h b/include/uapi/linux/ptrace.h -index 52ebcc8..524599d 100644 ---- a/include/uapi/linux/ptrace.h -+++ b/include/uapi/linux/ptrace.h -@@ -55,12 +55,6 @@ - - #define PTRACE_PEEKSIGINFO 0x4209 - --struct ptrace_peeksiginfo_args { -- __u64 off; /* from which siginfo to start */ -- __u32 flags; -- __s32 nr; /* how may siginfos to take */ --}; -- - /* Read signals from a shared (process wide) queue */ - #define PTRACE_PEEKSIGINFO_SHARED (1 << 0) - --- -1.7.10.4 -
meta/recipes-kernel/linux-libc-headers/linux-libc-headers/UAPI-include-asm-byteorder.h-in-linux-raid-md_p.h.patch deleted +0 -34
@@ -1,34 +0,0 @@ -From c0f8bd146a8b3e630798561c605f5669823107af Mon Sep 17 00:00:00 2001 -From: Aurelien Jarno <[email protected]> -Date: Thu, 14 Nov 2013 15:16:19 +1100 -Subject: [PATCH] UAPI: include <asm/byteorder.h> in linux/raid/md_p.h - -linux/raid/md_p.h is using conditionals depending on endianess and fails -with an error if neither of __BIG_ENDIAN, __LITTLE_ENDIAN or -__BYTE_ORDER are defined, but it doesn't include any header which can -define these constants. This make this header unusable alone. - -This patch adds a #include <asm/byteorder.h> at the beginning of this -header to make it usable alone. This is needed to compile klibc on MIPS. - -Signed-off-by: Aurelien Jarno <[email protected]> -Signed-off-by: NeilBrown <[email protected]> ---- - include/uapi/linux/raid/md_p.h | 1 + - 1 file changed, 1 insertion(+) - -diff --git a/include/uapi/linux/raid/md_p.h b/include/uapi/linux/raid/md_p.h -index fe1a540..f7cf7f3 100644 ---- a/include/uapi/linux/raid/md_p.h -+++ b/include/uapi/linux/raid/md_p.h -@@ -16,6 +16,7 @@ - #define _MD_P_H - - #include <linux/types.h> -+#include <asm/byteorder.h> - - /* - * RAID superblock. --- -1.8.1.2 -
meta/recipes-kernel/linux-libc-headers/linux-libc-headers/scripts-Makefile.headersinst-install-headers-from-sc.patch deleted +0 -59
59 lines not on this page · raw message
meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb deleted +0 -11
@@ -1,11 +0,0 @@ -require linux-libc-headers.inc - -SRC_URI += "file://0001-ptrace.h-remove-ptrace_peeksiginfo_args.patch" -SRC_URI += "file://scripts-Makefile.headersinst-install-headers-from-sc.patch" - -# fixes klibc build for MIPS, drop when libc-headers > 3.13 -SRC_URI += "file://UAPI-include-asm-byteorder.h-in-linux-raid-md_p.h.patch" - -SRC_URI[md5sum] = "72d0a9b3e60cd86fabcd3f24b1708944" -SRC_URI[sha256sum] = "46c9e55e1fddf40813b8d697d5645037a8e2af5c1a8dff52b3fe82b5021582b8" -
Signature · 1 line
1.8.1.2