From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from phobos.denx.de (phobos.denx.de [85.214.62.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 313FBC77B7A for ; Tue, 16 May 2023 04:59:39 +0000 (UTC) Received: from h2850616.stratoserver.net (localhost [IPv6:::1]) by phobos.denx.de (Postfix) with ESMTP id 60A41865B5; Tue, 16 May 2023 06:59:37 +0200 (CEST) Authentication-Results: phobos.denx.de; dmarc=pass (p=quarantine dis=none) header.from=ti.com Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=u-boot-bounces@lists.denx.de Authentication-Results: phobos.denx.de; dkim=pass (1024-bit key; unprotected) header.d=ti.com header.i=@ti.com header.b="ZQi51mFx"; dkim-atps=neutral Received: by phobos.denx.de (Postfix, from userid 109) id 3635B865FB; Tue, 16 May 2023 06:59:35 +0200 (CEST) Received: from fllv0016.ext.ti.com (fllv0016.ext.ti.com [198.47.19.142]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by phobos.denx.de (Postfix) with ESMTPS id 73BAC860B5 for ; Tue, 16 May 2023 06:59:32 +0200 (CEST) Authentication-Results: phobos.denx.de; dmarc=pass (p=quarantine dis=none) header.from=ti.com Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=n-francis@ti.com Received: from fllv0035.itg.ti.com ([10.64.41.0]) by fllv0016.ext.ti.com (8.15.2/8.15.2) with ESMTP id 34G4xNR8083898; Mon, 15 May 2023 23:59:23 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1684213163; bh=4rCOBdDqxZxl9uy4sIL2FwYX9iUQ8i4HtjBUeOHxF1c=; h=Date:Subject:To:CC:References:From:In-Reply-To; b=ZQi51mFxEqEgxSAmTb3hTGefjVti+zCp1e8Dbht4Y1d41EUZ96EgGacBfq5eZxBdo prBvT40vQr6n1pUb54FIJ5+3m2hhJu0NVtFl+rTxj3YdKih9Vil3mW9ZA3cjMGWnx2 mZrXsdA3tYidhQaEewPNgOw+esKzznxHp5gViwXk= Received: from DFLE114.ent.ti.com (dfle114.ent.ti.com [10.64.6.35]) by fllv0035.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 34G4xN60044184 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Mon, 15 May 2023 23:59:23 -0500 Received: from DFLE115.ent.ti.com (10.64.6.36) by DFLE114.ent.ti.com (10.64.6.35) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.23; Mon, 15 May 2023 23:59:23 -0500 Received: from fllv0040.itg.ti.com (10.64.41.20) by DFLE115.ent.ti.com (10.64.6.36) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.23 via Frontend Transport; Mon, 15 May 2023 23:59:22 -0500 Received: from [172.24.145.195] (ileaxei01-snat2.itg.ti.com [10.180.69.6]) by fllv0040.itg.ti.com (8.15.2/8.15.2) with ESMTP id 34G4xJIY059732; Mon, 15 May 2023 23:59:19 -0500 Message-ID: Date: Tue, 16 May 2023 10:29:18 +0530 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0 Subject: Re: [PATCH v3 00/19] Migration to using binman for bootloader To: Manorit Chawdhry , Tom Rini , Vignesh Raghavendra CC: , , , , , , , , References: <20230421123203.1315330-1-n-francis@ti.com> <20230426223750.GA643785@bill-the-cat> <20230503135755.GZ1134230@bill-the-cat> <20230504054005.bvju3qgrx3cnksnl@ula0497581> Content-Language: en-US From: Neha Malcom Francis In-Reply-To: <20230504054005.bvju3qgrx3cnksnl@ula0497581> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 X-BeenThere: u-boot@lists.denx.de X-Mailman-Version: 2.1.39 Precedence: list List-Id: U-Boot discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: u-boot-bounces@lists.denx.de Sender: "U-Boot" X-Virus-Scanned: clamav-milter 0.103.8 at phobos.denx.de X-Virus-Status: Clean Hi Tom On 04/05/23 11:10, Manorit Chawdhry wrote: > 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 > > Bringing this back after yesterday's discussion. J7 HS is a definite regression and I think this should be taken into 2023.07 and not wait for binman in 2023.10. Rebasing binman on top of the J7 HS fix patches is very minimal effort. -- Thanking You Neha Malcom Francis