From: Alper Nebi Yasak <alpernebiyasak@gmail.com>
To: Andrew Davis <afd@ti.com>
Cc: sjg@chromium.org, vigneshr@ti.com, praneeth@ti.com,
u-boot@lists.denx.de, Tom Rini <trini@konsulko.com>,
n-francis@ti.com, Roger Quadros <rogerq@kernel.org>,
Nishanth Menon <nm@ti.com>
Subject: Re: [u-boot PATCH 3/3] k3-am642-evm-u-boot: Use binman to generate u-boot.img and tispl.bin
Date: Thu, 2 Jun 2022 20:34:04 +0300 [thread overview]
Message-ID: <17ae7b7b-8e7e-7261-6776-4b3b705754de@gmail.com> (raw)
In-Reply-To: <c7d93de3-f95b-3faf-0ae2-bd8b033d0c47@ti.com>
On 31/05/2022 17:15, Andrew Davis wrote:
> On 5/31/22 12:06 AM, Roger Quadros wrote:
>> On 27/05/2022 20:50, Alper Nebi Yasak wrote:
>>> This would definitely work, see etype/mkimage.py for example. I'd prefer
>>> to know the file-format details (and maybe replicate them in binman) if
>>> you could afford to publish them, though...
>>
>> This is a question to Nishanth/Andrew.
>
> What file format are we talking about here? If it is the signed format,
> it's an attached x509 certificate, that is already published [0] and
> the tools to make it are public [1].
Thanks, I meant this. I saw 'secure-binary-image.sh' in the first patch,
which lead me to 'doc/README.ti-secure', which mentions NDA and logins,
so I stopped looking there.
> There is also an effort to replicate some of this in binman too [2].
>
> Thanks,
> Andrew
>
> [0] https://software-dl.ti.com/tisci/esd/latest/2_tisci_msgs/security/sec_cert_format.html
> [1] https://git.ti.com/cgit/security-development-tools/core-secdev-k3
> [2] https://lore.kernel.org/all/20220510200511.GK3901321@bill-the-cat/T/
next prev parent reply other threads:[~2022-06-02 17:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 7:29 [u-boot PATCH 0/3] k3-am642-evm-u-boot: Use binman to generate u-boot.img and tispl.bin Roger Quadros
2022-05-09 7:29 ` [u-boot PATCH 1/3] tools: binman: add ti-secure entry type Roger Quadros
2022-05-09 7:29 ` [u-boot PATCH 2/3] tools/fdtgrep: Include __symbols__ table Roger Quadros
2022-06-10 13:42 ` Tom Rini
2022-06-11 8:43 ` Roger Quadros
2022-06-11 13:26 ` Tom Rini
2022-05-09 7:29 ` [u-boot PATCH 3/3] k3-am642-evm-u-boot: Use binman to generate u-boot.img and tispl.bin Roger Quadros
2022-05-24 22:03 ` Andrew Davis
2022-05-25 8:30 ` Roger Quadros
2022-05-25 15:14 ` Andrew Davis
2022-05-26 7:28 ` Roger Quadros
2022-05-26 14:15 ` Tom Rini
2022-05-27 17:50 ` Alper Nebi Yasak
2022-05-31 5:06 ` Roger Quadros
2022-05-31 14:15 ` Andrew Davis
2022-06-02 17:34 ` Alper Nebi Yasak [this message]
2022-05-09 13:39 ` [u-boot PATCH 0/3] " Tom Rini
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=17ae7b7b-8e7e-7261-6776-4b3b705754de@gmail.com \
--to=alpernebiyasak@gmail.com \
--cc=afd@ti.com \
--cc=n-francis@ti.com \
--cc=nm@ti.com \
--cc=praneeth@ti.com \
--cc=rogerq@kernel.org \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.com \
/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