linux/poky.git/meta/recipes-kernel/kmod, branch sumo

depmodwrapper-cross: Add kmod-native to DEPENDS

2018-06-15T16:56:57+00:00

Add `DEPENDS += "kmod-native"` to ensure depmod utility is added to recipe-sysroot-native during image build. Without this dependency, image builds where BUILD_IMAGES_FROM_FEEDS=1 have depmodwrapper in recipe-sysroot-native but are missing depmod. Kernel postinst scripts rely on depmod (via depmodwrapper) to index newly installed modules. (From OE-Core rev: d693457f9de92e4e8b61881638787e831f0ca197) (From OE-Core rev: c60711bb734dceb8274720c898eba11bfd8da749) Signed-off-by: Haris Okanovic Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

kmod: don't call gtkdocize twice

2018-03-15T13:27:19+00:00

The gtk-doc class already calls gtkdocize, so we don't need to do it again (From OE-Core rev: 14c6e4fd793e037d801a81c6581e0642ef61ab0c) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

kmod: refresh patches

2018-03-09T17:17:02+00:00

The patch tool will apply patches by default with "fuzz", which is where if the hunk context isn't present but what is there is close enough, it will force the patch in. Whilst this is useful when there's just whitespace changes, when applied to source it is possible for a patch applied with fuzz to produce broken code which still compiles (see #10450). This is obviously bad. We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For that to be realistic the existing patches with fuzz need to be rebased and reviewed. (From OE-Core rev: c94152fee766297b355fec7f6d3d4d8ba7ae5f86) Signed-off-by: Ross Burton Signed-off-by: Alexander Kanavin Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

kmod: 24 -> 25

2018-01-29T08:49:50+00:00

Upgrade kmod from 24 to 25. (From OE-Core rev: df525efab1cefa3e05e50544b1fbc790cc4cf850) Signed-off-by: Huang Qiyu Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

kernel: Add support for multiple kernel packages

2018-01-02T17:24:37+00:00

Some distros may want to provide alternate kernel "flavors" via feeds or within bootable images. For example, readily available builds which provide certain diagnostic features can enable developers and testers to more quickly resolve issues by avoiding lengthy kernel builds. This change allows for building multiple flavors of the kernel and module packages by templatizing kernel package names via a new KERNEL_PACKAGE_NAME variable in kernel.bbclass. It defaults to the old name of "kernel", but can be overridden by certain recipes providing alternate kernel flavors. To maintain compatibility, recipes providing alternate kernel flavors cannot be the "preferred provider" for virtual/kernel. This is because OE puts the preferred provider's build and source at "tmp-glibc/work-shared/$MACHINE/kernel-build-artifacts/" and "tmp-glibc/work-shared/$MACHINE/kernel-source/" instead of "tmp-glibc/work/*/$PN/" like other recipes. Therefore, recipes using the default KERNEL_PACKAGE_NAME="kernel" follows the old semantics -- build in the old location and may be preferred provider -- while recipes using all other KERNEL_PACKAGE_NAME's build from the normal WORKDIR and don't provide "virtual/kernel". Testing: 1. Add `KERNEL_PACKAGE_NAME_pn-linux-yocto-tiny = "tiny-linux"` to local.conf so that linux-yocto-tiny may build alongside the main kernel (linux-yocto). 2. `bitbake linux-yocto linux-yocto-tiny` to build both kernel flavors. 3. Verified image and modules IPKs exist for both: tmp-glibc/deploy/ipk/qemux86/kernel-* for linux-yocto tmp-glibc/deploy/ipk/qemux86/tiny-linux* for linux-yocto-tiny 4. Verified linux-yocto is the "preferred provider", and was built in shared directory: tmp-glibc/work-shared/qemux86/kernel-* 5. Add `CORE_IMAGE_BASE_INSTALL_append_pn-core-image-base = "tiny-linux"` to local.conf to install both kernel flavors in core-image-base. 6. `bitbake core-image-base` to build an image. 7. Verified image contains two bzImage's under /boot/, with "yocto-standard" (linux-yocto recipe) selected to boot via symlink. Discussion threads: http://lists.openembedded.org/pipermail/openembedded-core/2015-December/thread.html#114122 http://lists.openembedded.org/pipermail/openembedded-core/2017-July/thread.html#139130 [YOCTO #11363] (From OE-Core rev: 6c8c899849d101fd1b86aad0b8eed05c7c785924) Signed-off-by: Ioan-Adrian Ratiu Signed-off-by: Gratian Crisan Signed-off-by: Haris Okanovic Coauthored-by: Gratian Crisan Coauthored-by: Haris Okanovic Coauthored-by: Josh Hernstrom Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

depmodwrapper-cross: Set PACKAGES=''

2017-12-21T10:21:00+00:00

This recipe inherits nopackages but has a non-empty PACKAGES which confuses the archiver class when: INHERIT += "archiver" ARCHIVER_MODE[srpm] = "1" Ensuring PACKAGES is empty removes the errors that occur in this configuration. [YOCTO #11121] (From OE-Core rev: b8a603d3f1d3adac41d042e42a2283b7fdf2ae7c) Signed-off-by: Richard Purdie

kmod: upgrade to 24

2017-06-09T16:12:14+00:00

Drop kcmdline_quotes.patch as it has been integrated. (From OE-Core rev: 68880e7dc48df4707e2c67f7434603e516c335c6) Signed-off-by: Chen Qi Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

sstate.bbclass, staging.bbclass: Handle HOSTTOOLS_DIR when restoring state

2017-05-01T07:56:35+00:00

Paths to host tools that have been copied to ${HOSTTOOLS_DIR} may end up in the sstate cache. They thus need to be corrected when restoring from the sstate cache. (From OE-Core rev: f8671aecf05a286dd2b34b07bb5fbbe0c31e26d0) Signed-off-by: Peter Kjellerstedt Signed-off-by: Richard Purdie

kmod: set ac_cv_path_DOLT_BASH to /usr/bin/env bash

2017-04-10T22:00:43+00:00

The shebang's length is usually 128 as defined in /usr/include/linux/binfmts.h: #define BINPRM_BUF_SIZE 128 So there would be errors when /path/to/hosttools/bash is longer than 128: /bin/sh: ./doltcompile: [snip]: bad interpreter: No such file or directory Set ac_cv_path_DOLT_BASH to "/usr/bin/env bash" to fix the problem. (From OE-Core rev: fd2758ed26e8ed6d76c66af0275c4aafbec758ac) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie

depmodwrapper-cross/qemuwrapper-cross: Drop unneeded binutils dependency

2017-02-23T20:49:49+00:00

By default these pull in binutils-cross since they're a cross tool and pull in any native tool requirements. In reality they don't need such tools at build time or runtime since they're scripts. Therefore clear the dependency and save on some processing time. (From OE-Core rev: 63796765122e2eee2b78930797d571acb5c244d1) (From OE-Core rev: 50feffd0917b0ab408b34ded9c2f741a9c4e5b74) Signed-off-by: Richard Purdie