linux-yocto: consolidated update
cover linux-yocto: consolidated update
Richard/Saul,
A small ``consolidated'' update this time. Two fixes, one to the build/tools, one meta branch update for KVM guests.
The tools fix is something that I've been wanting to get to for a month now .. and I finally did. Matthew Foster reported the strange messages when working with linux-yocto-custom. It is now fixed, and no more nasty looking messages. The details of the messages and fix are in the patch.
The second meta/config patch is to embed some fragments for use by a KVM guest. These will be used by other updates to the tools/scripts to follow.
Cheers,
Bruce
The following changes since commit 7401ed019196313a7ae7cab0b9f3820356cfee29:
Update to upstream_tracking.inc (2012-09-12 17:56:58 +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 (2):
kernel-yocto: fix kernel configuration audit for custom yocto kernels
linux-yocto: virtio and KVM guest configuration
meta/classes/kernel-yocto.bbclass | 7 ++++++- .../kern-tools/kern-tools-native_git.bb | 2 +- meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb | 2 +- meta/recipes-kernel/linux/linux-yocto_3.4.bb | 2 +- 4 files changed, 9 insertions(+), 4 deletions(-)
Signature · 1 line
1.7.5.4
PATCH 1/2 kernel-yocto: fix kernel configuration audit for custom yocto kernels
It was reported that the kernel configuration checks for custom yocto kernels had the following output:
NOTE: validating kernel configuration
grep: /meta-series: No such file or directory
grep: /meta-series: No such file or directory
WARNING: Can't find any BSP hardware or required configuration fragments.
WARNING: Looked at //cfg///hdw_frags.txt and //cfg///required_frags.txt in directory: //cfg//
NOTE: Tasks Summary: Attempted 375 tasks of which 367 didn't need to be rerun and all succeeded.
which is not inspire confidence in the output of the process.
Completely inhibiting the check is one option to remove the messages, but that removes the ability see output, which can help move users to a better or more fully configured linux-yocto based kernel.
To fix this, we have to ensure that the path to the meta-series is always valid, and that the tools can deal with not all files existing in the audit directory.
Since custom yocto kernels do not set KMETA (they don't have a meta branch), we ensure that a default of 'meta' is passed to the audit ('meta' is always valid), and that kconf_check itself can deal with an incomplete set of input audit files.
The net result is output like this (using a defconfig with invalid options for the kernel being built):
NOTE: validating kernel configuration
This BSP sets 19 invalid/obsolete kernel options. These config options are not offered anywhere within this kernel. The full list can be found in your kernel src dir at:
meta/cfg/standard/qemux86/invalid.cfg
There were 1 instances of config fragment errors. The full list can be found in your kernel src dir at:
meta/cfg/standard/qemux86/fragment_errors.txt
The full list can be found in your kernel src dir at:
meta/cfg/standard/qemux86/missing_required.cfg
--- meta/classes/kernel-yocto.bbclass | 7 ++++++- .../kern-tools/kern-tools-native_git.bb | 2 +- 2 files changed, 7 insertions(+), 2 deletions(-)
meta/classes/kernel-yocto.bbclass +6 -1
@@ -212,8 +212,13 @@ python do_kernel_configcheck() { bb.plain("NOTE: validating kernel configuration") + # 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 + kmeta = d.getVar( "KMETA", True ) or "meta" + pathprefix = "export PATH=%s:%s; " % (d.getVar('PATH', True), "${S}/scripts/util/") - cmd = d.expand("cd ${S}; kconf_check -config- ${KMETA}/meta-series ${S} ${B}") + cmd = d.expand("cd ${S}; kconf_check -config- %s/meta-series ${S} ${B}" % kmeta) ret, result = commands.getstatusoutput("%s%s" % (pathprefix, cmd)) bb.plain( "%s" % result )
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 guilt-native" -SRCREV = "0c7b625280eb9ff62d40b53308e7238ddd164f38" +SRCREV = "a04138a02644eada0d012196e5ac3db4f516114d" PR = "r12" PV = "0.1+git${SRCPV}"
Signature · 1 line
1.7.5.4
PATCH 2/2 linux-yocto: virtio and KVM guest configuration
In reply to Bruce AshfieldUpdating the meta branch SRCREV to pick up virtio and kvm guest configuration fragments.
79947f1 meta: add paravirtualized KVM guest config fragment 3ed86ed meta: add MMIO support in virtio config fragment
--- meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb | 2 +- meta/recipes-kernel/linux/linux-yocto_3.4.bb | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb +1 -1
@@ -10,7 +10,7 @@ KMETA = "meta" SRCREV_machine ?= "a35693b1287c0e50cdca33a1b95af0ff48b43cd0" SRCREV_machine_qemuppc ?= "85a1190530cb5749f5f831670976b163438dc301" -SRCREV_meta ?= "e0374ce012e7e6fc8e5bb8b957addb0478950898" +SRCREV_meta ?= "79947f1eb9f695c374ba63672f94deaa1de75561" PR = "${INC_PR}.0" PV = "${LINUX_VERSION}+git${SRCPV}"
meta/recipes-kernel/linux/linux-yocto_3.4.bb +1 -1
@@ -9,7 +9,7 @@ SRCREV_machine_qemuppc ?= "b9a720ca38d298ed457f37d099c85771f9164b19" SRCREV_machine_qemux86 ?= "46d8c757b3be1953f30d6745505d24436e2d6844" SRCREV_machine_qemux86-64 ?= "46d8c757b3be1953f30d6745505d24436e2d6844" SRCREV_machine ?= "46d8c757b3be1953f30d6745505d24436e2d6844" -SRCREV_meta ?= "e0374ce012e7e6fc8e5bb8b957addb0478950898" +SRCREV_meta ?= "79947f1eb9f695c374ba63672f94deaa1de75561" SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.4.git;protocol=git;nocheckout=1;branch=${KBRANCH},meta;name=machine,meta"
Signature · 1 line
1.7.5.4
Saul Wold
AppliedQuoted 31 lines · Bruce Ashfield
Richard/Saul,
A small ``consolidated'' update this time. Two fixes, one to the build/tools, one meta branch update for KVM guests.
The tools fix is something that I've been wanting to get to for a month now .. and I finally did. Matthew Foster reported the strange messages when working with linux-yocto-custom. It is now fixed, and no more nasty looking messages. The details of the messages and fix are in the patch.
The second meta/config patch is to embed some fragments for use by a KVM guest. These will be used by other updates to the
tools/scriptsto follow.Cheers,
Bruce
The following changes since commit
7401ed019196313a7ae7cab0b9f3820356cfee29:Update to upstream_tracking.inc (2012-09-12 17:56:58 +0100)are available in the git repository at:
git://git.pokylinux.org/poky-contribzedd/kernel
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernelBruce Ashfield (2):
kernel-yocto: fix kernel configuration audit for custom yocto kernels
linux-yocto: virtio and KVM guest configuration
Quoted 6 lines
meta/classes/kernel-yocto.bbclass | 7 ++++++- .../kern-tools/kern-tools-native_git.bb | 2 +- meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb | 2 +- meta/recipes-kernel/linux/linux-yocto_3.4.bb | 2 +- 4 files changed, 9 insertions(+), 4 deletions(-)
Merged into OE-Core
Thanks
Sau!