From: Denys Dmytriyenko <denis@denix.org>
To: Andre McCurdy <armccurdy@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:43:40 -0500 [thread overview]
Message-ID: <20200123224340.GG4735@denix.org> (raw)
In-Reply-To: <CAJ86T=VYsiBgrxPL-N4yy0S2FNUixxn6sfWjaaWQioFHqD=2-g@mail.gmail.com>
On Thu, Jan 23, 2020 at 02:39:52PM -0800, Andre McCurdy wrote:
> On Thu, Jan 23, 2020 at 2:17 PM Ross Burton <ross.burton@intel.com> wrote:
> > On 23/01/2020 21:43, 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
> > >
> > > What's the delta between the two ?
> >
> > That was precisely my thought too. meta-arm isn't exactly well known
> > right now, but ideally it should be a central place for common pieces
> > that are specific to ARM hardware (unlike anything that is needed for
> > qemuarm itself).
>
> Such as all the various cortex etc CPU tuning files?
LOL! :) Of course, since ARM is such an inferior arch to x86. Otherwise we
should move everything that is not needed by qemux86 to meta-intel... JK :)
--
Denys
next prev parent reply other threads:[~2020-01-23 22:43 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
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 [this message]
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=20200123224340.GG4735@denix.org \
--to=denis@denix.org \
--cc=armccurdy@gmail.com \
--cc=denys@ti.com \
--cc=jdmason@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