ARM client program boot architecture

[Yoder Stuart-B08248]

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

Besides reading code is this stuff written down anywhere? ...for both ARM v7
and ARM v8.

Thanks,
Stuart Yoder


___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev

RE: ARM client program boot architecture

[Yoder Stuart-B08248]

Thanks for the references.

Stuart

> -Original Message-
> From: glik...@secretlab.ca [mailto:glik...@secretlab.ca] On Behalf Of Grant 
> Likely
> Sent: Tuesday, July 23, 2013 7:04 AM
> To: Peter Maydell
> Cc: Yoder Stuart-B08248; boot-architect...@lists.linaro.org; 
> linaro-dev@lists.linaro.org
> Subject: Re: ARM client program boot architecture
> 
> On Tue, Jul 23, 2013 at 12:39 PM, Peter Maydell
>  wrote:
> > On 23 July 2013 12:33, Grant Likely  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.html
> >
> > 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.



___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev