diff options
| author | Johannes Berg <anonymous.contributor@example.org> | 2014-05-21 19:17:03 +0000 |
|---|---|---|
| committer | Konstantin Ryabitsev <konstantin@linuxfoundation.org> | 2024-10-04 15:47:32 -0400 |
| commit | 78b564a7723ade11f03264a406934e6dd59c8fe4 (patch) | |
| tree | 3eb0041d9286ccef34062cb9f75e5a50e2c70031 | |
| parent | ca8685f3294bac6b0e46745239cd6bfa947904dd (diff) | |
| download | backports-78b564a7723ade11f03264a406934e6dd59c8fe4.tar.gz | |
Update Documentation
| -rw-r--r-- | wiki/Documentation.mediawiki | 15 |
1 files changed, 7 insertions, 8 deletions
diff --git a/wiki/Documentation.mediawiki b/wiki/Documentation.mediawiki index 56a3f1f..ec79e5f 100644 --- a/wiki/Documentation.mediawiki +++ b/wiki/Documentation.mediawiki @@ -2,7 +2,7 @@ title: Documentation --- -The Linux kernel backports project aims at backporting Linux '''upstream''' device drivers for usage on older kernels. The point of the project is to provide a central mechanism for backporting device drivers for ''any'' subsystem and enable ''both'' users '''and''' developers to always focus on upstream Linux kernel development. The backports project shall '''never''' include proprietary drivers and by design does not allow usage of itself with proprietary drivers. Every backports release has been test compiled ''for usage'' against all supported kernels, currently 2.6.24 - latest. Note that Linux kernel releases can become deprecated. Right now we provide backport support for all kernels 2.6.24 up to the latest release inclusive even if a kernel is deprecated however you are encouraged to follow the best practices and at the '''very''' least be on a supported Linux kernel. Supported stable kernels are annotated on [http://kernel.org kernel.org]. +The Linux kernel backports project aims at backporting Linux '''upstream''' device drivers for usage on older kernels. The point of the project is to provide a central mechanism for backporting device drivers for ''any'' subsystem and enable ''both'' users '''and''' developers to always focus on upstream Linux kernel development. The backports project shall '''never''' include proprietary drivers and by design does not allow usage of itself with proprietary drivers. Every backports release has been test compiled ''for usage'' against all supported kernels, the oldest one is (currently) 3.0. Note that Linux kernel releases can become deprecated. You are encouraged to use supported stable kernels as listed on [http://kernel.org kernel.org]. <h2>Release types</h2> @@ -16,12 +16,11 @@ Device drivers are available for the following subsystems: * Wireless * Bluetooth * NFC - * ieee802154 (will be available on v3.11 releases) - * GPU + * ieee802154 * Media * Regulator -Whether or not a device driver is available from a subsytem will depend on whether or not a developer decided to backport it '''and''' if the device driver is backported down to the kernel you are on. If you see the driver on '''make menuconfig''' it means you can use it. An alternative is to look at the git tree [https://git.kernel.org/cgit/linux/kernel/git/mcgrof/backports.git/tree/dependencies dependencies] file. Note that the [https://git.kernel.org/cgit/linux/kernel/git/mcgrof/backports.git/tree/dependencies dependencies] '''does not''' exist on a final release, it only exists on the development git tree and the one linked here is the one on the master branch -- you should look at the [https://git.kernel.org/cgit/linux/kernel/git/mcgrof/backports.git/refs/ release branches] for their respective dependencies file if using an older release. Someone is welcome to come up with a fancy page that provides the device driver <--> kernel dependency map page. If a device driver is available on '''make menuconfig''' but is not listed on the [https://git.kernel.org/cgit/linux/kernel/git/mcgrof/backports.git/tree/dependencies dependencies] file it means it is available for usage on all supported kernel, v2.6.24 - on. +Whether or not a device driver is available from a subsytem will depend on whether or not a developer decided to backport it '''and''' if the device driver is backported down to the kernel you are on. If you see the driver on '''make menuconfig''' it means you can use it. An alternative is to look at the git tree [https://git.kernel.org/cgit/linux/kernel/git/mcgrof/backports.git/tree/dependencies dependencies] file. Note that the [https://git.kernel.org/cgit/linux/kernel/git/mcgrof/backports.git/tree/dependencies dependencies] '''does not''' exist on a final release, it only exists on the development git tree and the one linked here is the one on the master branch -- you should look at the [https://git.kernel.org/cgit/linux/kernel/git/mcgrof/backports.git/refs/ release branches] for their respective dependencies file if using an older release. Someone is welcome to come up with a fancy page that provides the device driver <--> kernel dependency map page. If a device driver is available on '''make menuconfig''' but is not listed on the [https://git.kernel.org/cgit/linux/kernel/git/mcgrof/backports.git/tree/dependencies dependencies] file it means it is available for usage on all supported kernel. 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. @@ -38,24 +37,24 @@ make install # reboot and enjoy </pre> -Its understood users may not 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. +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 DRM drivers: +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-drm +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 over 830 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). +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> |