summaryrefslogtreecommitdiff
path: root/scripts/make-module-ipkgs.sh
AgeCommit message (Collapse)Author
2017-03-21rework kernel build process, changes to kernelconfig are reflected nowWaldemar Brodkorb
Cleanup the package directory which is always used as intermediate step to build in the default some xz compressed archives with all package data. While reconfiguring the kernel mini.config or custom config changes to the firmware did not happen always. Some targets where redundant and the install step tries to compile, too. Be more quiet with any cpio usage.
2015-12-20use strings instead of modinfo for a portable wayWaldemar Brodkorb
Idea from Phil to have a portable method to find the kernel module dependencies. make-module-ipkgs.sh uses associative arrays, so check for bash version 4.
2015-09-06remove unused call to modinfoWaldemar Brodkorb
2015-09-06scripts: fix make-module-ipkgs.shPhil Sutter
The recursive call of find_modlevel overwrites the loop variable 'dep' if not declared local before. Yay. Signed-off-by: Phil Sutter <phil@nwl.cc>
2015-08-03rework kernel module infrastructureWaldemar Brodkorb
Instead of maintaining mk/modules.mk which defines compilations of related kernel modules to pack together into a single package, follow an automatic approach: For every kernel module found in the modules installation directory, create a single package. There are a few caveats to cover: === Module Loading Order === Upon bootup, module loading is ordered based on the number-prefixed files in /etc/modules.d/. The correct number was previously managed in mk/modules.mk on a per-collection basis. The new approach is to have levels which modules are to be assigned to. Level 0 contains modules with no dependencies at all. Level 1 contains modules which have only level 0 dependencies, and so on. This information is determined at compile-time by make-module-ipkgs.sh. === Module Installation to Target RootFS === Since module packages are created automatically from the modules the script finds, ADK build system has no knowledge about the connection between what the user has selected in menuconfig and the actual module packages. Therefore the earlier approach to install selected packages into rootfs does not hold anymore. Instead, use wildcards to find all packages in firmware directory prefixed by 'kmod-' and install them all (hopefully doing the right thing). === Kernel Version === KERNEL_VERSION now contains KERNEL_RELEASE already By creating a localversion file, make KERNEL_RELEASE part of the kernel's version number (so KERNEL_VERSION is correct in most situations) Signed-off-by: Phil Sutter <phil@nwl.cc>