From: Thomas Perrot <thomas.perrot@bootlin.com>
To: yocto@lists.yoctoproject.org
Cc: "thomas.perrot@bootlin.com" <thomas.perrot@bootlin.com>,
meta-arm@lists.yoctoproject.org, nylon.chen@sifive.com,
peter.lin@sifive.com,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [RFC] Moving OP-TEE support from meta-arm to oe-core
Date: Tue, 03 Mar 2026 15:31:25 +0100 [thread overview]
Message-ID: <84f4a7735a6ba8af9dfd8d314c71ed02cf4ee7a5.camel@bootlin.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1080 bytes --]
Hello,
I'm following up on the RFC I sent in January [1] about moving OP-TEE
support from meta-arm to oe-core.
Thank you to everyone who participated in the discussion, Ross, Khem,
Sumit, Rahul and John.
OP-TEE is being adopted on RISC-V (non-ARM) platforms, and having it in
oe-core would avoid duplication and fragmentation across layers,
consolidate generic parts, and make it accessible without a dependency
on the ARM BSP layer. This follows the same model as U-Boot, which was
seen as a valid precedent.
Please let us know if you have any remaining concerns or objections,
then to move forward and maybe prepare a first patch series adding OP-
TEE recipes to oe-core with support for qemuarm64 and qemuriscv64 as a
first step.
Kind Regards,
Thomas Perrot
[1]
https://lore.kernel.org/all/39d5c5061d0c220d37a302b5669df66d04ca41c0.camel@bootlin.com/
--
Thomas Perrot, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next reply other threads:[~2026-03-03 14:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 14:31 Thomas Perrot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-01-22 9:33 [RFC] Moving OP-TEE support from meta-arm to oe-core Thomas Perrot
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=84f4a7735a6ba8af9dfd8d314c71ed02cf4ee7a5.camel@bootlin.com \
--to=thomas.perrot@bootlin.com \
--cc=meta-arm@lists.yoctoproject.org \
--cc=nylon.chen@sifive.com \
--cc=peter.lin@sifive.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yocto@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox