From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: u-boot@lists.denx.de
Subject: u-boot environment on x86
Date: Tue, 31 Mar 2020 11:20:50 +0900 [thread overview]
Message-ID: <20200331022049.GG11504@linaro.org> (raw)
In-Reply-To: <AM7PR10MB37455CC734E95FEF475E362DF8CC0@AM7PR10MB3745.EURPRD10.PROD.OUTLOOK.COM>
On Fri, Mar 27, 2020 at 01:26:09PM +0000, Kim B?ndergaard wrote:
> I'm struggling with a u-boot as an uefi overlay on x86 (currently Qemu).
> Basically it is working, but I'm now considering how /where to store my u-boot environment.
>
> I need to have it stored in a device being accessible also from my Linux being installed by u-boot.
>
> Anyone having had similar considerations.
Can fw_printenv/fw_setenv under tools be a solution to your issue?
(I've never used those commands though.)
> I feel storing the environment in e.g. a FAT file is not the right solution. It is too vulnerable to power loss.
> I'd prefer e.g. a raw sd partition, but u-boot has no means to read it right now. Making support for that would be quite easy I think.
>
> Alternatively I know the UEFI provides means to store "UEFI variables". Anyone who knows if adding the environment as a huge UEFI variable is a way to go?
Any reason to stick to UEFI here?
-Takahiro Akashi
>
> Comments are welcome
>
> Kim B?ndergaard
> Prevas A/S
> Team Manager / Systems Architect
>
> Hedeager 3, DK-8200 Aarhus N
> Phone +45 3315 9090
> Mobile +45 5154 3961
> kibo at prevas.dk
> www.prevas.dk<https://webmail.prevas.se/owa/redir.aspx?C=iN_3zIhizUqp7BVo33RNR3R2ecTf_dEIdGI1j2JStIzDh7zuxYMXNtw7TKp3qanuPKuw20ZD0vE.&URL=http%3a%2f%2fwww.prevas.dk%2f>
>
>
>
next prev parent reply other threads:[~2020-03-31 2:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 13:26 u-boot environment on x86 Kim Bøndergaard
2020-03-31 2:20 ` AKASHI Takahiro [this message]
2020-03-31 5:57 ` Kim Bøndergaard
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=20200331022049.GG11504@linaro.org \
--to=takahiro.akashi@linaro.org \
--cc=u-boot@lists.denx.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