From: "Denys Dmytriyenko" <denis@denix.org>
To: Ross Burton <ross@burtonini.com>
Cc: Gabor Abonyi <gabor.abonyi@arm.com>,
meta-arm@lists.yoctoproject.org, nd@arm.com
Subject: Re: [meta-arm] [PATCH 4/6] arm: trusted-firmware-m: Add recipe
Date: Mon, 22 Jun 2020 15:48:02 -0400 [thread overview]
Message-ID: <20200622194802.GI17660@denix.org> (raw)
In-Reply-To: <CAAnfSTtxQ3_OST4mk52GNtdaNUWhV3tARX2SfM6k2RaUbrRrtg@mail.gmail.com>
On Mon, Jun 22, 2020 at 08:29:02PM +0100, Ross Burton wrote:
> On Mon, 22 Jun 2020 at 19:44, Denys Dmytriyenko <denis@denix.org> 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
next prev parent reply other threads:[~2020-06-22 19:48 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 7:13 [PATCH 0/6] arm, arm-bsp, arm-toolchain: Add Trusted-Firmware-M recipe gabor.abonyi
2020-06-22 7:13 ` [PATCH 1/6] arm-toolchain: external-arm-toolchain: Rename Gabor Abonyi
2020-06-22 7:13 ` [PATCH 2/6] arm-toolchain: armcompiler: Add Arm Clang recipe Gabor Abonyi
2020-06-22 14:23 ` [meta-arm] " Jon Mason
2020-06-22 18:22 ` Ross Burton
2020-06-23 7:47 ` Gabor Abonyi
2020-06-26 10:05 ` Ross Burton
2020-06-22 7:13 ` [PATCH 3/6] arm: python3-cbor: Add recipe Gabor Abonyi
2020-06-22 7:13 ` [PATCH 4/6] arm: trusted-firmware-m: " Gabor Abonyi
2020-06-22 16:49 ` [meta-arm] " Denys Dmytriyenko
2020-06-22 17:26 ` Jon Mason
2020-06-22 17:36 ` Denys Dmytriyenko
2020-06-22 18:04 ` Joshua Watt
2020-06-23 8:59 ` Gabor Abonyi
2020-07-01 18:08 ` Denys Dmytriyenko
2020-07-02 9:14 ` Ross Burton
2020-07-02 15:39 ` Jon Mason
2020-07-16 6:14 ` Fabien Parent
2020-07-17 13:32 ` Jon Mason
2020-06-22 18:23 ` Ross Burton
2020-06-22 18:43 ` Denys Dmytriyenko
2020-06-22 19:29 ` Ross Burton
2020-06-22 19:48 ` Denys Dmytriyenko [this message]
2020-06-23 7:06 ` Diego Sueiro
2020-07-01 18:10 ` [meta-arm] " Denys Dmytriyenko
2020-07-02 15:33 ` Jon Mason
2020-06-22 7:14 ` [PATCH 5/6] arm-bsp: musca_b1: Add machine Gabor Abonyi
2020-06-22 7:14 ` [PATCH 6/6] arm-bsp: musca_s1: " Gabor Abonyi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200622194802.GI17660@denix.org \
--to=denis@denix.org \
--cc=gabor.abonyi@arm.com \
--cc=meta-arm@lists.yoctoproject.org \
--cc=nd@arm.com \
--cc=ross@burtonini.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.