Skip to contentSkip to conversation

linux-yocto: consolidated pull request

PATCH In review Bruce Ashfield 4 participants 11 messages Mar 24, 2015 – Apr 13, 2015

lore
Share & tools
lore
#0 lore raw

cover linux-yocto: consolidated pull request

Hi all,

Here is the latest linux-yocto consolidated pull request. It is a mix of kernel version -stable imports (CVEs and fixes), kernel configuration changes, a documentation update and kernel configuration enhancement.

The -stable updates are routine, and I build/boot tested them here (with my fixup commits being evidence). These are ready for a round of autobuilder/soak testing.

The only other change is the addition of the ability to use a defconfig that is maintained within a kernel tree. This enhacement request came from the raspberrypi2 maintainers. We went through a few revisions and test cycles on this (see YOCTO: 7474 for the details).

The final result has no impact on existing configuration workflows, but does allow an in-tree config to be copied out into WORKDIR and then incorporated with other fragments as part of kconfig processing. A new variable is introduced for specifying the defconfig KBUILD_DEFCONFIG, and I'll work with Scott to make sure this is documented in the appropriate locations.

Cheers,

Bruce

The following changes since commit 369932178fe9e7aa4a6d0e2ef1e2e539be701d02:

yocto-bsp: Update templates to 3.19 kernel (2015-03-24 10:06:03 +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 (5):
kernel-yocto: allow in-tree defconfigs linux-yocto/3.19: configuration updates and stable import linux-yocto/3.14: integrate korg stable and meta data changes linux-yocto/3.19: fixes for Intel core warnings
skeleton: clarify linux-yocto-custom workflow

 .../recipes-kernel/linux/linux-yocto-custom.bb     |  6 ++--
 meta/classes/kernel-yocto.bbclass                  | 39 ++++++++++++++++++++--
 meta/recipes-kernel/linux/linux-yocto-rt_3.14.bb   |  8 ++---
 meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb |  6 ++--
 meta/recipes-kernel/linux/linux-yocto-tiny_3.19.bb |  6 ++--
 meta/recipes-kernel/linux/linux-yocto_3.14.bb      | 20 +++++------
 meta/recipes-kernel/linux/linux-yocto_3.19.bb      | 20 +++++------
 7 files changed, 69 insertions(+), 36 deletions(-)
Signature · 1 line
2.1.0
#1 lore raw

PATCH 1/5 kernel-yocto: allow in-tree defconfigs

In a similar manner to the kernel itself, which does the following to bring a defconfig into the configuration:

    defconfig: $(obj)/conf
    ifeq ($(KBUILD_DEFCONFIG),)
        $< --defconfig $(Kconfig)
    else
        @echo "*** Default configuration is based on '$(KBUILD_DEFCONFIG)'"
        $(Q)$< --defconfig=arch/$(SRCARCH)/configs/$(KBUILD_DEFCONFIG) $(Kconfig)
    endif

We do the same with the linux-yocto configuration processing. If a defconfig is specified via the KBUILD_DEFCONFIG variable, we copy it from the source tree, into a common location and normalized "defconfig" name, where the rest of the process will include and incorporate it into the configuration process.

If the fetcher has already placed a defconfig in WORKDIR (from the SRC_URI), we don't overwrite it, but instead warn the user that SRC_URI defconfigs take precedence.

[YOCTO: #7474]

---
 meta/classes/kernel-yocto.bbclass | 39 +++++++++++++++++++++++++++++++++++++--
 1 file changed, 37 insertions(+), 2 deletions(-)
meta/classes/kernel-yocto.bbclass +37 -2
index 1e226a5722ac..14551a23f28c 100644
@@ -56,6 +56,7 @@ def get_machine_branch(d, default):
     return default
 
 do_kernel_metadata() {
+	set +e
 	cd ${S}
 	export KMETA=${KMETA}
 
@@ -75,6 +76,41 @@ do_kernel_metadata() {
 		machine_srcrev="${SRCREV}"
 	fi
 
+	# In a similar manner to the kernel itself:
+	#
+	#   defconfig: $(obj)/conf
+	#   ifeq ($(KBUILD_DEFCONFIG),)
+	#	$< --defconfig $(Kconfig)
+	#   else
+	#	@echo "*** Default configuration is based on '$(KBUILD_DEFCONFIG)'"
+	#	$(Q)$< --defconfig=arch/$(SRCARCH)/configs/$(KBUILD_DEFCONFIG) $(Kconfig)
+	#   endif
+	#
+	# If a defconfig is specified via the KBUILD_DEFCONFIG variable, we copy it
+	# from the source tree, into a common location and normalized "defconfig" name,
+	# where the rest of the process will include and incoroporate it into the build
+	#
+	# If the fetcher has already placed a defconfig in WORKDIR (from the SRC_URI),
+	# we don't overwrite it, but instead warn the user that SRC_URI defconfigs take
+	# precendence.
+	#
+	if [ -n "${KBUILD_DEFCONFIG}" ]; then
+		if [ -f "${S}/arch/${ARCH}/configs/${KBUILD_DEFCONFIG}" ]; then
+			if [ -f "${WORKDIR}/defconfig" ]; then
+				# If the two defconfigs are the same, leave the existing one in place
+				cmp "${WORKDIR}/defconfig" "${S}/arch/${ARCH}/configs/${KBUILD_DEFCONFIG}"
+				if [ $? -ne 0 ]; then
+					bbnote "defconfig detected in WORKDIR. ${KBUILD_DEFCONFIG} skipped"
+				else
+					cp -f ${S}/arch/${ARCH}/configs/${KBUILD_DEFCONFIG} ${WORKDIR}/defconfig
+					sccs="${WORKDIR}/defconfig"
+				fi
+			fi
+		else
+			bbfatal "A KBUILD_DECONFIG '${KBUILD_DEFCONFIG}' was specified, but not present in the source tree"
+		fi
+	fi
+
 	# if we have a defined/set meta branch we should not be generating
 	# any meta data. The passed branch has what we need.
 	if [ -n "${KMETA}" ]; then
@@ -86,11 +122,10 @@ do_kernel_metadata() {
 		bbfatal "Could not create ${machine_branch}"
 	fi
 
-	sccs="${@" ".join(find_sccs(d))}"
+	sccs="$sccs ${@" ".join(find_sccs(d))}"
 	patches="${@" ".join(find_patches(d))}"
 	feat_dirs="${@" ".join(find_kernel_feature_dirs(d))}"
 
-	set +e
 	# add any explicitly referenced features onto the end of the feature
 	# list that is passed to the kernel build scripts.
 	if [ -n "${KERNEL_FEATURES}" ]; then
Signature · 1 line
2.1.0
#2 lore raw

PATCH 2/5 linux-yocto/3.19: configuration updates and stable import

In reply to Bruce Ashfield

Updating the 3.19 SRCREVs to pick up the korg 3.19.2 release, as well as the following meta data changes:

ed82e1ac3196 features: soc: fix typo in baytrail.cfg 76bc151242d7 tiny.cfg: Enable BINFMT_SCRIPT

---
 meta/recipes-kernel/linux/linux-yocto-tiny_3.19.bb |  6 +++---
 meta/recipes-kernel/linux/linux-yocto_3.19.bb      | 20 ++++++++++----------
 2 files changed, 13 insertions(+), 13 deletions(-)
meta/recipes-kernel/linux/linux-yocto-tiny_3.19.bb +3 -3
index 98ffc5a3cc37..d5a07dd68918 100644
@@ -4,13 +4,13 @@ KCONFIG_MODE = "--allnoconfig"
 
 require recipes-kernel/linux/linux-yocto.inc
 
-LINUX_VERSION ?= "3.19.1"
+LINUX_VERSION ?= "3.19.2"
 
 KMETA = "meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
-SRCREV_machine ?= "8c38c1015bbb5fc121018f67ed45a7eb2f357cfe"
-SRCREV_meta ?= "e3303ca4bd7d7a5a3d9a9a9a9467c4c70db4258d"
+SRCREV_machine ?= "31b35da6a5c8a2b162f6c33202e9b64dd13757d5"
+SRCREV_meta ?= "8fc194deced3f83e78b0671c6ff8b45bdb7f80e7"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
meta/recipes-kernel/linux/linux-yocto_3.19.bb +10 -10
index 31321c55e984..ac1856abcecc 100644
@@ -11,19 +11,19 @@ KBRANCH_qemux86  ?= "standard/common-pc"
 KBRANCH_qemux86-64 ?= "standard/common-pc-64/base"
 KBRANCH_qemumips64 ?= "standard/mti-malta64"
 
-SRCREV_machine_qemuarm ?= "a40304a6dfdad6618420854121ee91cf09481bd4"
-SRCREV_machine_qemuarm64 ?= "8c38c1015bbb5fc121018f67ed45a7eb2f357cfe"
-SRCREV_machine_qemumips ?= "6f1c5213591d7a35efc542a0971c70dcd16ea00e"
-SRCREV_machine_qemuppc ?= "6b9a1cb9e10e76d8a3102c046656c93651fde9ab"
-SRCREV_machine_qemux86 ?= "8c38c1015bbb5fc121018f67ed45a7eb2f357cfe"
-SRCREV_machine_qemux86-64 ?= "8c38c1015bbb5fc121018f67ed45a7eb2f357cfe"
-SRCREV_machine_qemumips64 ?= "723d6e1eb8dfa06f374d925d2c36e22feb1a2c86"
-SRCREV_machine ?= "8c38c1015bbb5fc121018f67ed45a7eb2f357cfe"
-SRCREV_meta ?= "e3303ca4bd7d7a5a3d9a9a9a9467c4c70db4258d"
+SRCREV_machine_qemuarm ?= "473e2f3788730c51e82714a9785325b6308f6762"
+SRCREV_machine_qemuarm64 ?= "31b35da6a5c8a2b162f6c33202e9b64dd13757d5"
+SRCREV_machine_qemumips ?= "d43f1cbf282d020f7aa31d68a54b2876d2c0e81b"
+SRCREV_machine_qemuppc ?= "35de413056b86191963ffe686913da31b978a9b3"
+SRCREV_machine_qemux86 ?= "31b35da6a5c8a2b162f6c33202e9b64dd13757d5"
+SRCREV_machine_qemux86-64 ?= "31b35da6a5c8a2b162f6c33202e9b64dd13757d5"
+SRCREV_machine_qemumips64 ?= "d35649ef8cbb0a0404be5c721377b138866181ad"
+SRCREV_machine ?= "31b35da6a5c8a2b162f6c33202e9b64dd13757d5"
+SRCREV_meta ?= "8fc194deced3f83e78b0671c6ff8b45bdb7f80e7"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.19.git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta"
 
-LINUX_VERSION ?= "3.19.1"
+LINUX_VERSION ?= "3.19.2"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
Signature · 1 line
2.1.0
#3 lore raw

PATCH 3/5 linux-yocto/3.14: integrate korg stable and meta data changes

In reply to Bruce Ashfield

Updating the 3.14 SRCREVs to import the v3.14.36 korg stable changes and configuration changes to the meta branch.

---
 meta/recipes-kernel/linux/linux-yocto-rt_3.14.bb   |  8 ++++----
 meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb |  6 +++---
 meta/recipes-kernel/linux/linux-yocto_3.14.bb      | 20 ++++++++++----------
 3 files changed, 17 insertions(+), 17 deletions(-)
meta/recipes-kernel/linux/linux-yocto-rt_3.14.bb +4 -4
index aff670271cb8..4b602b1b03f6 100644
@@ -3,13 +3,13 @@ KBRANCH_qemuppc ?= "standard/preempt-rt/qemuppc"
 
 require recipes-kernel/linux/linux-yocto.inc
 
-SRCREV_machine ?= "eb2c9c93de9b806f2a52c26bba229089a7a71385"
-SRCREV_machine_qemuppc ?= "bd470d1c8337323b0f7d1529df70a1c68108df0b"
-SRCREV_meta ?= "6eddbf47875ef48ddc5864957a7b63363100782b"
+SRCREV_machine ?= "3fb54cf8f4c3254f628e6c4720fe3c731a9de0b2"
+SRCREV_machine_qemuppc ?= "ab935c000435b6f5af42543f8e2300e473995d5a"
+SRCREV_meta ?= "162dfe3bb092c1a792e5ed224fe09672e9814b24"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.14.git;bareclone=1;branch=${KBRANCH},meta;name=machine,meta"
 
-LINUX_VERSION ?= "3.14.29"
+LINUX_VERSION ?= "3.14.36"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb +3 -3
index f6b95a218ad7..afcc4dd6206c 100644
@@ -4,13 +4,13 @@ KCONFIG_MODE = "--allnoconfig"
 
 require recipes-kernel/linux/linux-yocto.inc
 
-LINUX_VERSION ?= "3.14.29"
+LINUX_VERSION ?= "3.14.36"
 
 KMETA = "meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
-SRCREV_machine ?= "3bab81113682d3a5ffc8ea60cf770beed4831492"
-SRCREV_meta ?= "6eddbf47875ef48ddc5864957a7b63363100782b"
+SRCREV_machine ?= "4434aa71ff7043c570f9eae493df1ccadbda9b85"
+SRCREV_meta ?= "162dfe3bb092c1a792e5ed224fe09672e9814b24"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
meta/recipes-kernel/linux/linux-yocto_3.14.bb +10 -10
index 0d0d8b2ee22a..b71aea2b18e9 100644
@@ -11,19 +11,19 @@ KBRANCH_qemux86  ?= "standard/common-pc/base"
 KBRANCH_qemux86-64 ?= "standard/common-pc-64/base"
 KBRANCH_qemumips64 ?= "standard/mti-malta64"
 
-SRCREV_machine_qemuarm ?= "38d0249598bef8263f1f1e280badf6b92a0bc668"
-SRCREV_machine_qemuarm64 ?= "3bab81113682d3a5ffc8ea60cf770beed4831492"
-SRCREV_machine_qemumips ?= "d2138247c6f1ba8f082f7c2b0d4a6a4efb0cf908"
-SRCREV_machine_qemuppc ?= "2ec2927314d58a012403cbaccdf0a8a1f5c5d666"
-SRCREV_machine_qemux86 ?= "9ed9a63eeafbcbee0e378e304a1029bb14d45697"
-SRCREV_machine_qemux86-64 ?= "3bab81113682d3a5ffc8ea60cf770beed4831492"
-SRCREV_machine_qemumips64 ?= "afdaa94d540bf671f4d4d198ec6b891df22fb323"
-SRCREV_machine ?= "3bab81113682d3a5ffc8ea60cf770beed4831492"
-SRCREV_meta ?= "6eddbf47875ef48ddc5864957a7b63363100782b"
+SRCREV_machine_qemuarm ?= "d1cea997ae512ee325600a247d75027e65655e0a"
+SRCREV_machine_qemuarm64 ?= "4434aa71ff7043c570f9eae493df1ccadbda9b85"
+SRCREV_machine_qemumips ?= "c37155f99472e7dc9f94b3bda72c73a3f718fdbf"
+SRCREV_machine_qemuppc ?= "521b9fd001dc25a446d39f349cdfb7f9f5697d05"
+SRCREV_machine_qemux86 ?= "f7cbba6012312f5bf9b7279bafa8bb09d18b547d"
+SRCREV_machine_qemux86-64 ?= "4434aa71ff7043c570f9eae493df1ccadbda9b85"
+SRCREV_machine_qemumips64 ?= "a777f11a26f075b71becb47b5133252c5d8fafff"
+SRCREV_machine ?= "4434aa71ff7043c570f9eae493df1ccadbda9b85"
+SRCREV_meta ?= "162dfe3bb092c1a792e5ed224fe09672e9814b24"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.14.git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta"
 
-LINUX_VERSION ?= "3.14.29"
+LINUX_VERSION ?= "3.14.36"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
Signature · 1 line
2.1.0
#4 lore raw

PATCH 4/5 linux-yocto/3.19: fixes for Intel core warnings

In reply to Bruce Ashfield

Updating the 3.19 meta branch to include the following configuration change to deal with kernel configuration audit warnings:

9e70b482d377 romley: remove common video and media config items 8a4e096759ad intel-common: remove eg20t from common config c2f5ab15620c drm-cdvpvr: Add STAGING_MEDIA
ac4693c1db39 media: Prefer modules(m) to yes(y) and update for 3.19 Kernel

---
 meta/recipes-kernel/linux/linux-yocto-tiny_3.19.bb | 2 +-
 meta/recipes-kernel/linux/linux-yocto_3.19.bb      | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)
meta/recipes-kernel/linux/linux-yocto-tiny_3.19.bb +1 -1
index d5a07dd68918..0631c5e55156 100644
@@ -10,7 +10,7 @@ KMETA = "meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
 SRCREV_machine ?= "31b35da6a5c8a2b162f6c33202e9b64dd13757d5"
-SRCREV_meta ?= "8fc194deced3f83e78b0671c6ff8b45bdb7f80e7"
+SRCREV_meta ?= "9e70b482d3773abf92c9c5850e134cbca1d5651f"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
meta/recipes-kernel/linux/linux-yocto_3.19.bb +1 -1
index ac1856abcecc..9b19eb299b16 100644
@@ -19,7 +19,7 @@ SRCREV_machine_qemux86 ?= "31b35da6a5c8a2b162f6c33202e9b64dd13757d5"
 SRCREV_machine_qemux86-64 ?= "31b35da6a5c8a2b162f6c33202e9b64dd13757d5"
 SRCREV_machine_qemumips64 ?= "d35649ef8cbb0a0404be5c721377b138866181ad"
 SRCREV_machine ?= "31b35da6a5c8a2b162f6c33202e9b64dd13757d5"
-SRCREV_meta ?= "8fc194deced3f83e78b0671c6ff8b45bdb7f80e7"
+SRCREV_meta ?= "9e70b482d3773abf92c9c5850e134cbca1d5651f"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.19.git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta"
 
Signature · 1 line
2.1.0
#6 lore raw

PATCH 5/5 skeleton: clarify linux-yocto-custom workflow

In reply to Bruce Ashfield

It was pointed out that the kernel development documentation recommends making a copy of linux-yocto-custom, while the comments in the recipe itself suggest a bbappend.

To keep things consistent between these two sources, we update the comment in the recipe itself to also recommend a copy (and rename).

[YOCTO: #6925]

---
 meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)
meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb +2 -4
index b1a0784c1b7d..05463c026304 100644
@@ -4,11 +4,9 @@
 #   kernel classes to apply a subset of yocto kernel management to git
 #   managed kernel repositories.
 #
-#   To use linux-yocto-custom in your layer, create a
-#   linux-yocto-custom.bbappend file containing at least the following
-#   lines:
+#   To use linux-yocto-custom in your layer, copy this recipe (optionally
+#   rename it as well) and modify it appropriately for your machine. i.e.:
 #
-#     FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
 #     COMPATIBLE_MACHINE_yourmachine = "yourmachine"
 #
 #   You must also provide a Linux kernel configuration. The most direct
Signature · 1 line
2.1.0
#7 lore raw
In reply to Bruce Ashfield
Quoted 9 lines · Bruce Ashfield

Hi all,

Here is the latest linux-yocto consolidated pull request. It is a mix of kernel version -stable imports (CVEs and fixes), kernel configuration changes, a documentation update and kernel configuration enhancement.

The -stable updates are routine, and I build/boot tested them here (with my fixup commits being evidence). These are ready for a round of autobuilder/soak testing.

Something in here broke lttng-modules causing cascades of failures on the autobuilder so I've updated it to the latest code on the 2.6 stable branch and am retesting.

Cheers,

Richard

#8 lore raw
Quoted 7 lines · Richard Purdie
Quoted 6 lines · Bruce Ashfield

Hi all,

Here is the latest linux-yocto consolidated pull request. It is a mix of kernel version -stable imports (CVEs and fixes), kernel configuration changes, a documentation update and kernel configuration enhancement.

Quoted 7 lines
Quoted 3 lines

The -stable updates are routine, and I build/boot tested them here (with my fixup commits being evidence). These are ready for a round of autobuilder/soak testing.

Something in here broke lttng-modules causing cascades of failures on the autobuilder so I've updated it to the latest code on the 2.6 stable branch and am retesting.

Gah. I built and booted here, but can't think of any reason why that didn't trigger and fail here.

I've started my own build as well, with a completely clean starting point.

Bruce

Quoted 10 lines

Cheers,

Richard

--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Signature · 2 lines
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
#9 lore raw
Quoted 13 lines · Bruce Ashfield
Quoted 11 lines · Richard Purdie
Quoted 9 lines · Bruce Ashfield

Hi all,

Here is the latest linux-yocto consolidated pull request. It is a mix of kernel version -stable imports (CVEs and fixes), kernel configuration changes, a documentation update and kernel configuration enhancement.

The -stable updates are routine, and I build/boot tested them here (with my fixup commits being evidence). These are ready for a round of autobuilder/soak testing.

Quoted 8 lines
Quoted 3 lines

Something in here broke lttng-modules causing cascades of failures on the autobuilder so I've updated it to the latest code on the 2.6 stable branch and am retesting.

Gah. I built and booted here, but can't think of any reason why that didn't trigger and fail here.

I've started my own build as well, with a completely clean starting point.

and sure enough, it blows up on my clean build.

If your update doesn't resolve this, ping me and I'll take care of the fix.

Bruce

Quoted 19 lines

Bruce

Quoted 10 lines

Cheers,

Richard

--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

--
"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"

Signature · 2 lines
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
#10 lore raw
Quoted 19 lines · Bruce Ashfield
Quoted 17 lines · Bruce Ashfield
Quoted 14 lines · Richard Purdie
Quoted 9 lines · Bruce Ashfield

Hi all,

Here is the latest linux-yocto consolidated pull request. It is a mix of kernel version -stable imports (CVEs and fixes), kernel configuration changes, a documentation update and kernel configuration enhancement.

The -stable updates are routine, and I build/boot tested them here (with my fixup commits being evidence). These are ready for a round of autobuilder/soak testing.

Something in here broke lttng-modules causing cascades of failures on the autobuilder so I've updated it to the latest code on the 2.6 stable branch and am retesting.

Quoted 8 lines
Quoted 4 lines

Gah. I built and booted here, but can't think of any reason why that didn't trigger and fail here.

I've started my own build as well, with a completely clean starting point.

and sure enough, it blows up on my clean build.

If your update doesn't resolve this, ping me and I'll take care of the fix.

It seemed to work, we've merged everything to master and branched for the release. Release build now in progress so we'll see... :)

Cheers,

Richard

#5 lore raw

Re: [PATCH 4/5] linux-yocto/3.19: fixes for Intel core warnings

In reply to Bruce Ashfield
Quoted 7 lines · Bruce Ashfield

Updating the 3.19 meta branch to include the following configuration change to deal with kernel configuration audit warnings:

9e70b482d377 romley: remove common video and media config items 8a4e096759ad intel-common: remove eg20t from common config c2f5ab15620c drm-cdvpvr: Add STAGING_MEDIA
ac4693c1db39 media: Prefer modules(m) to yes(y) and update for 3.19 Kernel

I don't know if it's caused by this one or some other linux-yocto change, but recent qemux86 builds are failing with:

ERROR: Logfile of failure stored in: /OE/build/owpb/webos-ports/tmp-glibc/work/qemux86-webos-linux/linux-yocto/3.19.2+gitAUTOINC+9e70b482d3_31b35da6a5-r0/temp/log.do_compile_kernelmodules.22804 Log data follows:

| DEBUG: Executing shell function do_compile_kernelmodules
| NOTE: make -j 9 modules CC=i586-webos-linux-gcc  LD=i586-webos-linux-ld.bfd
|   CHK     include/config/kernel.release
|   GEN     ./Makefile
|   CHK     include/generated/uapi/linux/version.h
|   Using /OE/build/owpb/webos-ports/tmp-glibc/work-shared/qemux86/kernel-source as source for kernel
|   CHK     include/generated/utsrelease.h
|   CALL    /OE/build/owpb/webos-ports/tmp-glibc/work-shared/qemux86/kernel-source/scripts/checksyscalls.sh
| net/sctp/.transport.o.cmd:5: *** unterminated call to function 'wildcard': missing ')'.  Stop.
| /OE/build/owpb/webos-ports/tmp-glibc/work-shared/qemux86/kernel-source/scripts/Makefile.build:402: recipe for target 'net/sctp' failed
| make[3]: *** [net/sctp] Error 2
| /OE/build/owpb/webos-ports/tmp-glibc/work-shared/qemux86/kernel-source/Makefile:939: recipe for target 'net' failed
| make[2]: *** [net] Error 2
| make[2]: *** Waiting for unfinished jobs....
| Makefile:145: recipe for target 'sub-make' failed
| make[1]: *** [sub-make] Error 2
| Makefile:24: recipe for target '__sub-make' failed
| make: *** [__sub-make] Error 2

Any idea what went wrong?

tmp-glibc/work/qemux86-webos-linux/linux-yocto/3.19.2+gitAUTOINC+9e70b482d3_31b35da6a5-r0/linux-qemux86-standard-build/net/sctp/.transport.o.cmd is attached

Quoted 41 lines
---
 meta/recipes-kernel/linux/linux-yocto-tiny_3.19.bb | 2 +-
 meta/recipes-kernel/linux/linux-yocto_3.19.bb      | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)
meta/recipes-kernel/linux/linux-yocto-tiny_3.19.bb +1 -1
index d5a07dd68918..0631c5e55156 100644
@@ -10,7 +10,7 @@ KMETA = "meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
 SRCREV_machine ?= "31b35da6a5c8a2b162f6c33202e9b64dd13757d5"
-SRCREV_meta ?= "8fc194deced3f83e78b0671c6ff8b45bdb7f80e7"
+SRCREV_meta ?= "9e70b482d3773abf92c9c5850e134cbca1d5651f"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
meta/recipes-kernel/linux/linux-yocto_3.19.bb +1 -1
index ac1856abcecc..9b19eb299b16 100644
@@ -19,7 +19,7 @@ SRCREV_machine_qemux86 ?= "31b35da6a5c8a2b162f6c33202e9b64dd13757d5"
 SRCREV_machine_qemux86-64 ?= "31b35da6a5c8a2b162f6c33202e9b64dd13757d5"
 SRCREV_machine_qemumips64 ?= "d35649ef8cbb0a0404be5c721377b138866181ad"
 SRCREV_machine ?= "31b35da6a5c8a2b162f6c33202e9b64dd13757d5"
-SRCREV_meta ?= "8fc194deced3f83e78b0671c6ff8b45bdb7f80e7"
+SRCREV_meta ?= "9e70b482d3773abf92c9c5850e134cbca1d5651f"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.19.git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta"
 
Signature · 7 lines
2.1.0

-- 
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Signature · 1 line
Martin 'JaMa' Jansa     jabber: [email protected]