public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Steve Capper <steve.capper@linaro.org>
To: Laszlo Ersek <lersek@redhat.com>
Cc: edk2-devel@lists.01.org,
	Nariman Poushin <nariman.poushin@linaro.org>,
	 Leif Lindholm <leif.lindholm@linaro.org>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: Boot failure for ArmVExpress-FVP-AArch64, CpuArch protocol does not appear to be registered
Date: Wed, 11 Apr 2018 17:41:05 +0100	[thread overview]
Message-ID: <CAPvkgC0TWU+zziXLdxqdqqXE9q4EAzqYdOGgT2_vgs6vWktuLA@mail.gmail.com> (raw)
In-Reply-To: <ed541568-2269-8e3b-2d6b-1136c4fc9865@redhat.com>

On 11 April 2018 at 13:25, Laszlo Ersek <lersek@redhat.com> wrote:
> Hi Steve,

Hi Laszlo,

[...]

> Summary:
> (1) introduce a custom GUID for "NorFlashDxe has formatted the variable
>     store headers for the variable driver to read";
> (2) install the GUID in NorFlashDxe once it's done verifying and/or
>     formatting the headers;
> (3) introduce a custom library instance with an empty constructor
>     function, and a DEPEX on the GUID;
> (4) hook the library instance into
>     "MdeModulePkg/Universal/Variable/RuntimeDxe/VariableRuntimeDxe.inf"
>     in all the platform DSC files where the platform build does not
>     pre-format a varstore template in the FDF file;
> (5) replace the BEFORE depex with gEfiCpuArchProtocolGuid.
>

A *very* big thank you for taking the time to explain this in detail,
after a couple of reads (I mainly just build EDK2) I was able to get
something booting following the above approach :-).

Cheers,
--
Steve


  parent reply	other threads:[~2018-04-11 16:41 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 [this message]
2018-04-12 15:02   ` Gao, Liming
2018-04-12 17:31     ` Laszlo Ersek

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=CAPvkgC0TWU+zziXLdxqdqqXE9q4EAzqYdOGgT2_vgs6vWktuLA@mail.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