linux/poky.git/meta/classes/kernel.bbclass, branch 1.3_M3.rc2

kernel.bbclass: Revert ${base_libdir} change

2012-08-07T10:17:36+00:00

The base_libdir change in 5b8a4798ea2ea7df66bb53c26448251ea7da3dd9 breaks the kernel build for 64 bit machines. Revert this part of the change. (From OE-Core rev: 351bdc59f8af915ae203af7799eedc0ce42785f2) Signed-off-by: Richard Purdie

kernel.bbclass: use ${base_libdir} and ${sysconfdir} instead of /lib and /etc

2012-08-06T14:18:51+00:00

It is considered good practice to use the build system provided variables instead of directly specify hardcoded paths. (From OE-Core rev: c859717f522098e7c68df578d59011f68122dc2c) Signed-off-by: Javier Martinez Canillas Signed-off-by: Richard Purdie

kernel.bbclass: Copy bounds.h only if it exists, needed for 2.6.x.

2012-07-31T07:02:09+00:00

Linux 2.6.x kernels did not (all) have the bounds.h file, so copy only iff exists. (From OE-Core rev: 02ac0d1b65389e1779d5f95047f761d7a82ef7a4) Signed-off-by: Leon Woestenberg Signed-off-by: Richard Purdie

kernel bbclass: Recreate uImage only when KEEPUIMAGE != "yes"

2012-07-26T13:40:47+00:00

The intent of the uImage code in this class includes the following 1) be able to specify custom load addresses without needing to patch the kernel 2) add better information to the uImage description field The current state is a NOP anyway, the kernel will always build a uImage when you tell it to 'make uImage'. weakly Set KEEPUIMAGE to 'yes' in default-distrovars.inc which preserve the current OE-Core behavior. Machines which are being ported from oe.dev and need to regenerate uImage can set this to be empty (From OE-Core rev: 72a7049526ee107005bd39c7bdd814ed71345829) Signed-off-by: Koen Kooi Signed-off-by: Khem Raj Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

kernel.bbclass: fix external module building

2012-07-26T13:40:45+00:00

Without that fix we have the following while compiling compat-wireless. include/linux/mmzone.h:18:30: fatal error: generated/bounds.h: No such file or directory Note that the compat-wireless recipe will be added in another commit. make -C $kerneldir _mrproper_scripts deleted this file along with other things so we resurrect it with this patch. (From OE-Core rev: 2d114fd0cdf7486f18e53f2bf41c4f559e4b4a8d) Signed-off-by: Denis 'GNUtoo' Carikli Signed-off-by: Koen Kooi Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

Convert tab indentation in python functions into four-space

2012-07-19T09:24:50+00:00

(From OE-Core rev: 604d46c686d06d62d5a07b9c7f4fa170f99307d8) Signed-off-by: Richard Purdie

kernel.bbclass: Dont package kxgettext.o

2012-07-17T09:54:02+00:00

kxgettext.o is generated when building ppc kernels so we end up with packaging errors like > ERROR: QA Issue: Architecture did not match (20 to 62) on > /work/virtex5-poky-linux/linux-xilinx-2.6.38-r00/packages-split/kernel-dev/usr/src/kernel/scripts/kconfig/kxgettext.o (From OE-Core rev: 77278bd23617834c7f90b3b24a9945ec081dbb38) Signed-off-by: Khem Raj Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

kernel.bbclass: add non-santized kernel provides

2012-07-09T15:59:00+00:00

If the kernel version string uses characters or symbols that need to be santized for the package name, we can end up with a mismatch between module requirements and what the kernel provides. The kernel version is pulled from utsrelease.h, which contains the exact string that was passed to the kernel build, not one that is santized, this can result in: echo "CONFIG_LOCALVERSION="\"MYVER+snapshot_standard\" >> ${B}/.config % rpm -qp kernel-module-uvesafb-3.4-r0.qemux86.rpm --requires update-modules kernel-3.4.3-MYVER+snapshot_standard % rpm -qp kernel-3.4.3-myver+snapshot-standard-3.4-r0.qemux86.rpm --provides kernel-3.4.3-myver+snapshot-standard = 3.4-r0 At rootfs assembly time, we'll have a dependency issue with the kernel providing the santizied string and the modules requiring the utsrelease.h string. To not break existing use cases, we can add a second provides to the kernel packaging with the unsantized version string, and allowing the kernel module packaging to be unchanged. RPROVIDES_kernel-base += "kernel-${KERNEL_VERSION}" % rpm -qp kernel-3.4.3-myver+snapshot-standard-3.4-r0.qemux86.rpm --provides kernel-3.4.3-MYVER+snapshot_standard kernel-3.4.3-myver+snapshot-standard = 3.4-r0 (From OE-Core rev: 7be043178f5b9d16d9a06696bc0b96689f202a8d) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

kernel: Add kernel headers to kernel-dev package

2012-07-04T16:40:33+00:00

[YOCTO #1614] Add the kernel headers to the kernel-dev package. This packages what was already built and kept in sysroots for building modules with bitbake. Making this available on the target requires removing some additional host binaries. Move the location to /usr/src/kernel Before use on the target, the user will need to: # cd /usr/src/kernel # make scripts This renders the kernel-misc recipe empty, so remove it. As we use /usr/src/kernel in several places (and I missed one in the previous version), add a KERNEL_SRC_DIR variable and use that throughout the class to avoid update errors in the future. Now that we package the kernel headers, drop the kernel_package_preprocess function which removed them from PKGD. All *-sdk image recipes include dev-pkgs, so the kernel-dev package will be installed by default on all such images. (From OE-Core rev: 6125ea40d4483965f793bd847b3ce14b668a5b1e) Signed-off-by: Darren Hart CC: Bruce Ashfield CC: Tom Zanussi CC: Khem Raj Signed-off-by: Richard Purdie

recipes-kernel: make perf a standalone package

2012-06-21T12:03:04+00:00

perf has been coupled to the kernel packages via kernel.bbclass. While maintaining the build of perf out of the kernel source tree is desired the package coupling has proved to be awkward in several situations such as: - when a kernel recipe doesn't want to build/provide perf - when licensing of dependencies would prohibit perf and hence the kernel from being built. To solve some of these problems, this recipe is the extraction of the linux-tools.inc provided perf compilation into a standalone perf recipe that builds out of the kernel source, but is otherwise independent. No new functionality is provided above what the linux-tools.inc variant provided, but the separate recipe provides baseline for adding new functionality. (From OE-Core rev: ab883d0c1a05bd99e97e5d71bc7bed05cb1ae8c8) Signed-off-by: Liang Li Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie