From: Denys Dmytriyenko <denis@denix.org>
To: Joshua Watt <jpewhacker@gmail.com>
Cc: Jon Mason <jdmason@gmail.com>, Denys Dmytriyenko <denys@ti.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] arm-trusted-firmware: add upstream version 2.2
Date: Thu, 23 Jan 2020 17:16:27 -0500 [thread overview]
Message-ID: <20200123221627.GF4735@denix.org> (raw)
In-Reply-To: <4e8ae0a5-bf21-9f91-6e04-c1f733f14905@gmail.com>
On Thu, Jan 23, 2020 at 04:10:33PM -0600, Joshua Watt wrote:
>
> On 1/23/20 4:05 PM, Denys Dmytriyenko wrote:
> >On Thu, Jan 23, 2020 at 04:43:23PM -0500, Bruce Ashfield wrote:
> >>On Thu, Jan 23, 2020 at 4:00 PM Denys Dmytriyenko <denis@denix.org> wrote:
> >>>From: Denys Dmytriyenko <denys@ti.com>
> >>>
> >>>Many BSPs require ARM Trusted Firmware (also known as Trusted Firmware-A).
> >>>To avoid duplicating efforts of adding very similar recipes to BSP layers,
> >>>add an upstream reference implementation to openembedded-core, which can be
> >>>customized by BSPs, if needed.
> >>Isn't this one of the things that Jon Mason is trying to
> >>standardize/support in meta-arm ?
> >>
> >>http://git.yoctoproject.org/cgit/cgit.cgi/meta-arm/tree/meta-arm/recipes-bsp/trusted-firmware-a
> >Ah, interesting, somehow I totally missed that one! :)
> >
> >What triggered this submission is that we have our own variant in meta-ti and
> >Joshua Watt was adding a very similar one to meta-rockchip:
> >https://lists.yoctoproject.org/g/yocto/topic/70054501#48116
>
> FWIW, variants of this recipe crop up in pretty much every ARM-based
> BSP layer (e.g. https://github.com/alistair23/meta-pine64/blob/master/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.1.bb);
> it seems common enough that a base recipe that each BSP layer can
> bbappend to suite their needs seems like it would be useful?
Yes, indeed, hence we agreed to submit it to oe-core...
And meta-arm sounds like a good idea and can be used by all those ARM-based
BSPs as a base, but for some reason I cannot find any announcements for that
new layer... Jon?
--
Denys
> >>What's the delta between the two ?
> >Hmm, that one uses older 2.1 version. Other than that, I'll need to test to
> >see if it's as adaptable and expandable as our more simplistic variants...
> >
>
next prev parent reply other threads:[~2020-01-23 22:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 20:59 [PATCH] arm-trusted-firmware: add upstream version 2.2 Denys Dmytriyenko
2020-01-23 21:43 ` Bruce Ashfield
2020-01-23 22:05 ` Denys Dmytriyenko
2020-01-23 22:10 ` Joshua Watt
2020-01-23 22:14 ` Bruce Ashfield
2020-01-23 22:16 ` Denys Dmytriyenko [this message]
2020-01-24 22:30 ` Jon Mason
2020-01-24 22:46 ` Denys Dmytriyenko
2020-01-24 23:00 ` Jon Mason
2020-01-23 22:15 ` Bruce Ashfield
2020-01-24 22:26 ` Jon Mason
2020-01-24 22:24 ` Jon Mason
2020-01-23 22:17 ` Ross Burton
2020-01-23 22:39 ` Andre McCurdy
2020-01-23 22:43 ` Denys Dmytriyenko
2020-01-24 11:42 ` Ross Burton
2020-01-24 17:05 ` Khem Raj
2020-01-24 22:47 ` Jon Mason
2020-01-24 22:59 ` Denys Dmytriyenko
2020-01-23 22:50 ` Richard Purdie
2020-01-24 22:42 ` Jon Mason
2020-01-23 22:57 ` akuster808
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=20200123221627.GF4735@denix.org \
--to=denis@denix.org \
--cc=denys@ti.com \
--cc=jdmason@gmail.com \
--cc=jpewhacker@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox