From: Roman Kopytin <Roman.Kopytin@kaspersky.com>
To: "u-boot@lists.denx.de" <u-boot@lists.denx.de>
Cc: Simon Glass <sjg@chromium.org>
Subject: U-boot
Date: Fri, 30 Jul 2021 17:34:30 +0000 [thread overview]
Message-ID: <94d75c521aed46dbb54a8275be2f529e@kaspersky.com> (raw)
In-Reply-To: <CAPnjgZ2BSCMcN=-3Vr4wcgZgtB5ExdAxDPE2yfQvT5WJTVajbg@mail.gmail.com>
Hello, dear U-boot team
I have question about your old feature: U-boot patch for adding of the public key to dtb file.
https://patchwork.ozlabs.org/project/uboot/patch/1363650725-30459-37-git-send-email-sjg%40chromium.org/
I can’t understand, can we work only with public key? Why do we need to have private key for adding step?
In documentation it is not very clear for me.
Thanks a lot.
next parent reply other threads:[~2021-07-30 17:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <25743c08c4b34f9791e39e687399f802@kaspersky.com>
[not found] ` <CAPnjgZ2BSCMcN=-3Vr4wcgZgtB5ExdAxDPE2yfQvT5WJTVajbg@mail.gmail.com>
2021-07-30 17:34 ` Roman Kopytin [this message]
2021-07-30 17:50 ` U-boot Michael Nazzareno Trimarchi
2021-07-31 3:34 ` U-boot Roman Kopytin
2021-07-31 6:51 ` U-boot Thomas Perrot
2021-07-31 8:26 ` U-boot Roman Kopytin
2021-07-31 16:59 ` U-boot Simon Glass
2021-08-02 9:00 ` U-boot Rasmus Villemoes
2021-08-02 9:25 ` U-boot Roman Kopytin
2021-08-02 9:37 ` U-boot Rasmus Villemoes
2021-08-02 9:55 ` U-boot Roman Kopytin
2021-08-02 11:08 ` U-boot Rasmus Villemoes
2021-08-02 11:18 ` U-boot Roman Kopytin
2021-08-02 12:35 ` U-boot Roman Kopytin
2021-08-02 19:20 ` U-boot Simon Glass
[not found] ` <4ba7d9814f544d56b32589e86a5e0617@kaspersky.com>
2021-11-10 19:37 ` U-boot Simon Glass
2024-10-22 10:05 u-boot Dharshini V
-- strict thread matches above, loose matches on Subject: below --
2026-02-16 10:31 U-Boot Shakhrukh Shakirov
2026-02-16 16:37 ` U-Boot Heinrich Schuchardt
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=94d75c521aed46dbb54a8275be2f529e@kaspersky.com \
--to=roman.kopytin@kaspersky.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.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