From: Alper Nebi Yasak <alpernebiyasak@gmail.com>
To: Neha Malcom Francis <n-francis@ti.com>
Cc: u-boot@lists.denx.de, afd@ti.com, trini@konsulko.com,
a-govindraju@ti.com, vigneshr@ti.com, rogerq@kernel.org
Subject: Re: [PATCH RFC v3 00/11] Integration of tiboot3.bin, sysfw.itb and
Date: Fri, 1 Jul 2022 22:07:12 +0300 [thread overview]
Message-ID: <357122e7-b20d-dd94-05ba-7e14b3e34c4a@gmail.com> (raw)
In-Reply-To: <20220615064804.29553-1-n-francis@ti.com>
On 15/06/2022 09:47, Neha Malcom Francis wrote:
> [...]
>
> Neha Malcom Francis (11):
> j721e_evm: schema: yaml: Add general schema and J721E board config
> files
> ti: tools: config: Add board config class to generate config binaries
> ti: etype: sysfw: Add entry type for sysfw
> ti: etype: dm: Add entry type for TI DM
> ti: etype: x509: Add etype for x509 certificate for K3 devices
These three would be better as 'binman: ...", sorry for not being clear
about that.
> ti: sysfw: Add support for packaging sysfw.itb
> ti: j721e: Exclude makefile tiboot3.bin target for J721E
> ti: j721e: Exclude makefile tispl.bin target for J721E
> ti: dtsi: j721e: Use binman to package sysfw.itb and tiboot3.bin
> ti: dtsi: j721e: Use binman to package tispl.bin
> ci: world_build: test: Add requirements.txt
prev parent reply other threads:[~2022-07-01 19:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 6:47 [PATCH RFC v3 00/11] Integration of tiboot3.bin, sysfw.itb and Neha Malcom Francis
2022-06-15 6:47 ` [PATCH RFC v3 01/11] j721e_evm: schema: yaml: Add general schema and J721E board config files Neha Malcom Francis
2022-06-15 6:47 ` [PATCH RFC v3 02/11] ti: tools: config: Add board config class to generate config binaries Neha Malcom Francis
2022-07-01 19:07 ` Alper Nebi Yasak
2022-06-15 6:47 ` [PATCH RFC v3 03/11] ti: etype: sysfw: Add entry type for sysfw Neha Malcom Francis
2022-06-15 15:37 ` Andrew Davis
2022-06-16 11:23 ` Neha Malcom Francis
2022-07-01 19:07 ` Alper Nebi Yasak
2022-06-15 6:47 ` [PATCH RFC v3 04/11] ti: etype: dm: Add entry type for TI DM Neha Malcom Francis
2022-07-01 19:07 ` Alper Nebi Yasak
2022-06-15 6:47 ` [PATCH RFC v3 05/11] ti: etype: x509: Add etype for x509 certificate for K3 devices Neha Malcom Francis
2022-07-01 19:07 ` Alper Nebi Yasak
2022-06-15 6:47 ` [PATCH RFC v3 06/11] ti: sysfw: Add support for packaging sysfw.itb Neha Malcom Francis
2022-06-15 6:48 ` [PATCH RFC v3 07/11] ti: j721e: Exclude makefile tiboot3.bin target for J721E Neha Malcom Francis
2022-06-15 6:48 ` [PATCH RFC v3 08/11] ti: j721e: Exclude makefile tispl.bin " Neha Malcom Francis
2022-06-15 13:44 ` Roger Quadros
2022-06-16 11:09 ` Neha Malcom Francis
2022-06-15 6:48 ` [PATCH RFC v3 09/11] ti: dtsi: j721e: Use binman to package sysfw.itb and tiboot3.bin Neha Malcom Francis
2022-07-01 19:07 ` Alper Nebi Yasak
2022-06-15 6:48 ` [PATCH RFC v3 10/11] ti: dtsi: j721e: Use binman to package tispl.bin Neha Malcom Francis
2022-06-15 14:25 ` Roger Quadros
2022-06-15 14:29 ` Roger Quadros
2022-07-01 19:08 ` Alper Nebi Yasak
2022-06-15 6:48 ` [PATCH RFC v3 11/11] ci: world_build: test: Add requirements.txt Neha Malcom Francis
2022-07-01 19:09 ` Alper Nebi Yasak
2022-07-01 19:07 ` Alper Nebi Yasak [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=357122e7-b20d-dd94-05ba-7e14b3e34c4a@gmail.com \
--to=alpernebiyasak@gmail.com \
--cc=a-govindraju@ti.com \
--cc=afd@ti.com \
--cc=n-francis@ti.com \
--cc=rogerq@kernel.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