[PATCH v3 00/19] Migration to using binman for bootloader

[Manorit Chawdhry]

On 09:57-20230503, Tom Rini wrote:
> On Wed, May 03, 2023 at 12:57:13PM +0530, Neha Malcom Francis wrote:
> > Hi Tom
> > 
> > On 27/04/23 04:07, Tom Rini wrote:
> > > On Fri, Apr 21, 2023 at 06:01:44PM +0530, Neha Malcom Francis wrote:
> > > 
> > > > This series aims to eliminate the use of additional custom repositories
> > > > such as k3-image-gen (K3 Image Generation) repo and core-secdev-k3 (K3
> > > > Security Development Tools) that was plumbed into the U-Boot build flow
> > > > to generate boot images for TI K3 platform devices. And instead, we move
> > > > towards using binman that aligns better with the community standard build
> > > > flow.
> > > > 
> > > > This series uses binman for all K3 platforms supported on U-Boot currently;
> > > > both HS (High Security, both SE and FS) and GP (General Purpose) devices.
> > > > 
> > > > Background on using k3-image-gen:
> > > > 	* TI K3 devices require a SYSFW (System Firmware) image consisting
> > > > 	of a signed system firmware image and board configuration binaries,
> > > > 	this is needed to bring up system firmware during U-Boot R5 SPL
> > > > 	startup.
> > > > 	* Board configuration data contain board-specific information
> > > > 	such as resource management, power management and security.
> > > > 
> > > > Background on using core-secdev-k3:
> > > > 	* Contains resources to sign x509 certificates for HS devices
> > > > 
> > > > Series intends to use binman to take over the packaging and signing for
> > > > the R5 bootloader images tiboot3.bin (and sysfw.itb, for non-combined
> > > > boot flow) instead of k3-image-gen.
> > > > 
> > > > Series also packages the A72/A53 bootloader images (tispl.bin and
> > > > u-boot.img) using ATF, OPTEE and DM (Device Manager)
> > > 
> > > So, next up is fixing this in CI. After taking Andrew's patch to fix the
> > > typedef issue, and after my patches to ensure we can get
> > > pyyaml/jsonschema for python, there's problems still:
> > 
> > 
> > Thanks for checking this! Couple things:
> > 
> > > Over at https://source.denx.de/u-boot/u-boot/-/jobs/617966:
> > > binman: Filename 'spl/dts/k3-am68-sk-base-board.dtb' not found in input
> > > path (.,/builds/u-boot/u-boot,board/ti/j721s2,arch/arm/dts)
> > > (cwd='/tmp/.bm-work/j721s2_hs_evm_a72')
> > 
> > 1. This is dependent on the patch merging J721S2 HS and GP configs [1].
> > However it has been reverted on -next, seen in the same thread.
> 
> OK.  I'm not sure the priority order here. I would like to see this
> series get in first, and get everything else rebased on top of it.
> 
> -- 

Hi Tom, I aligned with Neha on the order which will be easier for us
both in terms of handling both the series,

 1. J721S2 and J7200 HS defconfig merge
  ( https://lore.kernel.org/r/20230405-j721s2-hs-evm-upstream-v2-0-c0f10a410e07@ti.com )
 2. Binman can go after that
 3. J721E HS defconfig patches
  ( https://lore.kernel.org/u-boot/20230324-j721e-upstream-hs-v6-0-5aa43a4817a9@ti.com )
  Will re-roll once binman is merged

Thanks and regards,
Manorit

> Tom