Re: Boot failure for ArmVExpress-FVP-AArch64, CpuArch protocol does not appear to be registered

[Laszlo Ersek <lersek@redhat.com>]

On 04/11/18 18:10, Ard Biesheuvel wrote:
> On 11 April 2018 at 17:34, Supreeth Venkatesh
> <Supreeth.Venkatesh@arm.com> wrote:
>> Laszlo/Steve,
>>
>> I ran into the same problem on ArmVExpress-FVP-AArch64 while running management mode.
>> I have fixed this problem in this patch by reordering driver load order here:
>> https://lists.01.org/pipermail/edk2-devel/2018-April/023550.html
>>
>> Not sure whether Leif/Ard/Laszlo agree with this.
>>
> 
> Nope, sorry. PI has an elaborate scheme involving dependency
> expressions to manage load order of modules, and tweaking the order
> they appear in the flash volume to get things working again is not the
> way to address this.
> 
> Ironically, though, it seems my patch
> 61a7b0ec634fa3288f47929ba3ced05ff48de739 (which introduces an AFTER
> xxx depex) is the culprit here, and so I should probably take some
> responsibility to get things working again.
> 
> I will look into replacing the NorFlashDxe DEPEX with something more
> suitable to address this issue, but I am a bit swamped at the moment,
> so if anyone else beats me to it, I won't complain.

I'll try. :)

Thanks,
Laszlo