diff options
| author | Hauke <anonymous.contributor@example.org> | 2013-07-20 14:12:26 +0000 |
|---|---|---|
| committer | Konstantin Ryabitsev <konstantin@linuxfoundation.org> | 2024-10-04 15:47:32 -0400 |
| commit | 155871b1f8a769633d49784acc4111293349972d (patch) | |
| tree | 5f42aed4ae315fab3d11825bffc2d3b4e7afc22d | |
| parent | bb6232a6c150e08132db02a5b288d86e5b364524 (diff) | |
| download | backports-155871b1f8a769633d49784acc4111293349972d.tar.gz | |
rework adding new driver
| -rw-r--r-- | wiki/Documentation_backports_hacking.mediawiki | 15 |
1 files changed, 12 insertions, 3 deletions
diff --git a/wiki/Documentation_backports_hacking.mediawiki b/wiki/Documentation_backports_hacking.mediawiki index e6bb02c..0ab4870 100644 --- a/wiki/Documentation_backports_hacking.mediawiki +++ b/wiki/Documentation_backports_hacking.mediawiki @@ -38,9 +38,18 @@ This will take the path to the already checked out linux-next kernel as the seco = Adding new driver = -When adding a new driver you first have to copy it to the resulting release by adding it to the copy-list file in the root directory of backports. -If this backported driver does not work on all supported kernel versions you have to specify it in the dependencies file. -You should also add a new defconfig for your driver to /backport/defconfigs/ +This is a list of steps to be done when adding a new driver. Not all steps are needed for every new driver it depends on what type of driver is added. You can take the patch adding support for the ieee802154 subsystem as a reference [https://git.kernel.org/cgit/linux/kernel/git/mcgrof/backports.git/commit/?id=a42aa4d474e5859164a00bf451970fb58b676fcf]. + +You should target the master branch of the backports repository. + +# Add directories and files that should be copied from the mainline kernel to <code>copy-list</code> +# Add patches to <code>patches/collateral-evolutions/</code> if needed, it is better to add or modify a header file in <code>backport/backport-include/</code> than adding a patch. +# Add reference to the newly added driver directory in <code>backport/Makefile.kernel</code> if needed (just needed for new substems) +# Add reference to the newly added driver directory in <code>backport/Kconfig</code> if needed (just needed for new subsystems) +# Add a defconfig file for this driver in <code>backport/defconfigs/</code> and modify other defconfig files if appropriate, e.g. if you add a wifi driver add it to <code>backport/defconfigs/wifi</code> +# If the driver does not build on all kernel versions specify a minimum kernel version in <code>dependencies</code> + +Backports currently supports the latest minor version of every mainline kernel starting from 2.6.24. You should check that backports still builds after making your changes. To do so you should install all supported kernel with the script in <code>devel/get-compat-kernels</code> and then run <code>devel/ckmake</code> to build backports against every kernel version. = Backporting a kernel feature = |