From: hchauhan@ventanamicro.com <hchauhan@ventanamicro.com>
To: opensbi@lists.infradead.org
Subject: [PATCH 1/1] Add RISC-V TEE support
Date: Wed, 11 Jan 2023 17:32:44 +0530 [thread overview]
Message-ID: <019501d925b4$9e792220$db6b6660$@ventanamicro.com> (raw)
In-Reply-To: <20230111020159.1234-1-liushiwei@eswincomputing.com>
-----Original Message-----
> From: opensbi <opensbi-bounces@lists.infradead.org> On Behalf Of liushiwei
> Sent: 11 January 2023 07:32
> To: opensbi at lists.infradead.org
> Cc: chenchaokai at eswincomputing.com; liushiwei
<liushiwei@eswincomputing.com>
> Subject: [PATCH 1/1] Add RISC-V TEE support
>RISC-V Trusted Executable Environment security software includes linux,
opensbi, and OP-TEE OS. linux is the non-secure domain, and OP-TEE OS is the
secure domain. At boot time, opensbi boots OP->TEE OS and then starts linux.
At runtime, opensbi acts as a secure monitor, responsible for context saving
and restoring when switching between linux and OP-TEE OS.
>TEE function is off by default, when using configuration is added in the
config and objects file, such as platform/generic/configs/defconfig add
CONFIG_SBI_ECALL_TEE = y, In the >platform/generic/objects.mk add
CONFIG_TEE_LOAD_ADDR = 0x27c000000, CONFIG_TEE_LOAD_ADDR is the starting
address of the OP-TEE OS.
Hi Liushiwei,
Was there any formal specification or draft for this? Could you please point
me to the draft or specification?
Regards
Himanshu
--
opensbi mailing list
opensbi at lists.infradead.org
http://lists.infradead.org/mailman/listinfo/opensbi
next prev parent reply other threads:[~2023-01-11 12:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 2:01 [PATCH 1/1] Add RISC-V TEE support liushiwei
2023-01-11 12:02 ` hchauhan [this message]
2023-01-11 12:27 ` 答复: " liushiwei
2023-01-11 12:34 ` Anup Patel
2023-01-12 7:06 ` 答复: " liushiwei
2023-01-13 3:30 ` liushiwei
2023-01-13 11:46 ` Conor Dooley
2023-01-11 15:38 ` Himanshu Chauhan
2023-01-12 7:08 ` 答复: " liushiwei
2023-01-13 11:59 ` Anup Patel
2023-01-16 13:09 ` 答复: " liushiwei
2023-01-21 13:36 ` Anup Patel
2023-01-24 19:12 ` Atish Patra
2023-01-11 12:43 ` liushiwei
-- strict thread matches above, loose matches on Subject: below --
2023-01-11 2:08 liushiwei
2023-01-16 13:08 liushiwei
2023-01-28 7:39 liushiwei
2023-01-28 8:33 liushiwei
2023-02-07 22:37 ` Atish Patra
2023-02-16 11:40 liushiwei
2023-02-21 20:22 ` Atish Patra
2023-02-23 11:23 liushiwei
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='019501d925b4$9e792220$db6b6660$@ventanamicro.com' \
--to=hchauhan@ventanamicro.com \
--cc=opensbi@lists.infradead.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