From: Trevor Woerner <twoerner@gmail.com>
To: yocto-patches@lists.yoctoproject.org
Subject: [meta-rockchip][PATCH v2] linux-torvalds-next: add rauc config
Date: Wed, 31 Jul 2024 23:05:06 -0400 [thread overview]
Message-ID: <20240801030506.8626-1-twoerner@gmail.com> (raw)
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 <twoerner@gmail.com>
---
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
diff --git a/dynamic-layers/rk-rauc-demo/recipes-kernel/linux/linux-torvalds-next_%.bbappend b/dynamic-layers/rk-rauc-demo/recipes-kernel/linux/linux-torvalds-next_%.bbappend
new file mode 100644
index 000000000000..6c75cb1338e7
--- /dev/null
+++ b/dynamic-layers/rk-rauc-demo/recipes-kernel/linux/linux-torvalds-next_%.bbappend
@@ -0,0 +1 @@
+include ${@ 'recipes-kernel/linux/linux-yocto_rauc.inc' if bb.utils.to_boolean(d.getVar('RK_RAUC_DEMO'), False) else ''}
--
2.44.0.478.g7774cfed6261
next reply other threads:[~2024-08-01 3:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7208a42b-4309-4216-ab64-16a5a82eced8.a73bd9c8-8cbe-42e2-876b-4c548d837fba.f860893f-53ad-4466-9b34-7b39f9829994@emailsignatures365.codetwo.com>
2024-08-01 3:05 ` Trevor Woerner [this message]
2024-08-01 9:03 ` [yocto-patches] [meta-rockchip][PATCH v2] linux-torvalds-next: add rauc config Quentin Schulz
2024-08-01 12:03 ` Trevor Woerner
2024-08-01 12:02 ` Trevor Woerner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240801030506.8626-1-twoerner@gmail.com \
--to=twoerner@gmail.com \
--cc=yocto-patches@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.