From: Khem Raj <raj.khem@gmail.com>
To: Ross Burton <ross.burton@intel.com>,
Denys Dmytriyenko <denis@denix.org>,
Andre McCurdy <armccurdy@gmail.com>
Cc: Jon Mason <jdmason@gmail.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
Denys Dmytriyenko <denys@ti.com>
Subject: Re: [PATCH] arm-trusted-firmware: add upstream version 2.2
Date: Fri, 24 Jan 2020 09:05:09 -0800 [thread overview]
Message-ID: <51f70cda-9ddf-ea8c-e8a9-3a3f69db8167@gmail.com> (raw)
In-Reply-To: <0620f17c-53ca-7e95-1607-621507baedd8@intel.com>
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.
next prev parent reply other threads:[~2020-01-24 17:05 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
2020-01-24 11:42 ` Ross Burton
2020-01-24 17:05 ` Khem Raj [this message]
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=51f70cda-9ddf-ea8c-e8a9-3a3f69db8167@gmail.com \
--to=raj.khem@gmail.com \
--cc=armccurdy@gmail.com \
--cc=denis@denix.org \
--cc=denys@ti.com \
--cc=jdmason@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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.