* [PATCH 1/5] linux-libc-headers: update to 3.19
2015-02-20 18:37 [PATCH 0/5] linux-yocto: consolidated pull request (3.19 + config visibility) Bruce Ashfield
@ 2015-02-20 18:37 ` Bruce Ashfield
2015-02-20 18:38 ` [PATCH 2/5] linux-yocto: make kernel configuration audit user visible Bruce Ashfield
` (3 subsequent siblings)
4 siblings, 0 replies; 8+ messages in thread
From: Bruce Ashfield @ 2015-02-20 18:37 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
Updating the libc-headers now that the kernel has released.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
---
meta/conf/distro/include/tcmode-default.inc | 2 +-
| 7 -------
| 7 +++++++
3 files changed, 8 insertions(+), 8 deletions(-)
delete mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.17.7.bb
create mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.19.bb
diff --git a/meta/conf/distro/include/tcmode-default.inc b/meta/conf/distro/include/tcmode-default.inc
index 9e25bf0225de..6b602d2f9412 100644
--- a/meta/conf/distro/include/tcmode-default.inc
+++ b/meta/conf/distro/include/tcmode-default.inc
@@ -27,7 +27,7 @@ SDKGCCVERSION ?= "${GCCVERSION}"
BINUVERSION ?= "2.24"
GLIBCVERSION ?= "2.21"
UCLIBCVERSION ?= "0.9.33+git%"
-LINUXLIBCVERSION ?= "3.17.7"
+LINUXLIBCVERSION ?= "3.19"
PREFERRED_VERSION_gcc ?= "${GCCVERSION}"
PREFERRED_VERSION_gcc-cross-${TARGET_ARCH} ?= "${GCCVERSION}"
diff --git a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.17.7.bb b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.17.7.bb
deleted file mode 100644
index 73325973326f..000000000000
--- a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.17.7.bb
+++ /dev/null
@@ -1,7 +0,0 @@
-KORG_ARCHIVE_COMPRESSION = "xz"
-
-require linux-libc-headers.inc
-
-SRC_URI[md5sum] = "59cc7d0a236b08de743d6d9421f0f2c6"
-SRC_URI[sha256sum] = "a3c8e6aee912bfd2e69abf9df5a06058434a8771bcaa1784b5980bf1b5298e1c"
-
--git a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.19.bb b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.19.bb
new file mode 100644
index 000000000000..078df4512ba1
--- /dev/null
+++ b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.19.bb
@@ -0,0 +1,7 @@
+KORG_ARCHIVE_COMPRESSION = "xz"
+
+require linux-libc-headers.inc
+
+SRC_URI[md5sum] = "d3fc8316d4d4d04b65cbc2d70799e763"
+SRC_URI[sha256sum] = "be42511fe5321012bb4a2009167ce56a9e5fe362b4af43e8c371b3666859806c"
+
--
2.1.0
^ permalink raw reply related [flat|nested] 8+ messages in thread* [PATCH 2/5] linux-yocto: make kernel configuration audit user visible
2015-02-20 18:37 [PATCH 0/5] linux-yocto: consolidated pull request (3.19 + config visibility) Bruce Ashfield
2015-02-20 18:37 ` [PATCH 1/5] linux-libc-headers: update to 3.19 Bruce Ashfield
@ 2015-02-20 18:38 ` Bruce Ashfield
2015-02-20 18:38 ` [PATCH 3/5] linux-yocto: remove 3.10 and 3.17 recipes Bruce Ashfield
` (2 subsequent siblings)
4 siblings, 0 replies; 8+ messages in thread
From: Bruce Ashfield @ 2015-02-20 18:38 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
After a linux-yocto style kernel is configured, a kernel configuration
audit is executed to detect common errors or issues with the config.
This output used to be visible, but was made less obvious to not alarm
users unnecessarily (since some configuration issues are acceptable).
There are some classes of configuration issue that are worth being
visible, and that is specified configuration values that do not make the
final .config. These dropped options can result in any number of runtime
failures, so flagging them at build time makes sense.
The visibility of auditing is controlled by KCONF_AUDIT_LEVEL:
0: no reporting
1: report options that are specified, but not in the final config
2: report options that are not hardware related, but set by a BSP
The default level is 1, with level 2 and above being for BSP development
only.
If these conditions are detected, warnings will be generated as follows:
WARNING: [kernel config]: specified values did not make it into the
kernel's final configuration:
Value requested for CONFIG_SND_PCSP not in final ".config"
Requested value: "CONFIG_SND_PCSP=y"
Actual value set: ""
or
WARNING: [kernel config]: BSP specified non-hw configuration:
CONFIG_BLOCK
CONFIG_CFG80211_WEXT
CONFIG_CORDIC
CONFIG_CRC8
CONFIG_EFIVAR_FS
CONFIG_EFI_PARTITION
CONFIG_NET
CONFIG_NETDEVICES
CONFIG_PARTITION_ADVANCED
CONFIG_WEXT_CORE
CONFIG_WEXT_PROC
CONFIG_WIRELESS
At this point thse are only a warnings, since there needs to be time for
layers and configuration fragments to be validated against this new
check.
[YOCTO: #6943]
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
---
meta/classes/kernel-yocto.bbclass | 24 +++++++++++++++-------
.../kern-tools/kern-tools-native_git.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto.inc | 6 ++++++
3 files changed, 24 insertions(+), 8 deletions(-)
diff --git a/meta/classes/kernel-yocto.bbclass b/meta/classes/kernel-yocto.bbclass
index 223825e546a4..0cbbb5f2d22f 100644
--- a/meta/classes/kernel-yocto.bbclass
+++ b/meta/classes/kernel-yocto.bbclass
@@ -253,8 +253,6 @@ addtask kernel_configme after do_patch
python do_kernel_configcheck() {
import re, string, sys
- bb.plain("NOTE: validating kernel config, see log.do_kernel_configcheck for details")
-
# if KMETA isn't set globally by a recipe using this routine, we need to
# set the default to 'meta'. Otherwise, kconf_check is not passed a valid
# meta-series for processing
@@ -266,11 +264,23 @@ python do_kernel_configcheck() {
cmd = d.expand("cd ${S}; kconf_check -config- %s/meta-series ${S} ${B}" % kmeta)
ret, result = oe.utils.getstatusoutput("%s%s" % (pathprefix, cmd))
- config_check_visibility = d.getVar( "KCONF_AUDIT_LEVEL", True ) or 1
- if config_check_visibility == 1:
- bb.debug( 1, "%s" % result )
- else:
- bb.note( "%s" % result )
+ config_check_visibility = int(d.getVar( "KCONF_AUDIT_LEVEL", True ) or 0)
+
+ # if config check visibility is non-zero, report dropped configuration values
+ mismatch_file = "${S}/" + kmeta + "/" + "mismatch.cfg"
+ if os.path.exists(mismatch_file):
+ if config_check_visibility:
+ with open (mismatch_file, "r") as myfile:
+ results = myfile.read()
+ bb.warn( "[kernel config]: specified values did not make it into the kernel's final configuration:\n\n%s" % results)
+
+ # if config check visibility is level 2 or higher, report non-hardware options
+ nonhw_file = "${S}/" + kmeta + "/" + "nonhw_report.cfg"
+ if os.path.exists(nonhw_file):
+ if config_check_visibility > 1:
+ with open (nonhw_file, "r") as myfile:
+ results = myfile.read()
+ bb.warn( "[kernel config]: BSP specified non-hw configuration:\n\n%s" % results)
}
# Ensure that the branches (BSP and meta) are on the locations specified by
diff --git a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
index 32783986487f..80d26f98749d 100644
--- a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
+++ b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
@@ -4,7 +4,7 @@ LIC_FILES_CHKSUM = "file://git/tools/kgit;beginline=5;endline=9;md5=d8d1d729a70c
DEPENDS = "git-native"
-SRCREV = "daab4442c22c09a98a823c32d7219316b6832182"
+SRCREV = "cab17f884998b43692244a863dea6f505c7f67af"
PR = "r12"
PV = "0.2+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto.inc b/meta/recipes-kernel/linux/linux-yocto.inc
index 7416af99f57f..79b3f256f4bc 100644
--- a/meta/recipes-kernel/linux/linux-yocto.inc
+++ b/meta/recipes-kernel/linux/linux-yocto.inc
@@ -23,6 +23,12 @@ KBRANCH ?= "master"
KMACHINE ?= "${MACHINE}"
SRCREV_FORMAT ?= "meta_machine"
+# LEVELS:
+# 0: no reporting
+# 1: report options that are specified, but not in the final config
+# 2: report options that are not hardware related, but set by a BSP
+KCONF_AUDIT_LEVEL ?= "1"
+
LINUX_VERSION_EXTENSION ?= "-yocto-${LINUX_KERNEL_TYPE}"
do_patch[depends] = "kern-tools-native:do_populate_sysroot"
--
2.1.0
^ permalink raw reply related [flat|nested] 8+ messages in thread* [PATCH 3/5] linux-yocto: remove 3.10 and 3.17 recipes
2015-02-20 18:37 [PATCH 0/5] linux-yocto: consolidated pull request (3.19 + config visibility) Bruce Ashfield
2015-02-20 18:37 ` [PATCH 1/5] linux-libc-headers: update to 3.19 Bruce Ashfield
2015-02-20 18:38 ` [PATCH 2/5] linux-yocto: make kernel configuration audit user visible Bruce Ashfield
@ 2015-02-20 18:38 ` Bruce Ashfield
2015-02-20 18:38 ` [PATCH 4/5] linux-yocto: introduce 3.19 versioned recipes Bruce Ashfield
2015-02-20 18:38 ` [PATCH 5/5] linux-yocto: warn when a generated BSP description is used Bruce Ashfield
4 siblings, 0 replies; 8+ messages in thread
From: Bruce Ashfield @ 2015-02-20 18:38 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
In accordance with the kernel release criteria we support the latest
mainline kernel + the last LSTI kernel + a development kernel.
3.19 will be introduced as the latest mainline, and 3.14 is the released
LTSI kernel, which means that we remove the 3.10 and 3.17 variants.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
---
meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 27 ---------------
meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 22 ------------
meta/recipes-kernel/linux/linux-yocto-tiny_3.17.bb | 21 ------------
meta/recipes-kernel/linux/linux-yocto_3.10.bb | 37 --------------------
meta/recipes-kernel/linux/linux-yocto_3.17.bb | 39 ----------------------
5 files changed, 146 deletions(-)
delete mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.17.bb
delete mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
delete mode 100644 meta/recipes-kernel/linux/linux-yocto_3.17.bb
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb b/meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
deleted file mode 100644
index 36a00cf03b1a..000000000000
--- a/meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
+++ /dev/null
@@ -1,27 +0,0 @@
-KBRANCH ?= "standard/preempt-rt/base"
-KBRANCH_qemuppc ?= "standard/preempt-rt/qemuppc"
-
-require recipes-kernel/linux/linux-yocto.inc
-
-SRCREV_machine ?= "c75818e2932c3c0444ebebfcc0608fecf2440b92"
-SRCREV_machine_qemuppc ?= "fc7abf900967db5dea8a8f8648b8a0de7032f8d7"
-SRCREV_meta ?= "d5456dd830cad14bd844753b751b83744ced3793"
-
-SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.10.git;bareclone=1;branch=${KBRANCH},meta;name=machine,meta"
-
-LINUX_VERSION ?= "3.10.65"
-
-PV = "${LINUX_VERSION}+git${SRCPV}"
-
-KMETA = "meta"
-
-LINUX_KERNEL_TYPE = "preempt-rt"
-
-COMPATIBLE_MACHINE = "(qemux86|qemux86-64|qemuarm|qemuppc|qemumips)"
-
-# 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)}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
deleted file mode 100644
index 3248c4414b42..000000000000
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
+++ /dev/null
@@ -1,22 +0,0 @@
-KBRANCH ?= "standard/tiny/base"
-
-require recipes-kernel/linux/linux-yocto.inc
-
-LINUX_KERNEL_TYPE = "tiny"
-KCONFIG_MODE = "--allnoconfig"
-
-LINUX_VERSION ?= "3.10.65"
-
-KMETA = "meta"
-
-SRCREV_machine ?= "a2f2be49cd60b8d022fa47daae0a8293c3066b78"
-SRCREV_meta ?= "d5456dd830cad14bd844753b751b83744ced3793"
-
-PV = "${LINUX_VERSION}+git${SRCPV}"
-
-SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.10.git;bareclone=1;branch=${KBRANCH},meta;name=machine,meta"
-
-COMPATIBLE_MACHINE = "(qemux86)"
-
-# Functionality flags
-KERNEL_FEATURES = ""
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_3.17.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_3.17.bb
deleted file mode 100644
index 853f8d0289f4..000000000000
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_3.17.bb
+++ /dev/null
@@ -1,21 +0,0 @@
-KBRANCH ?= "standard/tiny/base"
-LINUX_KERNEL_TYPE = "tiny"
-KCONFIG_MODE = "--allnoconfig"
-
-require recipes-kernel/linux/linux-yocto.inc
-
-LINUX_VERSION ?= "3.17.8"
-
-KMETA = "meta"
-
-SRCREV_machine ?= "0409b1fbed221e61212e17b7637fa54f908d83f6"
-SRCREV_meta ?= "f24c2bf9c298595d00a9d8600841f2b0206e1fba"
-
-PV = "${LINUX_VERSION}+git${SRCPV}"
-
-SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.17.git;bareclone=1;branch=${KBRANCH},meta;name=machine,meta"
-
-COMPATIBLE_MACHINE = "(qemux86)"
-
-# Functionality flags
-KERNEL_FEATURES = ""
diff --git a/meta/recipes-kernel/linux/linux-yocto_3.10.bb b/meta/recipes-kernel/linux/linux-yocto_3.10.bb
deleted file mode 100644
index d3cb81662e98..000000000000
--- a/meta/recipes-kernel/linux/linux-yocto_3.10.bb
+++ /dev/null
@@ -1,37 +0,0 @@
-KBRANCH ?= "standard/base"
-
-require recipes-kernel/linux/linux-yocto.inc
-
-# 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 ?= "7a8c197b86281f9a445e23378fdfeeb4da0c48e9"
-SRCREV_machine_qemumips ?= "926e71942842a9d1a9f64aae0458b2d777d3bca9"
-SRCREV_machine_qemuppc ?= "65648fce58a5e095cfe2bf394bc0f6200efb281c"
-SRCREV_machine_qemux86 ?= "a2f2be49cd60b8d022fa47daae0a8293c3066b78"
-SRCREV_machine_qemux86-64 ?= "a2f2be49cd60b8d022fa47daae0a8293c3066b78"
-SRCREV_machine_qemumips64 ?= "06d173388a171e7371816d74567fdec994925aa4"
-SRCREV_machine ?= "a2f2be49cd60b8d022fa47daae0a8293c3066b78"
-SRCREV_meta ?= "d5456dd830cad14bd844753b751b83744ced3793"
-
-SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.10.git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta"
-
-LINUX_VERSION ?= "3.10.65"
-
-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)}"
diff --git a/meta/recipes-kernel/linux/linux-yocto_3.17.bb b/meta/recipes-kernel/linux/linux-yocto_3.17.bb
deleted file mode 100644
index f57d9c200256..000000000000
--- a/meta/recipes-kernel/linux/linux-yocto_3.17.bb
+++ /dev/null
@@ -1,39 +0,0 @@
-KBRANCH ?= "standard/base"
-
-require recipes-kernel/linux/linux-yocto.inc
-
-# board specific branches
-KBRANCH_qemuarm ?= "standard/arm-versatile-926ejs"
-KBRANCH_qemuarm64 ?= "standard/qemuarm64"
-KBRANCH_qemumips ?= "standard/mti-malta32"
-KBRANCH_qemuppc ?= "standard/qemuppc"
-KBRANCH_qemux86 ?= "standard/common-pc"
-KBRANCH_qemux86-64 ?= "standard/common-pc-64/base"
-KBRANCH_qemumips64 ?= "standard/mti-malta64"
-
-SRCREV_machine_qemuarm ?= "12991e8ac40c51ef3e337f17f12aa59c6500fc7f"
-SRCREV_machine_qemuarm64 ?= "0409b1fbed221e61212e17b7637fa54f908d83f6"
-SRCREV_machine_qemumips ?= "1f4735ed314defc95ab9929258ad12844cc2c676"
-SRCREV_machine_qemuppc ?= "3231dececf867215ecab7c7f9ec3a7a7640a3f32"
-SRCREV_machine_qemux86 ?= "0409b1fbed221e61212e17b7637fa54f908d83f6"
-SRCREV_machine_qemux86-64 ?= "0409b1fbed221e61212e17b7637fa54f908d83f6"
-SRCREV_machine_qemumips64 ?= "7005c584078109dae03567e9c597a847a2bc5136"
-SRCREV_machine ?= "0409b1fbed221e61212e17b7637fa54f908d83f6"
-SRCREV_meta ?= "f24c2bf9c298595d00a9d8600841f2b0206e1fba"
-
-SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.17.git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta"
-
-LINUX_VERSION ?= "3.17.8"
-
-PV = "${LINUX_VERSION}+git${SRCPV}"
-
-KMETA = "meta"
-
-COMPATIBLE_MACHINE = "qemuarm|qemuarm64|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 cfg/paravirt_kvm.scc"
-KERNEL_FEATURES_append = " ${@bb.utils.contains("TUNE_FEATURES", "mx32", " cfg/x32.scc", "" ,d)}"
--
2.1.0
^ permalink raw reply related [flat|nested] 8+ messages in thread* [PATCH 4/5] linux-yocto: introduce 3.19 versioned recipes
2015-02-20 18:37 [PATCH 0/5] linux-yocto: consolidated pull request (3.19 + config visibility) Bruce Ashfield
` (2 preceding siblings ...)
2015-02-20 18:38 ` [PATCH 3/5] linux-yocto: remove 3.10 and 3.17 recipes Bruce Ashfield
@ 2015-02-20 18:38 ` Bruce Ashfield
2015-02-20 18:38 ` [PATCH 5/5] linux-yocto: warn when a generated BSP description is used Bruce Ashfield
4 siblings, 0 replies; 8+ messages in thread
From: Bruce Ashfield @ 2015-02-20 18:38 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
Introducing the v3.19.x recipes for the validated linux-yocto kernel.
Build, boot and sanity testing was performed on qemu for all major
architectures.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
---
meta/recipes-kernel/linux/linux-yocto-tiny_3.19.bb | 21 ++++++++++++
meta/recipes-kernel/linux/linux-yocto_3.19.bb | 39 ++++++++++++++++++++++
2 files changed, 60 insertions(+)
create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.19.bb
create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.19.bb
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_3.19.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_3.19.bb
new file mode 100644
index 000000000000..dba163e006d3
--- /dev/null
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_3.19.bb
@@ -0,0 +1,21 @@
+KBRANCH ?= "standard/tiny/base"
+LINUX_KERNEL_TYPE = "tiny"
+KCONFIG_MODE = "--allnoconfig"
+
+require recipes-kernel/linux/linux-yocto.inc
+
+LINUX_VERSION ?= "3.19"
+
+KMETA = "meta"
+
+SRCREV_machine ?= "43b9eced9ba8a57add36af07736344dcc383f711"
+SRCREV_meta ?= "8897ef68b30e7426bc1d39895e71fb155d694974"
+
+PV = "${LINUX_VERSION}+git${SRCPV}"
+
+SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.19.git;bareclone=1;branch=${KBRANCH},meta;name=machine,meta"
+
+COMPATIBLE_MACHINE = "(qemux86)"
+
+# Functionality flags
+KERNEL_FEATURES = ""
diff --git a/meta/recipes-kernel/linux/linux-yocto_3.19.bb b/meta/recipes-kernel/linux/linux-yocto_3.19.bb
new file mode 100644
index 000000000000..044ee7f524ca
--- /dev/null
+++ b/meta/recipes-kernel/linux/linux-yocto_3.19.bb
@@ -0,0 +1,39 @@
+KBRANCH ?= "standard/base"
+
+require recipes-kernel/linux/linux-yocto.inc
+
+# board specific branches
+KBRANCH_qemuarm ?= "standard/arm-versatile-926ejs"
+KBRANCH_qemuarm64 ?= "standard/qemuarm64"
+KBRANCH_qemumips ?= "standard/mti-malta32"
+KBRANCH_qemuppc ?= "standard/qemuppc"
+KBRANCH_qemux86 ?= "standard/common-pc"
+KBRANCH_qemux86-64 ?= "standard/common-pc-64/base"
+KBRANCH_qemumips64 ?= "standard/mti-malta64"
+
+SRCREV_machine_qemuarm ?= "91b64df8cdcdacb9ef8d707a0c34f55a09bf170d"
+SRCREV_machine_qemuarm64 ?= "43b9eced9ba8a57add36af07736344dcc383f711"
+SRCREV_machine_qemumips ?= "7c67469a4c77a977c46f218de7e2f4699292d28b"
+SRCREV_machine_qemuppc ?= "7dc29d4265b44ad28ea3ec950b1a86be08933ce8"
+SRCREV_machine_qemux86 ?= "43b9eced9ba8a57add36af07736344dcc383f711"
+SRCREV_machine_qemux86-64 ?= "43b9eced9ba8a57add36af07736344dcc383f711"
+SRCREV_machine_qemumips64 ?= "b7ab9d4bac55415f125c81f529dbbefb07de98ad"
+SRCREV_machine ?= "43b9eced9ba8a57add36af07736344dcc383f711"
+SRCREV_meta ?= "8897ef68b30e7426bc1d39895e71fb155d694974"
+
+SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.19.git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta"
+
+LINUX_VERSION ?= "3.19"
+
+PV = "${LINUX_VERSION}+git${SRCPV}"
+
+KMETA = "meta"
+
+COMPATIBLE_MACHINE = "qemuarm|qemuarm64|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 cfg/paravirt_kvm.scc"
+KERNEL_FEATURES_append = " ${@bb.utils.contains("TUNE_FEATURES", "mx32", " cfg/x32.scc", "" ,d)}"
--
2.1.0
^ permalink raw reply related [flat|nested] 8+ messages in thread* [PATCH 5/5] linux-yocto: warn when a generated BSP description is used
2015-02-20 18:37 [PATCH 0/5] linux-yocto: consolidated pull request (3.19 + config visibility) Bruce Ashfield
` (3 preceding siblings ...)
2015-02-20 18:38 ` [PATCH 4/5] linux-yocto: introduce 3.19 versioned recipes Bruce Ashfield
@ 2015-02-20 18:38 ` Bruce Ashfield
2015-02-26 7:21 ` Ola X Nilsson
4 siblings, 1 reply; 8+ messages in thread
From: Bruce Ashfield @ 2015-02-20 18:38 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
The meta data (in tree or out of tree) that describes a BSP, its patches
and configuration is not always available when a new/default or manually
configured machine is built.
When this happens, the tools generate a skeleton BSP and use a
architecture defconfig for the build. If this is by design, the build
is typically sane and everything works fine. If an existing BSP
description was expected, chances are that the resulting kernel will not
be correct.
To avoid surprising the user when a default/skeleton BSP is used for the
build, we can make it obvious to the user by emitting a warning like
the following:
WARNING: [kernel]: An auto generated BSP description was used, this normally indicates a misconfiguration.
Check that your machine (myqemux86-64) has an associated kernel description.
[YOCTO: #3383]
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
---
meta/classes/kernel-yocto.bbclass | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/meta/classes/kernel-yocto.bbclass b/meta/classes/kernel-yocto.bbclass
index 0cbbb5f2d22f..a5e2b180c496 100644
--- a/meta/classes/kernel-yocto.bbclass
+++ b/meta/classes/kernel-yocto.bbclass
@@ -281,6 +281,15 @@ python do_kernel_configcheck() {
with open (nonhw_file, "r") as myfile:
results = myfile.read()
bb.warn( "[kernel config]: BSP specified non-hw configuration:\n\n%s" % results)
+
+ bsp_desc = "${S}/" + kmeta + "/" + "top_tgt"
+ if os.path.exists(bsp_desc):
+ with open (bsp_desc, "r") as myfile:
+ bsp_tgt = myfile.read()
+ m = re.match("^(.*)scratch.obj(.*)$", bsp_tgt)
+ if not m is None:
+ bb.warn( "[kernel]: An auto generated BSP description was used, this normally indicates a misconfiguration.\n" +
+ "Check that your machine (%s) has an associated kernel description." % "${MACHINE}" )
}
# Ensure that the branches (BSP and meta) are on the locations specified by
--
2.1.0
^ permalink raw reply related [flat|nested] 8+ messages in thread* Re: [PATCH 5/5] linux-yocto: warn when a generated BSP description is used
2015-02-20 18:38 ` [PATCH 5/5] linux-yocto: warn when a generated BSP description is used Bruce Ashfield
@ 2015-02-26 7:21 ` Ola X Nilsson
2015-02-26 13:05 ` Bruce Ashfield
0 siblings, 1 reply; 8+ messages in thread
From: Ola X Nilsson @ 2015-02-26 7:21 UTC (permalink / raw)
To: openembedded-core@lists.openembedded.org
We use a custom yocto-style kernel recipe to build our non-yocto-style kernel.
To do this we add a defconfig file to the SRC_URI variable and then a bunch of scc files to the KERNEL_FEATURES variable.
I guess this makes our BSP description auto generated. Can we have an option to turn the warning off?
--
Ola X Nilsson
> -----Original Message-----
> From: openembedded-core-bounces@lists.openembedded.org
> [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf
> Of Bruce Ashfield
> Sent: den 20 februari 2015 19:38
> To: richard.purdie@linuxfoundation.org
> Cc: openembedded-core@lists.openembedded.org
> Subject: [OE-core] [PATCH 5/5] linux-yocto: warn when a generated BSP
> description is used
>
> The meta data (in tree or out of tree) that describes a BSP, its patches and
> configuration is not always available when a new/default or manually
> configured machine is built.
>
> When this happens, the tools generate a skeleton BSP and use a architecture
> defconfig for the build. If this is by design, the build is typically sane and
> everything works fine. If an existing BSP description was expected, chances
> are that the resulting kernel will not be correct.
>
> To avoid surprising the user when a default/skeleton BSP is used for the build,
> we can make it obvious to the user by emitting a warning like the following:
>
> WARNING: [kernel]: An auto generated BSP description was used, this
> normally indicates a misconfiguration.
> Check that your machine (myqemux86-64) has an associated kernel
> description.
>
> [YOCTO: #3383]
>
> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
> ---
> meta/classes/kernel-yocto.bbclass | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/meta/classes/kernel-yocto.bbclass b/meta/classes/kernel-
> yocto.bbclass
> index 0cbbb5f2d22f..a5e2b180c496 100644
> --- a/meta/classes/kernel-yocto.bbclass
> +++ b/meta/classes/kernel-yocto.bbclass
> @@ -281,6 +281,15 @@ python do_kernel_configcheck() {
> with open (nonhw_file, "r") as myfile:
> results = myfile.read()
> bb.warn( "[kernel config]: BSP specified non-hw
> configuration:\n\n%s" % results)
> +
> + bsp_desc = "${S}/" + kmeta + "/" + "top_tgt"
> + if os.path.exists(bsp_desc):
> + with open (bsp_desc, "r") as myfile:
> + bsp_tgt = myfile.read()
> + m = re.match("^(.*)scratch.obj(.*)$", bsp_tgt)
> + if not m is None:
> + bb.warn( "[kernel]: An auto generated BSP description was used,
> this normally indicates a misconfiguration.\n" +
> + "Check that your machine (%s) has an
> + associated kernel description." % "${MACHINE}" )
> }
>
> # Ensure that the branches (BSP and meta) are on the locations specified by
> --
> 2.1.0
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [PATCH 5/5] linux-yocto: warn when a generated BSP description is used
2015-02-26 7:21 ` Ola X Nilsson
@ 2015-02-26 13:05 ` Bruce Ashfield
0 siblings, 0 replies; 8+ messages in thread
From: Bruce Ashfield @ 2015-02-26 13:05 UTC (permalink / raw)
To: Ola X Nilsson; +Cc: openembedded-core@lists.openembedded.org
On Thu, Feb 26, 2015 at 2:21 AM, Ola X Nilsson <ola.x.nilsson@axis.com> wrote:
> We use a custom yocto-style kernel recipe to build our non-yocto-style kernel.
>
> To do this we add a defconfig file to the SRC_URI variable and then a bunch of scc files to the KERNEL_FEATURES variable.
>
> I guess this makes our BSP description auto generated. Can we have an option to turn the warning off?
At the moment, no. Ignore it for now, and I can tweak the message to detect
and skip this scenario.
File a bugzilla enhancement request, and I can take care of it.
Cheers,
Bruce
>
> --
> Ola X Nilsson
>
>
>> -----Original Message-----
>> From: openembedded-core-bounces@lists.openembedded.org
>> [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf
>> Of Bruce Ashfield
>> Sent: den 20 februari 2015 19:38
>> To: richard.purdie@linuxfoundation.org
>> Cc: openembedded-core@lists.openembedded.org
>> Subject: [OE-core] [PATCH 5/5] linux-yocto: warn when a generated BSP
>> description is used
>>
>> The meta data (in tree or out of tree) that describes a BSP, its patches and
>> configuration is not always available when a new/default or manually
>> configured machine is built.
>>
>> When this happens, the tools generate a skeleton BSP and use a architecture
>> defconfig for the build. If this is by design, the build is typically sane and
>> everything works fine. If an existing BSP description was expected, chances
>> are that the resulting kernel will not be correct.
>>
>> To avoid surprising the user when a default/skeleton BSP is used for the build,
>> we can make it obvious to the user by emitting a warning like the following:
>>
>> WARNING: [kernel]: An auto generated BSP description was used, this
>> normally indicates a misconfiguration.
>> Check that your machine (myqemux86-64) has an associated kernel
>> description.
>>
>> [YOCTO: #3383]
>>
>> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
>> ---
>> meta/classes/kernel-yocto.bbclass | 9 +++++++++
>> 1 file changed, 9 insertions(+)
>>
>> diff --git a/meta/classes/kernel-yocto.bbclass b/meta/classes/kernel-
>> yocto.bbclass
>> index 0cbbb5f2d22f..a5e2b180c496 100644
>> --- a/meta/classes/kernel-yocto.bbclass
>> +++ b/meta/classes/kernel-yocto.bbclass
>> @@ -281,6 +281,15 @@ python do_kernel_configcheck() {
>> with open (nonhw_file, "r") as myfile:
>> results = myfile.read()
>> bb.warn( "[kernel config]: BSP specified non-hw
>> configuration:\n\n%s" % results)
>> +
>> + bsp_desc = "${S}/" + kmeta + "/" + "top_tgt"
>> + if os.path.exists(bsp_desc):
>> + with open (bsp_desc, "r") as myfile:
>> + bsp_tgt = myfile.read()
>> + m = re.match("^(.*)scratch.obj(.*)$", bsp_tgt)
>> + if not m is None:
>> + bb.warn( "[kernel]: An auto generated BSP description was used,
>> this normally indicates a misconfiguration.\n" +
>> + "Check that your machine (%s) has an
>> + associated kernel description." % "${MACHINE}" )
>> }
>>
>> # Ensure that the branches (BSP and meta) are on the locations specified by
>> --
>> 2.1.0
>>
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
^ permalink raw reply [flat|nested] 8+ messages in thread