[OE-core] [PATCH] arm-trusted-firmware: add upstream version 2.2

Jon Mason jdmason at kudzu.us
Fri Jan 24 22:47:44 UTC 2020

On Fri, Jan 24, 2020 at 12:05 PM Khem Raj <raj.khem at gmail.com> wrote:
> On 1/24/20 3:42 AM, Ross Burton wrote:
> > On 23/01/2020 22:43, Denys Dmytriyenko wrote:
> >>> 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 :)
> >
> > I almost pre-empted this comment in my reply because I knew it was
> > coming. :)
> >
> > Personally, not a terrible idea.  The slight difference is that
> > meta-intel is *Intel's* BSP and we don't share stuff like
> > firmware/drivers with AMD.
> >
> > Ross
> it will be good to find what the overlap will be, is it something that
> BSPs can use with minimum changes, or are we providing a template that
> will be copied over and housed in form of bbappends or bbs. I am not
> familiar enough to assess that.
> Perhaps it would be good to limit this to arm compatible machines,
> secondly, there is a point in having it in OE-Core if meta-arm is
> limiting itself to arm provided BSPs alone. I think it will be good to
> have a platform supported in core to be able to test it, between qemu
> and beaglebone, I guess it is not used. Or pehaps it is and we do not
> use it, so that change would be good to have as well.

To be clear, we do not want this limited to Arm BSPs.  We want this
used by everyone, to make this recipe as solid as possible.  Also, we
hope it encourages everyone to contribute their TF-A source code
"up-stream" and use the generic recipe.


> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core

More information about the Openembedded-core mailing list