linux-torvalds-next: add rauc config
PATCH v2 1/1 linux-torvalds-next: add rauc config
The kernel needs a couple configuration tweaks in order to work with RAUC, and the default upstream kernel recipes already have this built-in due to meta-rauc. The non-upstream, one-off kernel required to support the Radxa Zero 3{e|w} boards (linux-torvalds-next) needs a similar tweak.
---
v2 changes:
- use a different, more efficient, way to do the same thing without having to repeat (and keep in sync) the cfg itself
--- .../recipes-kernel/linux/linux-torvalds-next_%.bbappend | 1 + 1 file changed, 1 insertion(+) create mode 100644 dynamic-layers/rk-rauc-demo/recipes-kernel/linux/linux-torvalds-next_%.bbappend
dynamic-layers/rk-rauc-demo/recipes-kernel/linux/linux-torvalds-next_%.bbappend new file +1 -0
@@ -0,0 +1 @@ +include ${@ 'recipes-kernel/linux/linux-yocto_rauc.inc' if bb.utils.to_boolean(d.getVar('RK_RAUC_DEMO'), False) else ''}
Signature · 1 line
2.44.0.478.g7774cfed6261
Hi Trevor,
Mit freundlichen Grüßen / Best regards / 此致 敬礼
Quentin Schulz
Senior Software EngineerCherry Embedded Solutions GmbH [email protected] embedded.cherry.deSeestadtstraße 27, 1220 Vienna, Austria
Quoted 21 lines · Trevor Woerner via lists.yoctoproject.org
The kernel needs a couple configuration tweaks in order to work with RAUC, and the default upstream kernel recipes already have this built-in due to meta-rauc. The non-upstream, one-off kernel required to support the Radxa Zero 3{e|w} boards (linux-torvalds-next) needs a similar tweak.
Signed-off-by Trevor Woerner <[email protected]>---
v2 changes:
- use a different, more efficient, way to do the same thing without having to repeat (and keep in sync) the cfg itself
---
.../recipes-kernel/linux/linux-torvalds-next_%.bbappend | 1 +1 file changed, 1 insertion(+)create mode 100644 dynamic-layers/rk-rauc-demo/recipes-kernel/linux/linux-torvalds-next_%.bbappend
dynamic-layers/rk-rauc-demo/recipes-kernel/linux/linux-torvalds-next_%.bbappend new file +0
-0
dynamic-layers/rk-rauc-demo/recipes-kernel/linux/linux-torvalds-next_%.bbappend line 1
Quoted 1 line
dynamic-layers/rk-rauc-demo/recipes-kernel/linux/linux-torvalds-next_%.bbappend new file +1
-0@@ -0,0 +1 @@ +include ${@ 'recipes-kernel/linux/linux-yocto_rauc.inc' if bb.utils.to_boolean(d.getVar('RK_RAUC_DEMO'), False) else ''}
Considering this bbappend is only added if meta-rauc is present, which guarantees the presence of recipes-kernel/linux/linux-yocto_rauc.inc, we could have used require here.
Thanks!
Quentin
Trevor Woerner
AppliedQuoted 6 lines · Trevor Woerner
The kernel needs a couple configuration tweaks in order to work with RAUC, and the default upstream kernel recipes already have this built-in due to meta-rauc. The non-upstream, one-off kernel required to support the Radxa Zero 3{e|w} boards (linux-torvalds-next) needs a similar tweak.
Signed-off-by Trevor Woerner <[email protected]>
Quoted 8 lines
---
v2 changes:
- use a different, more efficient, way to do the same thing without having to repeat (and keep in sync) the cfg itself--- .../recipes-kernel/linux/linux-torvalds-next_%.bbappend | 1 + 1 file changed, 1 insertion(+) create mode 100644 dynamic-layers/rk-rauc-demo/recipes-kernel/linux/linux-torvalds-next_%.bbappend
Applied to meta-rockchip, master branch, using "require" instead of "include". Thanks!
Quoted 6 lines · Quentin Schulz via lists.yoctoproject.org
Hi Trevor,
Considering this bbappend is only added if meta-rauc is present, which guarantees the presence of recipes-kernel/linux/linux-yocto_rauc.inc, we could have used require here.Reviewed-by Quentin Schulz <[email protected]>
Sounds good, thanks for the review!