u-boot environment on x86
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.
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?
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@prevas.dk www.prevas.dkhttps://webmail.prevas.se/owa/redir.aspx?C=iN_3zIhizUqp7BVo33RNR3R2ecTf_dEIdGI1j2JStIzDh7zuxYMXNtw7TKp3qanuPKuw20ZD0vE.&URL=http%3a%2f%2fwww.prevas.dk%2f
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@prevas.dk www.prevas.dkhttps://webmail.prevas.se/owa/redir.aspx?C=iN_3zIhizUqp7BVo33RNR3R2ecTf_dEIdGI1j2JStIzDh7zuxYMXNtw7TKp3qanuPKuw20ZD0vE.&URL=http%3a%2f%2fwww.prevas.dk%2f
-----Original Message----- From: AKASHI Takahiro takahiro.akashi@linaro.org Sent: Tuesday, 31 March 2020 04.21 To: Kim Bøndergaard Kim.Bondergaard@prevas.dk Cc: u-boot@lists.denx.de Subject: Re: u-boot environment on x86
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?
I feel it will be easier to get started on most x86 boards since almost all of them come with an UEFI 'bios'.
The reason for putting a u-boot on top of it, is to keep testing similar to our ARM boards. But since you ask, I guess you have some other thoughts. I'm open to ideas so feel free to 'speak'
-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@prevas.dk
participants (2)
-
AKASHI Takahiro -
Kim Bøndergaard