Code
(→Backports code) |
|||
(9 intermediate revisions by one user not shown) | |||
Line 1: | Line 1: | ||
+ | In order to backport the Linux kernel we must divide and conquer the tasks at hand. | ||
− | + | This is now deprecated use [[Documentation/backports/hacking|hacking on backports]]. | |
+ | <h1>Backport components</h1> | ||
− | * git://github.com/mcgrof/compat.git | + | There are currently two components to the backports effort. |
− | * git://github.com/mcgrof/compat-drivers.git | + | |
+ | <h2>compat</h2> | ||
+ | |||
+ | compat is a shared module / headers that implements newer features for usage on older kernels. | ||
+ | |||
+ | * [https://github.com/mcgrof/compat git://github.com/mcgrof/compat.git] [[compat|compat documentation]] | ||
+ | |||
+ | <h2>compat-drivers</h2> | ||
+ | |||
+ | compat-drivers is the framework that pulls code from the Linux kernel, adds the compat module and backports features that compat could not backport within its module / headers. | ||
+ | |||
+ | * [https://github.com/mcgrof/compat-drivers git://github.com/mcgrof/compat-drivers.git] [[compat-drivers|compat-drivers documentation]] | ||
+ | |||
+ | <h1>Getting all required code</h1> | ||
To be able to make releases and test building releases however you need quite a bit more code. The setup is simplified with scripts from the compat.git tree. To set your system up for the first time you can run: | To be able to make releases and test building releases however you need quite a bit more code. The setup is simplified with scripts from the compat.git tree. To set your system up for the first time you can run: | ||
Line 18: | Line 33: | ||
</pre> | </pre> | ||
</code> | </code> | ||
+ | |||
+ | <h1>Hacking on the project</h1> | ||
+ | |||
+ | You should realize that there are a few components to the project and that although they are used together each one can be considered independent of each other. | ||
+ | |||
+ | * Read the [[compat|hacking on compat documentation]]. | ||
+ | * Read the [[Hacking|hacking on compat-drivers documentation]]. | ||
+ | |||
+ | <h2>TODO list</h2> | ||
+ | |||
+ | Read the [[Hacking#TODO|hacking TODO]] for a list of wish items we should be working towards. |
Latest revision as of 21:02, 13 June 2013
In order to backport the Linux kernel we must divide and conquer the tasks at hand.
This is now deprecated use hacking on backports.
Contents |
Backport components
There are currently two components to the backports effort.
compat
compat is a shared module / headers that implements newer features for usage on older kernels.
* git://github.com/mcgrof/compat.git compat documentation
compat-drivers
compat-drivers is the framework that pulls code from the Linux kernel, adds the compat module and backports features that compat could not backport within its module / headers.
* git://github.com/mcgrof/compat-drivers.git compat-drivers documentation
Getting all required code
To be able to make releases and test building releases however you need quite a bit more code. The setup is simplified with scripts from the compat.git tree. To set your system up for the first time you can run:
wget https://github.com/mcgrof/compat/raw/master/bin/get-compat-trees wget https://github.com/mcgrof/compat/raw/master/bin/get-compat-kernels chmod 755 get-compat-trees get-compat-kernels ./get-compat-trees ./get-compat-kernels
Hacking on the project
You should realize that there are a few components to the project and that although they are used together each one can be considered independent of each other.
* Read the hacking on compat documentation. * Read the hacking on compat-drivers documentation.
TODO list
Read the hacking TODO for a list of wish items we should be working towards.