From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailout4.zoneedit.com (mailout4.zoneedit.com [64.68.198.64]) by mx.groups.io with SMTP id smtpd.web11.2953.1592855290194862082 for ; Mon, 22 Jun 2020 12:48:10 -0700 Authentication-Results: mx.groups.io; dkim=missing; spf=none, err=permanent DNS error (domain: denix.org, ip: 64.68.198.64, mailfrom: denis@denix.org) Received: from localhost (localhost [127.0.0.1]) by mailout4.zoneedit.com (Postfix) with ESMTP id 87DDA40BA1; Mon, 22 Jun 2020 19:48:09 +0000 (UTC) Received: from mailout4.zoneedit.com ([127.0.0.1]) by localhost (zmo14-pco.easydns.vpn [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Af89OIuRyXXv; Mon, 22 Jun 2020 19:48:09 +0000 (UTC) Received: from mail.denix.org (pool-100-15-86-127.washdc.fios.verizon.net [100.15.86.127]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout4.zoneedit.com (Postfix) with ESMTPSA id 5ADE740B9F; Mon, 22 Jun 2020 19:48:03 +0000 (UTC) Received: by mail.denix.org (Postfix, from userid 1000) id B8A29173217; Mon, 22 Jun 2020 15:48:02 -0400 (EDT) Date: Mon, 22 Jun 2020 15:48:02 -0400 From: "Denys Dmytriyenko" To: Ross Burton Cc: Gabor Abonyi , meta-arm@lists.yoctoproject.org, nd@arm.com Subject: Re: [meta-arm] [PATCH 4/6] arm: trusted-firmware-m: Add recipe Message-ID: <20200622194802.GI17660@denix.org> References: <20200622071401.2570-1-gabor.abonyi@arm.com> <20200622071401.2570-5-gabor.abonyi@arm.com> <20200622184355.GH17660@denix.org> MIME-Version: 1.0 In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Jun 22, 2020 at 08:29:02PM +0100, Ross Burton wrote: > On Mon, 22 Jun 2020 at 19:44, Denys Dmytriyenko wrote: > > > Looks like it's time to start that multiconfig experiment where we > > > just build another cross compiler inside Yocto. > > > > You can check meta-ti - our K3 platforms have Aarch64 Cortex-A cores and Armv7 > > Cortex-R cores, so meta-ti now uses multiconfig to build 2 cross compilers and > > use those for corresponding components. TF-M sounds like a perfect use case > > for that, as well. > > Awesome for doing it already. Does it work well? Works quite well, as long as you can express relations between multiconfigs with build-time dependency and hand-off via DEPLOY_DIR. Works quite well if you only need to do firmwares or bootloaders for those extra cores. You can even have those packaged into a partition in your wic image. But more complex use cases, which would require run-time dependencies, like packaging an SDK with both cross-compilers and sysroots, aren't supported yet. -- Denys