From: Philipp Deppenwiese <zaolin.daisuki@gmail.com>
To: Jose Trujillo <ce.autom@protonmail.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: CorebootPayloadPkg: How to make boot/ACPI settings persistent?
Date: Wed, 18 Jul 2018 15:29:28 +0200 [thread overview]
Message-ID: <a4df92ef-c7ac-4d7b-67e1-6ba49e39820f@gmail.com> (raw)
In-Reply-To: <LrYRcRgflKAAAglThz2HCWntmmcMcU6ggQt9t3mvltlzXqhL8LTUbqpI5sMvFzUEzqReBXyhAnfrR2US1Cc-JvqKy8C0CgLmfSTz7eEtrz8=@protonmail.com>
Hey Jose,
There is a commit in the coreboot gerrit:
https://review.coreboot.org/#/c/coreboot/+/25182/
Introducing SMM vars for UEFI firmware. Not sure how far it got.
Try to ping patrickg on freenode #coreboot channel
BR, Philipp
On 18.07.2018 13:21, Jose Trujillo wrote:
> Dear EDK2 developers:
>
> I am running coreboot in a Intel Baytrail I E3845 board.
> I already built and integrated Tianocore as a payload of coreboot and is running great.
>
> But I still would like to know how to save the boot settings and ACPI parameters into non volatile memory.
>
> Actually if I want to boot from a multiboot HDD I need to manually with the option "boot from file"
> and boots fine the latest Fedora/Ubuntu and W7/W10.
>
> But I have S3, S4 (ACPI) issues when using Tianocore.
>
> And I would like to get some advise from you in how to save Tianocore data into NVS.
>
> Thank you in advance.
> Jose Trujillo.
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2018-07-18 13:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 11:21 CorebootPayloadPkg: How to make boot/ACPI settings persistent? Jose Trujillo
2018-07-18 13:29 ` Philipp Deppenwiese [this message]
2018-07-18 14:07 ` Jose Trujillo
[not found] ` <1376fbb7-12ab-6244-7717-e5237d1b2c3f@gmail.com>
2018-07-18 13:34 ` Philipp Deppenwiese
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-list 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=a4df92ef-c7ac-4d7b-67e1-6ba49e39820f@gmail.com \
--to=devel@edk2.groups.io \
/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