From: Laszlo Ersek <lersek@redhat.com>
To: "Gao, Liming" <liming.gao@intel.com>,
Steve Capper <steve.capper@linaro.org>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Leif Lindholm <leif.lindholm@linaro.org>,
Nariman Poushin <nariman.poushin@linaro.org>
Subject: Re: Boot failure for ArmVExpress-FVP-AArch64, CpuArch protocol does not appear to be registered
Date: Thu, 12 Apr 2018 19:31:30 +0200 [thread overview]
Message-ID: <4d59d73c-914c-8d4b-647e-a79f6c3dc47f@redhat.com> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E20D3DA@SHSMSX104.ccr.corp.intel.com>
On 04/12/18 17:02, Gao, Liming wrote:
> Laszlo:
> On variable storage format are hex, could you submit one bugzillar for it? I have some idea to simplify its description. We can reuse FV section for Variable storage. Its FV section is like below.
>
> [FV.NVStorage]
> FileSystemGuid = gEfiSystemNvDataFvGuid
> VariableSignatureGuid = gEfiAuthenticatedVariableGuid
> VariabeRegionSize = 0x40000
> FtwWorkingSpaceSize = 0x40000
> FtwSpareSpaceSize = 0x40000
This looks very nice; I've filed
<https://bugzilla.tianocore.org/show_bug.cgi?id=932>.
Thank you!
Laszlo
prev parent reply other threads:[~2018-04-12 17:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 10:30 Boot failure for ArmVExpress-FVP-AArch64, CpuArch protocol does not appear to be registered Steve Capper
2018-04-11 12:25 ` Laszlo Ersek
2018-04-11 15:34 ` Supreeth Venkatesh
2018-04-11 16:10 ` Ard Biesheuvel
2018-04-11 16:25 ` Laszlo Ersek
2018-04-11 16:20 ` Laszlo Ersek
2018-04-11 16:41 ` Steve Capper
2018-04-12 15:02 ` Gao, Liming
2018-04-12 17:31 ` Laszlo Ersek [this message]
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=4d59d73c-914c-8d4b-647e-a79f6c3dc47f@redhat.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