diff options
| author | Mcgrof <anonymous.contributor@example.org> | 2014-11-17 18:44:06 +0000 |
|---|---|---|
| committer | Konstantin Ryabitsev <konstantin@linuxfoundation.org> | 2024-10-04 15:47:33 -0400 |
| commit | c5574171f772d8683466390f4dabaa96af891428 (patch) | |
| tree | 92eb877e9f1b0a9dddf8ac70495b336a689a894a | |
| parent | f72e40422c0ef8702483cadcb497ec2785e2a7d3 (diff) | |
| download | backports-c5574171f772d8683466390f4dabaa96af891428.tar.gz | |
Update Documentation
| -rw-r--r-- | wiki/Documentation.mediawiki | 70 |
1 files changed, 2 insertions, 68 deletions
diff --git a/wiki/Documentation.mediawiki b/wiki/Documentation.mediawiki index af0ee89..e6149a0 100644 --- a/wiki/Documentation.mediawiki +++ b/wiki/Documentation.mediawiki @@ -6,8 +6,8 @@ The Linux kernel backports project aims at backporting Linux '''upstream''' devi <h2>Backport uses</h2> - * Backports package releases - * Backport kernel integration +* [[packaging|Backports package releases]] +* [[integration|Backports kernel integration]] <h2>Release types</h2> @@ -29,71 +29,5 @@ Whether or not a device driver is available from a subsytem will depend on wheth Users should just install what they ''know'' they need, if not sure don't enable a driver. Typically Linux distributions would use the backports project and build modules for you and you'd have a backports package available for your distribution. -<h2>Usage guide</h2> - -Building backports follows the same build mechanism as building the Linux kernel. - -<pre> -# as a user -make menuconfig -make -j4 -# as root -make install -# reboot and enjoy -</pre> - -Its understood users may not know how to configure the backports package, just like they may not know how to configure the Linux kernel, so a short cut is provided with default configuration files that can be used to only build their drivers / subsystems of interest. You can also just query the regular help menu. - -<pre> -make help -make defconfig-help -</pre> - -If you use this option just use the 'make defconf-option' in replacement for ''make menuconfig'' above. For example to compile all wifi drivers: - -<pre> -# as a user -make defconfig-wifi -make -j4 -# as root -make install -</pre> - -Note that there are only default configuration files written for a few drivers while the project actually backports a lot of device drivers, the reason we have default configuration files for a few drivers is simply because developer have provided a default config options for them. What we really need is a 'make localmodconfig' support but that will take a while given that it involves mapping older kernel configs to newer kernel configs (which likely would be welcomed upstream as well). - -<h2>Cross compiling</h2> - -To cross compile: - - set -a - CROSS_COMPILE=${CROSS_COMPILE} - ARCH=${TARGET_CPU} - KLIB_BUILD=${DEV_PATH}/${LINUX_DIR} - KLIB=${TARGET_ROOT_ON_HOST} - set +a - make oldconfig # menuconfig worked here too - make - make install - -The 'make install' target isn't currently sane for cross-builds due to the bacport_firmware_install script not respecting prefixes. For now you can comment out that script few others like initrd updates, from being run out of the Makefiles. - -<h2>Cross compile with Freescale's LTIB</h2> - -To get backports happy in LTIB, use UNSPOOF/SPOOF_PATH to switch between host and cross environment. Example <i>Build</i> section in backports.spec - - %Build - export PATH=$UNSPOOF_PATH - - make menuconfig prefix=%{_prefix} \ - CROSS_COMPILE=${TOOLCHAIN_PATH}/bin/${TOOLCHAIN_PREFIX} \ - ARCH=$LINTARCH KLIB=${TOP}/rootfs/lib/modules/%{kversion} \ - KLIB_BUILD=${TOP}/rpm/BUILD/linux - - export PATH=$SPOOF_PATH - - make prefix=%{_prefix} \ - CROSS_COMPILE=${TOOLCHAIN_PATH}/bin/${TOOLCHAIN_PREFIX} \ - ARCH=$LINTARCH KLIB=${TOP}/rootfs/lib/modules/%{kversion} \ - KLIB_BUILD=${TOP}/rpm/BUILD/linux [[File:88x31.png]] - This text is licensed under a [https://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.0 Unported License].
\ No newline at end of file |