linux-yocto: consolidated pull request
cover linux-yocto: consolidated pull request
Hi all,
Here is a slightly delayed consolidated pull request for the kernels, and kernel tools. I've been fighting with boot issues, which have now been resolved and were unrelated to this update.
I've avoided merging korg -stable updates for now to keep the kernel trees consistent and not introduce any extra churn.
Everything I've included in this pull reques is either a bug fix to the tools, or an addition of config/branches that won't impact existing users.
The tools fixes deal with an issue found with the yocto-bsp tool, and another that Saul found when using a kernel-cache with a korg based tree. I've run regression here, and everything looks sane.
Take what you think looks safe, and definitely feed it to the autobuilder to see if I missed anything.
Cheers,
Bruce
The following changes since commit 505a82673ac2487df5ea343a6422c2fc47018831:
build-appliance-image: Update to jethro head revision (2015-10-21 23:13:11 +0100)
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 (6):
linux-yocto: axxia configuration updates linux-yocto/4.1: drm/i915: Fix the VBT child device parsing for BSW
linux-yocto: nf_tables: Add nf_tables feature
kern-tools: avoid duplicate .scc file processing
linux-yocto: skip kernel meta data branches when finding machine
branch
linux-yocto/3.19: fix ARM boot with gcc5.x
meta/classes/kernel-yocto.bbclass | 4 +++- .../recipes-kernel/kern-tools/kern-tools-native_git.bb | 2 +- meta/recipes-kernel/linux/linux-yocto-rt_3.14.bb | 2 +- meta/recipes-kernel/linux/linux-yocto-rt_4.1.bb | 4 ++-- meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb | 2 +- meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb | 4 ++-- meta/recipes-kernel/linux/linux-yocto_3.14.bb | 2 +- meta/recipes-kernel/linux/linux-yocto_3.19.bb | 4 ++-- meta/recipes-kernel/linux/linux-yocto_4.1.bb | 18 +++++++++--------- 9 files changed, 22 insertions(+), 20 deletions(-)
Signature · 1 line
2.1.0
PATCH 1/6 linux-yocto: axxia configuration updates
Updating the configuration fragments for the Intel Axxia on the 3.14 and 4.1 kernels.
--- meta/recipes-kernel/linux/linux-yocto-rt_3.14.bb | 2 +- meta/recipes-kernel/linux/linux-yocto-rt_4.1.bb | 2 +- meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb | 2 +- meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb | 2 +- meta/recipes-kernel/linux/linux-yocto_3.14.bb | 2 +- meta/recipes-kernel/linux/linux-yocto_4.1.bb | 2 +- 6 files changed, 6 insertions(+), 6 deletions(-)
meta/recipes-kernel/linux/linux-yocto-rt_3.14.bb +1 -1
@@ -5,7 +5,7 @@ require recipes-kernel/linux/linux-yocto.inc SRCREV_machine ?= "8281915527ba8d79e59906c02f28e7aa11424723" SRCREV_machine_qemuppc ?= "5e7d372ebc327f28656fc972fab55605eea8aec3" -SRCREV_meta ?= "3a09b38a9f5015c56d99d17aa7c2f200c566249b" +SRCREV_meta ?= "060fa80b7996250001ee90c50a4978c8fdb87fc4" SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.14.git;branch=${KBRANCH};name=machine \ git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-3.14;destsuffix=${KMETA}"
meta/recipes-kernel/linux/linux-yocto-rt_4.1.bb +1 -1
@@ -3,7 +3,7 @@ KBRANCH ?= "standard/preempt-rt/base" require recipes-kernel/linux/linux-yocto.inc SRCREV_machine ?= "8acaa791408f146069473a96e3d98bed8be86244" -SRCREV_meta ?= "3d8f1378d07dbc052ca8a7c22297339ad7998b5e" +SRCREV_meta ?= "d8bbf59771fb915fa71debc8591bf6c69d8fa49c" SRC_URI = "git://git.yoctoproject.org/linux-yocto-4.1.git;branch=${KBRANCH};name=machine \ git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.1;destsuffix=${KMETA}"
meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb +1 -1
@@ -10,7 +10,7 @@ KMETA = "kernel-meta" KCONF_BSP_AUDIT_LEVEL = "2" SRCREV_machine ?= "578602a722dbfb260801f3b37c6eafd2abb2340d" -SRCREV_meta ?= "3a09b38a9f5015c56d99d17aa7c2f200c566249b" +SRCREV_meta ?= "060fa80b7996250001ee90c50a4978c8fdb87fc4" PV = "${LINUX_VERSION}+git${SRCPV}"
meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb +1 -1
@@ -10,7 +10,7 @@ KMETA = "kernel-meta" KCONF_BSP_AUDIT_LEVEL = "2" SRCREV_machine ?= "52a4a9f4a2b408ef3a0745372e44cc362832d86d" -SRCREV_meta ?= "3d8f1378d07dbc052ca8a7c22297339ad7998b5e" +SRCREV_meta ?= "d8bbf59771fb915fa71debc8591bf6c69d8fa49c" PV = "${LINUX_VERSION}+git${SRCPV}"
meta/recipes-kernel/linux/linux-yocto_3.14.bb +1 -1
@@ -19,7 +19,7 @@ SRCREV_machine_qemux86 ?= "af1f7f586bd32d39c057f17606991b887eadb389" SRCREV_machine_qemux86-64 ?= "578602a722dbfb260801f3b37c6eafd2abb2340d" SRCREV_machine_qemumips64 ?= "a63d40b860a6d255005a541894d53729090b40ea" SRCREV_machine ?= "578602a722dbfb260801f3b37c6eafd2abb2340d" -SRCREV_meta ?= "3a09b38a9f5015c56d99d17aa7c2f200c566249b" +SRCREV_meta ?= "060fa80b7996250001ee90c50a4978c8fdb87fc4" SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.14.git;branch=${KBRANCH};name=machine; \ git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-3.14;destsuffix=${KMETA}"
meta/recipes-kernel/linux/linux-yocto_4.1.bb +1 -1
@@ -19,7 +19,7 @@ SRCREV_machine_qemux86 ?= "52a4a9f4a2b408ef3a0745372e44cc362832d86d" SRCREV_machine_qemux86-64 ?= "52a4a9f4a2b408ef3a0745372e44cc362832d86d" SRCREV_machine_qemumips64 ?= "8458e792e2c595f48bc5b2924e20e844f2a96522" SRCREV_machine ?= "52a4a9f4a2b408ef3a0745372e44cc362832d86d" -SRCREV_meta ?= "3d8f1378d07dbc052ca8a7c22297339ad7998b5e" +SRCREV_meta ?= "d8bbf59771fb915fa71debc8591bf6c69d8fa49c" SRC_URI = "git://git.yoctoproject.org/linux-yocto-4.1.git;name=machine;branch=${KBRANCH}; \ git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.1;destsuffix=${KMETA}"
Signature · 1 line
2.1.0
PATCH 3/6 linux-yocto: nf_tables: Add nf_tables feature
In reply to Bruce AshfieldUpdating the META SRCREVs to make the nf_tables feature available.
--- meta/recipes-kernel/linux/linux-yocto-rt_4.1.bb | 2 +- meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb | 2 +- meta/recipes-kernel/linux/linux-yocto_4.1.bb | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)
meta/recipes-kernel/linux/linux-yocto-rt_4.1.bb +1 -1
@@ -3,7 +3,7 @@ KBRANCH ?= "standard/preempt-rt/base" require recipes-kernel/linux/linux-yocto.inc SRCREV_machine ?= "f7e4bbfef684e29b1257eaf2d7f534b38e2e1b1e" -SRCREV_meta ?= "d8bbf59771fb915fa71debc8591bf6c69d8fa49c" +SRCREV_meta ?= "aed902160251d69cc28d1e69a4f692e8ea8fa13b" SRC_URI = "git://git.yoctoproject.org/linux-yocto-4.1.git;branch=${KBRANCH};name=machine \ git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.1;destsuffix=${KMETA}"
meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb +1 -1
@@ -10,7 +10,7 @@ KMETA = "kernel-meta" KCONF_BSP_AUDIT_LEVEL = "2" SRCREV_machine ?= "dbe692d91c8e55d1430f2c45fd578c8e4e71e482" -SRCREV_meta ?= "d8bbf59771fb915fa71debc8591bf6c69d8fa49c" +SRCREV_meta ?= "aed902160251d69cc28d1e69a4f692e8ea8fa13b" PV = "${LINUX_VERSION}+git${SRCPV}"
meta/recipes-kernel/linux/linux-yocto_4.1.bb +1 -1
@@ -19,7 +19,7 @@ SRCREV_machine_qemux86 ?= "dbe692d91c8e55d1430f2c45fd578c8e4e71e482" SRCREV_machine_qemux86-64 ?= "dbe692d91c8e55d1430f2c45fd578c8e4e71e482" SRCREV_machine_qemumips64 ?= "2684711a16ed21f114d834742f860cee532f7438" SRCREV_machine ?= "dbe692d91c8e55d1430f2c45fd578c8e4e71e482" -SRCREV_meta ?= "d8bbf59771fb915fa71debc8591bf6c69d8fa49c" +SRCREV_meta ?= "aed902160251d69cc28d1e69a4f692e8ea8fa13b" SRC_URI = "git://git.yoctoproject.org/linux-yocto-4.1.git;name=machine;branch=${KBRANCH}; \ git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.1;destsuffix=${KMETA}"
Signature · 1 line
2.1.0
PATCH 4/6 kern-tools: avoid duplicate .scc file processing
In reply to Bruce AshfieldWith the recent changes to improve patch processing times, the ability to skip already applied patches is not active by default.
The automatic detection and resume was hiding issues with the include files generated by scripts like yocto-bsp.
If a .scc file that contains a patch is included twice, the patch is applied twice, and the second appliation fails for obvious reasons.
We can partially fix this by ensuring that already included configuration fragments are not forced into the meta-series.
.scc files that are explicitly listed twice will continue to fail, and recipes must be modified to avoid this.
[YOCTO: #8486]
--- meta/recipes-kernel/kern-tools/kern-tools-native_git.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
meta/recipes-kernel/kern-tools/kern-tools-native_git.bb +1 -1
@@ -4,7 +4,7 @@ LIC_FILES_CHKSUM = "file://git/tools/kgit;beginline=5;endline=9;md5=d8d1d729a70c DEPENDS = "git-native" -SRCREV = "1fb91c2965193df894089fbcbcafe3bf775c21fd" +SRCREV = "17d89d1861b532bbf1a81c1f024953e440db8de7" PR = "r12" PV = "0.2+git${SRCPV}"
Signature · 1 line
2.1.0
PATCH 6/6 linux-yocto/3.19: fix ARM boot with gcc5.x
In reply to Bruce AshfieldUpdating the SRCREVs to apply the same fix as 3.14 and 4.1 already have to fix qemuarm boots with gcc5.x
[YOCTO: #8415]
--- meta/recipes-kernel/linux/linux-yocto_3.19.bb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
meta/recipes-kernel/linux/linux-yocto_3.19.bb +2 -2
@@ -11,14 +11,14 @@ KBRANCH_qemux86 ?= "standard/common-pc" KBRANCH_qemux86-64 ?= "standard/common-pc-64/base" KBRANCH_qemumips64 ?= "standard/mti-malta64" -SRCREV_machine_qemuarm ?= "963b4df663dba2584ac864e0c016825de0046558" +SRCREV_machine_qemuarm ?= "857048f10bfe7089ca6007e72431f1c098b07115" SRCREV_machine_qemuarm64 ?= "e152349de59b43b2a75f2c332b44171df461d5a0" SRCREV_machine_qemumips ?= "cedbbc7b5e72df2e820bb9e7885f12132c5e2fff" SRCREV_machine_qemuppc ?= "23a83386e10986a63e6cef712a045445499d002b" SRCREV_machine_qemux86 ?= "e152349de59b43b2a75f2c332b44171df461d5a0" SRCREV_machine_qemux86-64 ?= "e152349de59b43b2a75f2c332b44171df461d5a0" SRCREV_machine_qemumips64 ?= "3eb70cea3532e22ab1b6da9864446621229e6616" -SRCREV_machine ?= "e152349de59b43b2a75f2c332b44171df461d5a0" +SRCREV_machine ?= "151571a39785218a57c3ae3355cd63694890cc8d" SRCREV_meta ?= "1016714868249d64fc16692fd7679672b1efa17b" SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.19.git;name=machine;branch=${KBRANCH}; \
Signature · 1 line
2.1.0
PATCH 2/6 linux-yocto/4.1: drm/i915: Fix the VBT child device parsing for BSW
In reply to Bruce AshfieldUpdating the 4.1 SRCREVs to integrate the following fix:
[
drm/i915: Fix the VBT child device parsing for BSW
Recent BSW VBT has a VBT child device size 37 bytes instead of the 33 bytes our code assumes. This means we fail to parse the VBT and thus fail to detect eDP ports properly and just register them as DP ports instead.
Fix it up by using the reported child device size from the VBT instead of assuming it matches out struct defintions.
The latest spec I have shows that the child device size should be 36 bytes for rev >= 195, however on my BSW the size is actually 37 bytes. And our current struct definition is 33 bytes.
Feels like the entire VBT parses would need to be rewritten to handle changes in the layout better, but for now I've decided to do just the bare minimum to get my eDP port back.
]
--- meta/recipes-kernel/linux/linux-yocto-rt_4.1.bb | 2 +- meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb | 2 +- meta/recipes-kernel/linux/linux-yocto_4.1.bb | 16 ++++++++-------- 3 files changed, 10 insertions(+), 10 deletions(-)
meta/recipes-kernel/linux/linux-yocto-rt_4.1.bb +1 -1
@@ -2,7 +2,7 @@ KBRANCH ?= "standard/preempt-rt/base" require recipes-kernel/linux/linux-yocto.inc -SRCREV_machine ?= "8acaa791408f146069473a96e3d98bed8be86244" +SRCREV_machine ?= "f7e4bbfef684e29b1257eaf2d7f534b38e2e1b1e" SRCREV_meta ?= "d8bbf59771fb915fa71debc8591bf6c69d8fa49c" SRC_URI = "git://git.yoctoproject.org/linux-yocto-4.1.git;branch=${KBRANCH};name=machine \
meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb +1 -1
@@ -9,7 +9,7 @@ LINUX_VERSION ?= "4.1.8" KMETA = "kernel-meta" KCONF_BSP_AUDIT_LEVEL = "2" -SRCREV_machine ?= "52a4a9f4a2b408ef3a0745372e44cc362832d86d" +SRCREV_machine ?= "dbe692d91c8e55d1430f2c45fd578c8e4e71e482" SRCREV_meta ?= "d8bbf59771fb915fa71debc8591bf6c69d8fa49c" PV = "${LINUX_VERSION}+git${SRCPV}"
meta/recipes-kernel/linux/linux-yocto_4.1.bb +8 -8
@@ -11,14 +11,14 @@ KBRANCH_qemux86 ?= "standard/base" KBRANCH_qemux86-64 ?= "standard/base" KBRANCH_qemumips64 ?= "standard/mti-malta64" -SRCREV_machine_qemuarm ?= "187e28708b478b5d01a7df9e6410a340347e4819" -SRCREV_machine_qemuarm64 ?= "52a4a9f4a2b408ef3a0745372e44cc362832d86d" -SRCREV_machine_qemumips ?= "dd6b1f0940dbffd5e0feef2beecbc89a25da8e8f" -SRCREV_machine_qemuppc ?= "52a4a9f4a2b408ef3a0745372e44cc362832d86d" -SRCREV_machine_qemux86 ?= "52a4a9f4a2b408ef3a0745372e44cc362832d86d" -SRCREV_machine_qemux86-64 ?= "52a4a9f4a2b408ef3a0745372e44cc362832d86d" -SRCREV_machine_qemumips64 ?= "8458e792e2c595f48bc5b2924e20e844f2a96522" -SRCREV_machine ?= "52a4a9f4a2b408ef3a0745372e44cc362832d86d" +SRCREV_machine_qemuarm ?= "bc11ecf659e30c8687604e086450ae1ff90c0169" +SRCREV_machine_qemuarm64 ?= "dbe692d91c8e55d1430f2c45fd578c8e4e71e482" +SRCREV_machine_qemumips ?= "181e2c553ffaae19d08a6730e98d288c7e337d39" +SRCREV_machine_qemuppc ?= "dbe692d91c8e55d1430f2c45fd578c8e4e71e482" +SRCREV_machine_qemux86 ?= "dbe692d91c8e55d1430f2c45fd578c8e4e71e482" +SRCREV_machine_qemux86-64 ?= "dbe692d91c8e55d1430f2c45fd578c8e4e71e482" +SRCREV_machine_qemumips64 ?= "2684711a16ed21f114d834742f860cee532f7438" +SRCREV_machine ?= "dbe692d91c8e55d1430f2c45fd578c8e4e71e482" SRCREV_meta ?= "d8bbf59771fb915fa71debc8591bf6c69d8fa49c" SRC_URI = "git://git.yoctoproject.org/linux-yocto-4.1.git;name=machine;branch=${KBRANCH}; \
Signature · 1 line
2.1.0
PATCH 5/6 linux-yocto: skip kernel meta data branches when finding machine branch
In reply to Bruce AshfieldBefore the fetcher validated the specified SRCREV was reachable on a specified branch, linux-yocto style kernel's were comparing the value of KBRANCH and branch on the SRC_URI and then allowing a SRC_URI specified branch to override KBRANCH.
With the introduction of kernel meta data on the SRC_URI, this routine is incorrectly picking up a kernel-cache repository and then attempting to apply that branch information to the kernel repository.
The rationalization of the branch specification is largely no longer required, and will may be removed in the future. But for now, to keep changes minimal, we can simply not return branch information that comes from kernel meta data by checking the 'type' parameter and skipping if it is of type 'kmeta'.
--- meta/classes/kernel-yocto.bbclass | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
meta/classes/kernel-yocto.bbclass +3 -1
@@ -52,7 +52,9 @@ def get_machine_branch(d, default): parm = urldata.parm if "branch" in parm: branches = urldata.parm.get("branch").split(',') - return branches[0] + btype = urldata.parm.get("type") + if btype != "kmeta": + return branches[0] return default
Signature · 1 line
2.1.0
Re: [PATCH 5/6] linux-yocto: skip kernel meta data branches when finding machine branch
Quoted 9 lines · Bruce Ashfield
Before the fetcher validated the specified SRCREV was reachable on a specified branch, linux-yocto style kernel's were comparing the value of KBRANCH and branch on the
SRC_URIand then allowing aSRC_URIspecified branch to override KBRANCH.With the introduction of kernel meta data on the
SRC_URI, this routine is incorrectly picking up a kernel-cache repository and then attempting to apply that branch information to the kernel repository.
Quoted 7 lines
The rationalization of the branch specification is largely no longer required, and will may be removed in the future. But for now, to keep changes minimal, we can simply not return branch information that comes from kernel meta data by checking the 'type' parameter and skipping if it is of type 'kmeta'.
Signed-off-by Bruce Ashfield <[email protected]>
Quoted 19 lines
--- meta/classes/kernel-yocto.bbclass | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)meta/classes/kernel-yocto.bbclass +3
-1@@ -52,7 +52,9 @@ def get_machine_branch(d, default): parm = urldata.parm if "branch" in parm: branches = urldata.parm.get("branch").split(',') - return branches[0] + btype = urldata.parm.get("type") + if btype != "kmeta": + return branches[0] return default