On Tuesday 30 July 2013 05:21 PM, Khasim Syed Mohammed wrote:
> Hi UEFI team,
>
> We are in the process of evaluating the tianocore EDKII for Android. I
> have the same booting on Arndale, but I am unable to find commands or
> procedure to flash (raw image) to onboard eMMC / SD cards.
It is implemented.Please refer the following wiki page for details
https://wiki.linaro.org/Boards/Arndale/Setup/EnterpriseUbuntuServer?action=…
>
> Can you please confirm if these features are already implemented in
> our sources?
>
> We need this info to estimate the effort for UEFI, kindly confirm at
> the earliest.
>
> Thanks.
>
> Regards,
> Khasim
Regards
Rony.
After the UEFI 2.4 specification - that contains the AArch64 (the ARM 64-bit
architecture) Binding - was approved last week, I started to send the
AArch64 patchset to be reviewed by the different EDK2 maintainers.
Because patches are still waiting to be approved and also not all the
patches have been sent yet (such as the pre-built binaries and few minor
others), I created a snapshot of the latest subversion (svn rev 14505 -
Friday 26 Jul 2013) with the AArch64 pathset to make it easier for people to
play with UEFI on AArch64 platforms.
The main reason of creating a snapshot and not a patch is binary data are
not really portable in patch files.
This archive is only a short term solution and should not be considered as a
release package (some AArch64 patches could diverge from their original
revision). The archive will be removed after all the patches will have been
accepted by the maintainers.
'Direct' link to the archive:
http://sourceforge.net/projects/edk2/files/ARM/aarch64-uefi-rev14505.tgz/dow
nload
Tutorial to build and run AArch64 EDK2 on the Foundation and Base FVP Model:
https://sourceforge.net/apps/mediawiki/tianocore/index.php?title=ArmPlatform
Pkg/AArch64
Note: The AArch64 Foundation FVP Model is free to download. So anyone could
try to build and run AArch64 UEFI on this Virtual Platform.
Thanks,
Olivier
On Tue, Jul 23, 2013 at 12:39 PM, Peter Maydell
<peter.maydell(a)linaro.org> wrote:
> On 23 July 2013 12:33, Grant Likely <grant.likely(a)secretlab.ca> wrote:
>> Historically each ARM SoC did its own thing for secondary CPU startup.
>> New platforms are expected to use the PSCI spec (which unfortunately
>> isn't an open document, but ARM partners can get access).
>>
>> http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.den0022b/index.…
>
> I believe that's just behind the same "you need to create
> an account on the website and login" wall as the main
> ARM ARM, isn't it? You don't need to be an ARM partner.
You're right. My mistake. Sorry for the noise.
g.
On Mon, Jul 22, 2013 at 8:56 PM, Yoder Stuart-B08248
<B08248(a)freescale.com> wrote:
> Is there a written spec or description of how a boot program (u-boot, UEFI,
> hypervisor) boots an OS on ARM platforms?
>
> ePAPR-type device trees are used to describe a platform, but what
> about the type of information in sections 5.3, 5.4 and 5.5 of the ePAPR:
> -initial mapped areas
> -state of MMU at the point the boot program transfers
> control to the OS, initial MMU mappings
> -initial state of registers
> -mechanisms to start secondary CPUs-- e.g. spin table
Historically each ARM SoC did its own thing for secondary CPU startup.
New platforms are expected to use the PSCI spec (which unfortunately
isn't an open document, but ARM partners can get access).
http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.den0022b/index.…
PSCI support has been merged into the kernel. Just 'git grep PSCI'.
g.
