From: Sascha Hauer <s.hauer@pengutronix.de>
To: BAREBOX <barebox@lists.infradead.org>,
Michael Tretter <m.tretter@pengutronix.de>
Subject: Re: [PATCH] Documentation: rk35xx: add secure boot documentation
Date: Tue, 12 May 2026 08:25:02 +0200 [thread overview]
Message-ID: <177856710257.351974.9661061617063300627.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20260511-rockchip-secure-boot-doc-v1-1-b4339a0d007f@pengutronix.de>
On Mon, 11 May 2026 17:53:50 +0200, Michael Tretter wrote:
> While barebox supports secure boot on rk3588, user documentation how to
> sign images and enable secure boot is still lacking.
>
> Add this documentation, now.
>
> While at it, add some documentation for the Rockchip image header, too,
> to explain how the signature guarantees the integrity and authenticity
> of the included barebox image.
>
> [...]
Applied, thanks!
[1/1] Documentation: rk35xx: add secure boot documentation
https://git.pengutronix.de/cgit/barebox/commit/?id=cbd846c548b3 (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2026-05-12 6:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 15:53 Michael Tretter
2026-05-12 6:25 ` Sascha Hauer [this message]
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=177856710257.351974.9661061617063300627.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=m.tretter@pengutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox