From: Michael Walle <mwalle@kernel.org>
To: xypron.glpk@gmx.de
Cc: Abdellatif.ElKhlifi@arm.com, Drew.Reed@arm.com,
ilias.apalodimas@linaro.org, mark.kettenis@xs4all.nl, nd@arm.com,
sjg@chromium.org, u-boot@lists.denx.de,
Michael Walle <mwalle@kernel.org>
Subject: Re: Adding EFI runtime support to the Arm's FF-A bus
Date: Tue, 19 Dec 2023 11:11:24 +0100 [thread overview]
Message-ID: <20231219101124.2847425-1-mwalle@kernel.org> (raw)
In-Reply-To: <B06FB6F5-416C-440D-BC72-070673DF3177@gmx.de>
Hi Heinrich,
> Any runtime device drivers for variable storage should not be in the
> U-Boot runtime but live in the secure world (e.g. OP-TEE) FF-A is the
> new ARM protocol for talking to the secure world and hence fits into
> the picture.
What if I just want a simple embedded boot stack where I don't
want any secure world and just want to be able to boot a COTS linux
distribution via EFI?
Assuming, that there might be a simple dedicated EEPROM to store the
variables which is not exposed to linux, is that something which would
be rejected by u-boot mainline now?
-michael
next prev parent reply other threads:[~2023-12-19 10:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 15:53 Adding EFI runtime support to the Arm's FF-A bus Abdellatif El Khlifi
2023-12-14 16:47 ` Mark Kettenis
2023-12-14 19:47 ` Ilias Apalodimas
2023-12-18 15:01 ` Simon Glass
2023-12-18 20:59 ` Heinrich Schuchardt
2023-12-19 10:11 ` Michael Walle [this message]
2023-12-19 12:27 ` Mark Kettenis
2023-12-19 12:47 ` Michael Walle
2023-12-19 15:40 ` Tom Rini
2023-12-20 6:17 ` Ilias Apalodimas
2023-12-20 15:43 ` Peter Robinson
2023-12-20 22:57 ` Shantur Rathore
2023-12-21 6:29 ` Ilias Apalodimas
2023-12-21 14:36 ` Shantur Rathore
2023-12-27 14:06 ` Ilias Apalodimas
2023-12-19 15:22 ` Abdellatif El Khlifi
2023-12-20 4:47 ` Simon Glass
2023-12-18 16:59 ` Abdellatif El Khlifi
2024-01-08 14:12 ` Abdellatif El Khlifi
2024-01-08 14:27 ` Heinrich Schuchardt
2024-01-08 14:35 ` Ilias Apalodimas
2024-01-08 16:34 ` Abdellatif El Khlifi
2023-12-18 17:01 ` Abdellatif El Khlifi
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=20231219101124.2847425-1-mwalle@kernel.org \
--to=mwalle@kernel.org \
--cc=Abdellatif.ElKhlifi@arm.com \
--cc=Drew.Reed@arm.com \
--cc=ilias.apalodimas@linaro.org \
--cc=mark.kettenis@xs4all.nl \
--cc=nd@arm.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
/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