From: Denys Dmytriyenko <denis@denix.org>
To: Ross Burton <Ross.Burton@arm.com>
Cc: Jon Mason <jdmason@kudzu.us>,
Adam Johnston <Adam.Johnston@arm.com>,
"meta-arm@lists.yoctoproject.org"
<meta-arm@lists.yoctoproject.org>, nd <nd@arm.com>,
Jon Mason <Jon.Mason@arm.com>,
Yocto TSC <tsc@lists.yoctoproject.org>
Subject: Re: [meta-arm] [PATCH 1/1] arm-bsp/optee: Update OP-TEE TA devkit to 3.20 for N1SDP
Date: Wed, 5 Apr 2023 19:44:14 -0400 [thread overview]
Message-ID: <20230405234414.GJ9226@denix.org> (raw)
In-Reply-To: <4C217F66-AD65-48CF-8850-78CC7034F21F@arm.com>
On Wed, Apr 05, 2023 at 07:20:20PM +0000, Ross Burton wrote:
> On 5 Apr 2023, at 20:13, Jon Mason <jdmason@kudzu.us> wrote:
> >
> >> At the TSC meetings recently we've discussed the possibility of migrating
> >> Trusted Firmware and OP-TEE components from meta-arm to oe-core in order to
> >> reduce dependencies on these core components by other BSPs.
>
> My opinion here is that in the ideal world a generic-arm64 BSP wouldn’t need
> anything extra in oe-core to work: assume working firmware (SystemReady),
> mainline kernel, mainline U-Boot, etc and it will work. It may not be as
> fully functional as you’d get by adding custom optee/tf pieces but that’s
> where meta-arm steps in, which was designed explicitly to be BSP-agnostic.
Understood and agree. I'm not yet that much familiar with SystemReady firmware
specifics - does that include Trusted Firmware? Not so sure about OP-TEE, but
what does the spec say about it?
--
Denys
next prev parent reply other threads:[~2023-04-05 23:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 15:43 [PATCH 0/1] arm-bsp/optee: Update OP-TEE TA devkit to 3.20 for N1SDP adam.johnston
2023-04-03 15:43 ` [PATCH 1/1] " adam.johnston
2023-04-04 0:05 ` [meta-arm] " Denys Dmytriyenko
2023-04-04 8:24 ` Adam Johnston
2023-04-04 16:14 ` Denys Dmytriyenko
2023-04-05 8:02 ` Adam Johnston
2023-04-05 15:08 ` Denys Dmytriyenko
2023-04-05 19:13 ` Jon Mason
2023-04-05 19:20 ` Ross Burton
2023-04-05 23:44 ` Denys Dmytriyenko [this message]
2023-04-06 7:29 ` Ross Burton
2023-04-06 17:39 ` [tsc] " akuster808
2023-04-06 19:04 ` Ross Burton
2023-04-05 23:40 ` Denys Dmytriyenko
2023-04-10 13:57 ` [PATCH 0/1] " Jon Mason
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=20230405234414.GJ9226@denix.org \
--to=denis@denix.org \
--cc=Adam.Johnston@arm.com \
--cc=Jon.Mason@arm.com \
--cc=Ross.Burton@arm.com \
--cc=jdmason@kudzu.us \
--cc=meta-arm@lists.yoctoproject.org \
--cc=nd@arm.com \
--cc=tsc@lists.yoctoproject.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 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.