[meta-intel] Atom E3826 storage that survives over reboot

California Sullivan california.l.sullivan at intel.com
Wed Jan 23 09:24:13 PST 2019


Its really grub vs systemd-boot in this case. systemd-boot is just a 
bootloader, and it can be used without systemd.

Thanks,
Cal

On 1/23/19 3:28 AM, Teemu K wrote:
> On Tue, Jan 22, 2019 at 1:44 PM Mittal, Anuj <anuj.mittal at intel.com> wrote:
>>
>>
>>> -----Original Message-----
>>> From: meta-intel-bounces at yoctoproject.org [mailto:meta-intel-
>>> bounces at yoctoproject.org] On Behalf Of Teemu K
>>> Sent: Tuesday, January 22, 2019 07:25 PM
>>> To: Burton, Ross <ross.burton at intel.com>
>>> Cc: meta-intel at yoctoproject.org
>>> Subject: Re: [meta-intel] Atom E3826 storage that survives over reboot
>>>
>>> On Tue, Jan 22, 2019 at 12:13 PM Burton, Ross <ross.burton at intel.com> wrote:
>>>> EFI variables should work?
>>> After doing some googling it looks promising. I just couldn't find any info how to
>>> actually do it. Also I don't know how big chunk of code is needed to access them from
>>> grub.  Linux seems to have filesystem for that.
>>>
>> There is a basic implementation available to set the next boot target (for systemd-boot which recognizes that specific variable) from kernel here:
>>
>> https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/lib/oeqa/controllers/masterimage.py#n162
> Thanks, I'll take a look and take a look also systemd-boot - code to
> see how big of a task it's actually access that variable from boot
> loader. Of course it'd be so much easier in this case if system would
> be using systemd instead sysvinit.
>
> -Teemu



More information about the meta-intel mailing list