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 8AF0CC433EF for ; Tue, 31 May 2022 05:06:30 +0000 (UTC) Received: from h2850616.stratoserver.net (localhost [IPv6:::1]) by phobos.denx.de (Postfix) with ESMTP id 250218426A; Tue, 31 May 2022 07:06:28 +0200 (CEST) Authentication-Results: phobos.denx.de; dmarc=pass (p=none dis=none) header.from=kernel.org Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=u-boot-bounces@lists.denx.de Authentication-Results: phobos.denx.de; dkim=pass (2048-bit key; unprotected) header.d=kernel.org header.i=@kernel.org header.b="uobjR8cD"; dkim-atps=neutral Received: by phobos.denx.de (Postfix, from userid 109) id 2119484282; Tue, 31 May 2022 07:06:27 +0200 (CEST) Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) (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 5C573840D8 for ; Tue, 31 May 2022 07:06:24 +0200 (CEST) Authentication-Results: phobos.denx.de; dmarc=pass (p=none dis=none) header.from=kernel.org Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=rogerq@kernel.org Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id AD8FC61181; Tue, 31 May 2022 05:06:22 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 0FD8FC385A9; Tue, 31 May 2022 05:06:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1653973582; bh=f0Pw6dQAsqVa+dSPejRuvEJo7E/NX8uiW3tv0Bhb9Pc=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=uobjR8cDpsw6PmsQB4WqP8K+9eYnDkEmanJADIWr2Xf0SDfrBl9TKh+f7IVgTzQlh VmVRUF6+UNmFPXGf01cN0v4ChHkNTiMrvx5GQsOLbfknllU71AsU70HZnIEXsl9Xek Fm8F/Wtio+fMxxzTRfKRT5A/oWqeVY7qCOTigZCelhAY0f7VDKYhmLRjt3/u7ZvRpd YCNBqTPUAaWqXIM3u1F5Htxe9ovEeFbkVn+FV1pDCnL+uM2T/gLlIYN7h9TICtETKP rnuEiseSogbYyjISzweei9TK7fgUYEPbXZMUfGsMA1JeFXWAN+UvGXFGWnlxkC3YTS yBbfK6QBMpchQ== Message-ID: Date: Tue, 31 May 2022 08:06:16 +0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0 Subject: Re: [u-boot PATCH 3/3] k3-am642-evm-u-boot: Use binman to generate u-boot.img and tispl.bin Content-Language: en-US To: Alper Nebi Yasak , "Andrew F. Davis" , Nishanth Menon Cc: sjg@chromium.org, vigneshr@ti.com, praneeth@ti.com, u-boot@lists.denx.de, Tom Rini , n-francis@ti.com References: <20220509072936.12899-1-rogerq@kernel.org> <20220509072936.12899-4-rogerq@kernel.org> <3dec7c74-e486-79da-e4e7-cad6205471a5@ti.com> <28124041-81c8-265f-5f54-57a7fb7562e4@ti.com> <3d5690e0-d77b-4592-dd55-0952d849a84b@kernel.org> <20220526141529.GV13239@bill-the-cat> <76474ded-a782-f491-eac6-ece3c5f4a7da@gmail.com> From: Roger Quadros In-Reply-To: <76474ded-a782-f491-eac6-ece3c5f4a7da@gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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.5 at phobos.denx.de X-Virus-Status: Clean Hi, On 27/05/2022 20:50, Alper Nebi Yasak wrote: > On 26/05/2022 17:15, Tom Rini wrote: >> On Thu, May 26, 2022 at 10:28:45AM +0300, Roger Quadros wrote: >>> Any thoughts on how to get the new ti-secure etype work with atf-bl31 and >>> tee-os etypes so that it can take the data output of those entries and create >>> a signed binary with filenames from those entries or atf-bl31-path and >>> tee-os-path? >>> >>> Can something like this work? >>> >>> ti-secure { >>> atf-bl31 { >>> filename = "bl31.bin"; >>> }; >>> } >>> >>> We could probably get rid of filename property from ti-secure etype and use >>> blob for regular files. >>> >>> ti-secure { >>> blob { >>> filename = "somefile.ext"; >>> } >>> } > > 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. > > > Sorry I couldn't look at either series yet, but I see mentions of > k3_fit_atf.sh, so let me point out another series [1][2] that might also > interest you: > > [1] [RESEND, RFC 0/8] Integration of sysfw and tispl with U-Boot > https://lore.kernel.org/u-boot/20220406122919.6104-1-n-francis@ti.com/ > > [2] [PATCH RFC v2 00/11] Integration of sysfw, tispl and tiboot3 > https://lore.kernel.org/u-boot/20220506043759.8193-1-n-francis@ti.com/ Thanks for this pointer. I will review those patches and see how we can consolidate. cheers, -roger