On Mon, Jul 22, 2013 at 8:56 PM, Yoder Stuart-B08248 B08248@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.h...
PSCI support has been merged into the kernel. Just 'git grep PSCI'.
g.
boot-architecture@lists.linaro.org