From: "Rahul Singh" <rahuls.work97@gmail.com>
To: "Ross Burton" <ross.burton@arm.com>, yocto@lists.yoctoproject.org
Subject: Re: [yocto] [RFC] Moving OP-TEE support from meta-arm to oe-core
Date: Thu, 22 Jan 2026 09:32:26 -0800 [thread overview]
Message-ID: <267167.1769103146565811779@lists.yoctoproject.org> (raw)
In-Reply-To: <6C7BC2F4-364D-41C1-87CB-755547FE281E@arm.com>
[-- Attachment #1: Type: text/plain, Size: 349 bytes --]
Hi,
I would like to add to this point that since the branches aren't gonna be shared (vendor specific or vendor agnostic), I feel we should first choose the suitable architecture implementation first where the base ISA is shared across many platforms (probably RV64* or RV32*)and then list out probable steps how OPTEE should be ported to risc-v.
[-- Attachment #2: Type: text/html, Size: 371 bytes --]
next prev parent reply other threads:[~2026-01-22 17:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 9:33 [RFC] Moving OP-TEE support from meta-arm to oe-core Thomas Perrot
2026-01-22 17:04 ` [yocto] " Ross Burton
2026-01-22 17:22 ` Khem Raj
2026-01-23 11:20 ` [meta-arm] " Sumit Garg
2026-02-03 16:29 ` Thomas Perrot
2026-03-31 13:49 ` Jose Quaresma
2026-01-22 17:32 ` Rahul Singh [this message]
2026-01-24 13:23 ` John Dowd
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=267167.1769103146565811779@lists.yoctoproject.org \
--to=rahuls.work97@gmail.com \
--cc=ross.burton@arm.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