linux/poky.git/meta/classes/module.bbclass, branch dizzy

kernel: extract functions for kernel modules to separate bbclass

2013-03-05T13:14:50+00:00

* this way we can reuse the same functionality also for external modules including module_autoload_foo and module_conf_foo functionality * MODULE_PACKAGES variable was removed (splited modules are now returned by do_split_packages * KERNEL_MODULES_META_PACKAGE is used to append all splitted packages to RDEPENDS. In kernel.bbclass it's old "kernel-modules" in module.bbclass it defaults to ${PN} for upgrade path from single PN with all modules to PN depending on all new kernel-module-* (From OE-Core rev: 51928b6b5ca0a46a9dcd754483a19af58b95fa18) Signed-off-by: Martin Jansa Signed-off-by: Richard Purdie

module.bbclass: Create a new depmodwrapper to assist cross-installs

2013-03-01T14:44:40+00:00

Previously the build path to STAGING_KERNEL_DIR was being embedded into the package post install scripts. We avoid this behavior by generating a special depmodwrapper script. This script contains that hard-coded path, ensuring that re-use of the sstate-cache (and/or packages) will always run through the wrapper generated by the current build with a checksum that includes STAGING_KERNEL_DIR. [ YOCTO #3962 ] (From OE-Core rev: b18c61bae4d7161c087a004bba3c696006f7a2f6) Signed-off-by: Mark Hatle Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

module.bbclass: Allow for modules to be packaged seperate from ${PN}

2013-02-01T15:54:30+00:00

This patch will allow recipes that provide kernel modules to package the module or modules in specific packages. That list is contained in MODULE_PACKAGES, this defaults to to preserve the current behavior. The package can also define MODULE_FILES to specify files. [YOCTO #3803] (From OE-Core rev: c1ff0467bf03a3342846f0d9dde74e34b740798f) (From OE-Core rev: 977aee43868499ab87a098f3798e90d6978836b9) Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

module.bbclass: Don't add pkg_postinst/pkg_prerm to all packages in recipe

2013-01-30T00:03:01+00:00

The code in module.bbclass was appending the pkg_postinst and pkg_prerm to all packages that are part of a given recipe, meaning that the -lic, -dev, -doc, ... packages all got the scriptlet This change uses only which macthes with the RDEPENDS and FILES already used in module.bbclass. The failure was that rootfs creation would fail due to the -lic package being installed before the kernel and the script would fail. [YOCTO #3803] (From OE-Core rev: cf05c4578c99c0cb885cf2706f7f2b39b100aeb8) Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

module.bbclass: do not use update-modules anymore

2013-01-18T13:28:07+00:00

update-modules is obsolete. The bbclass was updated not to use it anymore. [YOCTO #3598] (From OE-Core rev: 6fafbf71adb8b34211c2bc24226f0b1eb206a7d3) Signed-off-by: Laurentiu Palcu Signed-off-by: Richard Purdie

module.bbclass: make sure do_make_scripts() executes after do_patch()

2012-12-14T08:56:31+00:00

If do_make_scripts() executes before do_unpack()/do_patch(), the build fails because it can't cd into the workdir of a recipe using this class, so make sure do_make_scripts() doesn't run before the package has been unpacked and patched. Fixes [YOCTO #3589]. (From OE-Core rev: 824cf145bcb55bb99a717a2dfd73e43e6b3feea4) Signed-off-by: Tom Zanussi Signed-off-by: Richard Purdie

module.bbclass: Move do_make_scripts() to module-base

2012-10-18T11:13:34+00:00

It's sometimes useful to have this function available to recipes which don't wish to use module.bbclass for whatever reason. (From OE-Core rev: 7632b44e7f487180811d47fbe9c29aa8e58868a2) Signed-off-by: Phil Blundell Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

kernel.bbclass, module.bbclass: Make update-modules optional

2012-10-18T11:13:33+00:00

The update-modules mechanism is something of a historical relic and it isn't entirely clear that it has a great deal of value nowadays. Also, it causes a problem when building a read-only rootfs since update-modules itself refuses to configure offline. Allow DISTROs to circumvent this whole thing by declaring (via DISTRO_FEATURES) that they don't wish to use update-modules. This is backfilled for existing distributions and will have to be marked as CONSIDERED by those who actually don't want it. (From OE-Core rev: 14bf8ed115453077b4d4042b4b70ed6b3bca2a9f) Signed-off-by: Phil Blundell Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

{kernel, module}.bbclass: don't run depmod for module packages during do_rootfs

2012-04-26T09:05:15+00:00

* depmod already gets executed by pkg_postinst_kernel-image. * If you build a module using module.bbclass, pkg_postinst returns 1 in do_rootfs, causing pkg_postinst to run again on first boot. To improve this situation, I copied pkg_postinst from kernel.bbclass to module.bbclass. This was rejected by Koen, because he doesn't like the code from kernel.bblcass, which uses ${STAGING_DIR_KERNEL}. Richard then suggested that calling depmod during do_rootfs wasn't necessary at all, because it already gets done by kernel-image. (From OE-Core rev: c7809c03080925b5e9171df5c9175c7c6420b376) Signed-off-by: Andreas Oberritter Signed-off-by: Richard Purdie

module.bbclass: add lock to prevent error bulding ext modules

2011-10-20T16:13:41+00:00

When external modules are built, files in $STAGING_KERNEL_DIR/scripts/basic will/can get rebuilt. This raises a potential race condition. Prevent this by adding a lock around the do_make_scripts() function. Further, make sure that the kernel has been installed to the sysroot, prior to executing this new task. (From OE-Core rev: 8681b82e8b466929205edde7ba479f3ac1a6143e) Signed-off-by: Anders Darander Signed-off-by: Richard Purdie