On 30 November 2015 at 10:39, Michael Zimmermann <sigmaepsilo...@gmail.com> wrote: >> Unrelated note: *please* get rid of the ARM BDS and use the Intel BDS >> instead. The ARM BDS violates the UEFI spec, (i.e., you cannot boot >> installer images from it without a lot of hassle) and does not allow >> you to enable UEFI secure boot. >> >> Look at the development history of ArmVExpress-FVP-AArch64.dsc for >> hints how to do this. > > To make this easier for other, here is my commit for switching to Intel's > BDS(my code is based on ArmPlatformPkg/ArmPlatformPkg-2ndstage): > https://github.com/efidroid/uefi_edk2packages_LittleKernelPkg/commit/dbbf212823046e00db3879c6846d96532f703e30 > > You may also need dynamic PCD support: > https://github.com/efidroid/uefi_edk2packages_LittleKernelPkg/commit/673cd3bc2d71bf077e5744d9de1597a356b6d2d5 >
Thanks for sharing that. I hope it will be useful to other. Since the Intel BDS support is fairly recent, please don't hesitate to share observations or questions. There may be some issues lurking that we haven't spotted yet ourselves. Thanks, Ard. > On Tue, Nov 24, 2015 at 8:28 AM, Ard Biesheuvel <ard.biesheu...@linaro.org> > wrote: >> >> On 24 November 2015 at 00:05, Vladimir Olovyannikov >> <volov...@broadcom.com> wrote: >> >> -----Original Message----- >> >> From: Ard Biesheuvel [mailto:ard.biesheu...@linaro.org] >> >> Sent: Wednesday, November 18, 2015 11:32 PM >> >> To: Vladimir Olovyannikov >> >> Cc: Mark Rutland; edk2-devel@lists.01.org >> >> Subject: Re: [edk2] Armv8 64bit: System error booting linux from the >> >> UEFI >> >> >> >> On 19 November 2015 at 05:48, Vladimir Olovyannikov >> >> <volov...@broadcom.com> wrote: >> >> > >> >> > >> > [...] >> >> > A side note: I got the u-boot source for that board and there are >> >> > several >> >> hacks made to avoid SError (writing 0x20 to the HCR register (reroute >> >> SError >> >> to EL2), and >> >> > just ERET from SError exception handler, and then write 0x0 to HCR >> >> > before >> >> Linux boots), so it could be an HW issue I am not aware of as of yet. >> >> >> >> OK, that would explain it. Note that the kernel will replace the EL2 >> >> vector table if booted at EL2, so this is definitely not a workaround >> >> that you would want to reuse in UEFI. >> > [...] >> > >> > [...] >> >> >> >> >> >> I'd still like to double check the value of VBAR_EL2 as it is >> >> >> written, >> >> >> it should be a multiple of 2 KB >> >> > It is always at 0x85008800 which is a multiple of 2K >> >> > Any other things to verify? >> >> > >> >> >> >> No, that looks fine. You need to get in touch with the authors of the >> >> U-Boot code to figure out what it is they are working around. Simply >> >> ignoring SErrors is obviously not a long term solution. >> >> >> > Thanks a lot for your help Ard, Mark, >> > It is the ATF which has an issue. I will post additional information if >> > there is still a problem after ATF implementation is fixed >> > >> >> OK. >> Thanks for reporting back. >> >> -- >> Ard. >> _______________________________________________ >> edk2-devel mailing list >> edk2-devel@lists.01.org >> https://lists.01.org/mailman/listinfo/edk2-devel > > _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
