Differences

This shows you the differences between two versions of the page.

doc:devel:patches [2013/04/23 22:35]
jero patch: add clarification for host packages
doc:devel:patches [2014/06/27 10:59] (current)
jow tools != host builds of packages
Line 154: Line 154:
The process for modifying kernel patches is the same as for packages, only the make targets and directories differ.\\ The process for modifying kernel patches is the same as for packages, only the make targets and directories differ.\\
-:!: For the kernel, an additional subdirectory for patches is used, ''generic/'' contains patches common to all architectures and ''target/'' contains patches specific to the current target.+:!: For the kernel, an additional subdirectory for patches is used, ''generic/'' contains patches common to all architectures and ''platform/'' contains patches specific to the current target.
To prepare the kernel tree, use: To prepare the kernel tree, use:
Line 168: Line 168:
| ''make target/linux/update package/index V=s'' | | ''make target/linux/update package/index V=s'' |
-The last command for moving the changes back over the buildroot tree seems not to work with Attitude Adjustment 12.09-rc1; since if we typed such a command our patch will be deleted because it had remained in the temporary folder //build_dir// where it was created.So a workaround in order to have our patch applied is moving the patch to the proper folder manually. That is to say, if we have followed the previous sections in which we modified or created a new patch, after issuing'' quilt refresh'', our patch will appear under the next directory +(:!: Patches should be named with the correct prefix, platform/000-abc.patch or generic/000-abc.patch. If not the update may not work correctly.)
- +
-''~/attitude_adjustment/build_dir/linux-*/linux-*/patches/'' +
- +
-Therefore, depending on the changes we want to add to the kernel, we should copy that patch to one of these directories +
- +
-  * ''~/attidude_adjustment/target/linux/generic/patches-3.3'' -> it will in theory get applied to all platforms +
-  * ''~/attidude_adjustment/target/linux/<platform>/patches-3.<3>'' -> it gets only applied to the specific platform you place it +
- +
-Thus, we have to move our patch to one of those directories, for example the first one +
-| ''cp whateverNameYouSet.patch ~/attitude_adjustment/target/linux/generic/patches-3.3/'' |+
Afterwards, if we want to verify whether our patch is applied or not, we can go to the top level directory with Afterwards, if we want to verify whether our patch is applied or not, we can go to the top level directory with
Line 186: Line 176:
| ''make target/linux/{clean,prepare} V=s QUILT=1'' | | ''make target/linux/{clean,prepare} V=s QUILT=1'' |
-During this process all the applied patched will be shown, being our among them, preceede by //generic/// or // platform/// depending on what directory we placed the patch. Another way of retreiving the applied patches is through +During this process all the applied patched will be shown, ours being among them, preceeded by //generic/// or // platform/// depending on what directory we placed the patch. Another way of retrieving the applied patches is through
| ''quilt series'' | | ''quilt series'' |

Back to top

doc/devel/patches.1366749355.txt.bz2 · Last modified: 2013/04/23 22:35 by jero