On Mon, Jul 22, 2013 at 8:56 PM, Yoder Stuart-B08248
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.
On Mon, 2013-07-22 at 19:56 +, Yoder Stuart-B08248 wrote:
> Is there a written spec or description of how a boot program (u-boot, UEFI,
> hypervisor) boots an OS on ARM platforms?
There's some information in the Linux source in the file
Documentation/arm/Booting.
--
Tixy
__
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.
>
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
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=
On Tue, 2013-07-23 at 09:16 +0100, Jon Medhurst (Tixy) wrote:
> On Mon, 2013-07-22 at 19:56 +, Yoder Stuart-B08248 wrote:
> > Is there a written spec or description of how a boot program (u-boot, UEFI,
> > hypervisor) boots an OS on ARM platforms?
>
> There's some information in the Linux sour
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
