Documentation
(Revise introduction) |
|||
| Line 1: | Line 1: | ||
| − | The | + | The Backports Project aims to backport current Linux '''upstream''' device drivers for use with older kernels. The objective (1) is to provide a central mechanism for backporting the device drivers of ''any'' subsystem, thereby enabling (2) ''both'' users '''and''' developers to always focus on upstream Linux kernel development. |
| + | |||
| + | The project shall '''never''' include proprietary drivers, and is designed to disallow its use with proprietary drivers. | ||
| + | |||
| + | Backports supports backporting in either of two modes: | ||
| + | |||
| + | *'''package''' mode, where backports produces a tarball (loosely akin to a patch) containing the subsystems/drivers of a future kernel | ||
| + | * direct kernel integration mode, where backports directly '''integrates''' the subsystems/drivers of a future kernel into an older kernel tree | ||
| + | |||
| + | Every backports release has been test compiled ''for usage'' against all supported kernels. The oldest release is (currently) 3.0. | ||
| + | |||
| + | Linux kernel releases can become deprecated. You are encouraged to use supported stable kernels as listed on [http://kernel.org kernel.org]. | ||
<h2>Backport uses</h2> | <h2>Backport uses</h2> | ||
Revision as of 03:14, 25 June 2017
The Backports Project aims to backport current Linux upstream device drivers for use with older kernels. The objective (1) is to provide a central mechanism for backporting the device drivers of any subsystem, thereby enabling (2) both users and developers to always focus on upstream Linux kernel development.
The project shall never include proprietary drivers, and is designed to disallow its use with proprietary drivers.
Backports supports backporting in either of two modes:
- package mode, where backports produces a tarball (loosely akin to a patch) containing the subsystems/drivers of a future kernel
- direct kernel integration mode, where backports directly integrates the subsystems/drivers of a future kernel into an older kernel tree
Every backports release has been test compiled for usage against all supported kernels. The oldest release is (currently) 3.0.
Linux kernel releases can become deprecated. You are encouraged to use supported stable kernels as listed on kernel.org.
Backport uses
Currently backported subsystems
Device drivers are available for the following subsystems:
* Ethernet * Wireless * Bluetooth * NFC * 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 dependencies file. Note that the 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 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 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.
- This text is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
