Re: [PATCH RFC v2 00/11] Integration of sysfw, tispl and tiboot3

2022-05-31 Thread Neha Malcom Francis
Hi Roger, On 31/05/22 13:51, Roger Quadros wrote: Hi, On 06/05/2022 07:37, Neha Malcom Francis wrote: Devices that belong to the K3 architecture require SYSFW which is a FIT image consisting of a signed system firmware image and board config binaries. Board config binaries are needed to bring

Re: [PATCH RFC v2 00/11] Integration of sysfw, tispl and tiboot3

2022-05-31 Thread Roger Quadros
Hi, On 06/05/2022 07:37, Neha Malcom Francis wrote: > Devices that belong to the K3 architecture require SYSFW which is a FIT > image consisting of a signed system firmware image and board config > binaries. > > Board config binaries are needed to bring up SYSFW during U-Boot SPL > startup. The b

Re: [PATCH RFC v2 00/11] Integration of sysfw, tispl and tiboot3

2022-05-11 Thread Alper Nebi Yasak
On 10/05/2022 23:05, Tom Rini wrote: > Adding the other binman maintainer.. Thanks. I haven't been able to focus on anything for a while. I'll try to review the few series that have accumulated, maybe can manage this week or so if things go well. Just wanted to send an update.

Re: [PATCH RFC v2 00/11] Integration of sysfw, tispl and tiboot3

2022-05-10 Thread Tom Rini
On Fri, May 06, 2022 at 10:07:48AM +0530, Neha Malcom Francis wrote: > Devices that belong to the K3 architecture require SYSFW which is a FIT > image consisting of a signed system firmware image and board config > binaries. > > Board config binaries are needed to bring up SYSFW during U-Boot SPL

[PATCH RFC v2 00/11] Integration of sysfw, tispl and tiboot3

2022-05-05 Thread Neha Malcom Francis
Devices that belong to the K3 architecture require SYSFW which is a FIT image consisting of a signed system firmware image and board config binaries. Board config binaries are needed to bring up SYSFW during U-Boot SPL startup. The board config data is given in YAML as input. These board configs c