deleted>Frq08988 mNo edit summary |
Registered User mNo edit summary Tag: 2017 source edit |
||
(13 intermediate revisions by 6 users not shown) | |||
Line 1: | Line 1: | ||
<noinclude> | <noinclude>{{ApplicableFor | ||
{{ | |MPUs list=STM32MP13x, STM32MP15x, STM32MP25x | ||
|MPUs checklist=STM32MP13x, STM32MP15x, STM32MP25x | |||
}}</noinclude> | |||
</noinclude> | |||
==Purpose of article== | ==Purpose of article== | ||
This article gives the main steps needed to add kernel customization within the Yocto build process (with a Distribution Package). | This article gives the main steps needed to add kernel customization within the Yocto build process (with a Distribution Package). | ||
==Pre- | ==Pre-requisites== | ||
You are already familiar with the Yocto build process and OpenSTLinux distribution. | You are already familiar with the Yocto build process and OpenSTLinux distribution. | ||
Line 24: | Line 20: | ||
* First, create (in your custom layer) a <name of kernel recipe>.bbappend file | * First, create (in your custom layer) a <name of kernel recipe>.bbappend file | ||
{{PC$}} touch ../meta-my-custo-layer/recipes-kernel/linux/<name of kernel recipe>.bbappend | {{PC$}}touch ../meta-my-custo-layer/recipes-kernel/linux/<name of kernel recipe>.bbappend | ||
===Adding kernel configuration modifications=== | ===Adding kernel configuration modifications=== | ||
* Identify all new configs you set or unset with: {{PC$}} bitbake <name of kernel recipe> -c menuconfig | * Identify all new configs you set or unset with: {{PC$}} bitbake <name of kernel recipe> -c menuconfig | ||
* Put them inside a new fragment file and copy the fragment here: | * Put them inside a new fragment file and copy the fragment here: | ||
{{PC$}} cp <custom-fragment>.config ../meta-my-custo-layer/recipes-kernel/linux/<name of kernel recipe>/<kernel version>/ | {{PC$}}cp <custom-fragment>.config ../meta-my-custo-layer/recipes-kernel/linux/<name of kernel recipe>/<kernel version>/ | ||
* Update accordingly <name of kernel recipe>.bbappend: | * Update accordingly <name of kernel recipe>.bbappend: | ||
# Needed to tell Yocto to search inside this path | |||
FILESEXTRAPATHS:prepend := "${THISDIR}/${PN}:" | |||
KERNEL_CONFIG_FRAGMENTS:append = " ${WORKDIR}/fragments/<kernel version>/<custom-fragment>.config" | |||
SRC_URI:append = " file://<kernel version>/<custom-fragment>.config;subdir=fragments " | |||
For the use case described in the [[How to cross-compile with the Distribution Package#modifying_kernel_configuration]] example, you should: | For the use case described in the [[How to cross-compile with the Distribution Package#modifying_kernel_configuration|modified the kernel configuration]] example, you should: | ||
* Create fragment-cma-size.config with the following line: | * Create fragment-cma-size.config with the following line: | ||
CONFIG_CMA_SIZE_MBYTES=256 | CONFIG_CMA_SIZE_MBYTES=256 | ||
* Copy fragment-cma-size.config to ../meta-my-custo-layer/recipes-kernel/linux/linux-stm32mp/ | * Copy fragment-cma-size.config to ../meta-my-custo-layer/recipes-kernel/linux/linux-stm32mp/<kernel version> | ||
* Update ../meta-my-custo-layer/recipes-kernel/linux/linux-stm32mp.bbappend accordingly by adding these lines: | * Update ../meta-my-custo-layer/recipes-kernel/linux/linux-stm32mp.bbappend accordingly by adding these lines: | ||
KERNEL_CONFIG_FRAGMENTS:append = " ${WORKDIR}/fragments/${LINUX_VERSION}/fragment-cma-size.config" | |||
SRC_URI:append = <nowiki>" file://${LINUX_VERSION}/fragment-cma-size.config;subdir=fragments"</nowiki> | |||
===Adding kernel driver or device tree modifications=== | ===Adding kernel driver or device tree modifications=== | ||
The example given below is associated with the STM32MP15 Evaluation board, but the method is independent of the board. | {{Info| The example given below is associated with the STM32MP15 Evaluation board, but the method is independent of the board. }} | ||
Once you have made the changes for the device tree in <build dir>/workspace/sources/<name of kernel recipe>/arch/arm/boot/dts/stm32mp157c-ed1.dts '''AND''', for built-in device driver in <build dir>/workspace/sources/<name of kernel recipe>/drivers/gpu/drm/stm/drv.c, you must: | Once you have made the changes for the device tree in <build dir>/workspace/sources/<name of kernel recipe>/arch/arm/boot/dts/stm32mp157c-ed1.dts '''AND''', for built-in device driver in <build dir>/workspace/sources/<name of kernel recipe>/drivers/gpu/drm/stm/drv.c, you must: | ||
* Create the corresponding patch files: | * Create the corresponding patch files: | ||
{{PC$}} cd <build dir>/workspace/sources/<name of kernel recipe>/ | {{PC$}}cd <build dir>/workspace/sources/<name of kernel recipe>/ | ||
{{PC$}} git format-patch -2 | {{PC$}}git format-patch -2 | ||
* Copy these patch files into the custom layer | * Copy these patch files into the custom layer | ||
{{PC$}} cp *.patch ../meta-my-custo-layer/recipes-kernel/linux/<name of kernel recipe>/<kernel version>/<kernel version>.<revision>/ | {{PC$}}cp *.patch ../meta-my-custo-layer/recipes-kernel/linux/<name of kernel recipe>/<kernel version>/<kernel version>.<revision>/ | ||
{{Warning|Patches are linked to a kernel version, which means that these patches are rebuilt if the kernel version changes, and copied to the according kernel version sub-folder}} | {{Warning|Patches are linked to a kernel version, which means that these patches are rebuilt if the kernel version changes, and copied to the according kernel version sub-folder}} | ||
* Update <name of kernel recipe>.bbappend accordingly: | * Update <name of kernel recipe>.bbappend accordingly: | ||
SRC_URI:append = " \ | |||
file:// | <nowiki>file://${LINUX_VERSION}/${LINUX_VERSION}.${LINUX_SUBVERSION}/0001-DT-leds-change.patch \ | ||
file://${LINUX_VERSION}/${LINUX_VERSION}.${LINUX_SUBVERSION}/0002-Driver-change.patch \</nowiki> | |||
" | " | ||
<noinclude> | |||
[[Category:How to customize software]] | |||
[[Category:Distribution Package]] | |||
{{PublicationRequestId | 8461 | 2018-08-29 | PhilipS}} | |||
</noinclude> |
Latest revision as of 14:47, 24 June 2024
1. Purpose of article
This article gives the main steps needed to add kernel customization within the Yocto build process (with a Distribution Package).
2. Pre-requisites
You are already familiar with the Yocto build process and OpenSTLinux distribution.
You have already created a customer layer (How to create a new open embedded layer) to update, for your own needs, the OpenSTLinux distribution.
We describe here what you must do once you have:
- modified the kernel configuration
- modified the Linux kernel device tree
- modified a built-in device driver
so that these modifications are taken into account in your build process.
3. Adding kernel customization (including Linux kernel device tree, configuration, driver modification)
- First, create (in your custom layer) a <name of kernel recipe>.bbappend file
Template:PC$touch ../meta-my-custo-layer/recipes-kernel/linux/<name of kernel recipe>.bbappend
3.1. Adding kernel configuration modifications
- Identify all new configs you set or unset with: Template:PC$ bitbake <name of kernel recipe> -c menuconfig
- Put them inside a new fragment file and copy the fragment here:
Template:PC$cp <custom-fragment>.config ../meta-my-custo-layer/recipes-kernel/linux/<name of kernel recipe>/<kernel version>/
- Update accordingly <name of kernel recipe>.bbappend:
# Needed to tell Yocto to search inside this path
FILESEXTRAPATHS:prepend := "${THISDIR}/${PN}:"
KERNEL_CONFIG_FRAGMENTS:append = " ${WORKDIR}/fragments/<kernel version>/<custom-fragment>.config"
SRC_URI:append = " file://<kernel version>/<custom-fragment>.config;subdir=fragments "
For the use case described in the modified the kernel configuration example, you should:
- Create fragment-cma-size.config with the following line:
CONFIG_CMA_SIZE_MBYTES=256
- Copy fragment-cma-size.config to ../meta-my-custo-layer/recipes-kernel/linux/linux-stm32mp/<kernel version>
- Update ../meta-my-custo-layer/recipes-kernel/linux/linux-stm32mp.bbappend accordingly by adding these lines:
KERNEL_CONFIG_FRAGMENTS:append = " ${WORKDIR}/fragments/${LINUX_VERSION}/fragment-cma-size.config"
SRC_URI:append = " file://${LINUX_VERSION}/fragment-cma-size.config;subdir=fragments"
3.2. Adding kernel driver or device tree modifications
![]() |
The example given below is associated with the STM32MP15 Evaluation board, but the method is independent of the board. |
Once you have made the changes for the device tree in <build dir>/workspace/sources/<name of kernel recipe>/arch/arm/boot/dts/stm32mp157c-ed1.dts AND, for built-in device driver in <build dir>/workspace/sources/<name of kernel recipe>/drivers/gpu/drm/stm/drv.c, you must:
- Create the corresponding patch files:
Template:PC$cd <build dir>/workspace/sources/<name of kernel recipe>/ Template:PC$git format-patch -2
- Copy these patch files into the custom layer
Template:PC$cp *.patch ../meta-my-custo-layer/recipes-kernel/linux/<name of kernel recipe>/<kernel version>/<kernel version>.<revision>/
- Update <name of kernel recipe>.bbappend accordingly:
SRC_URI:append = " \
file://${LINUX_VERSION}/${LINUX_VERSION}.${LINUX_SUBVERSION}/0001-DT-leds-change.patch \
file://${LINUX_VERSION}/${LINUX_VERSION}.${LINUX_SUBVERSION}/0002-Driver-change.patch \
"