[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <504E4D89.3020203@jonmasters.org>
Date: Mon, 10 Sep 2012 16:28:57 -0400
From: Jon Masters <jonathan@...masters.org>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@...osoft.com>
CC: Nicolas Pitre <nico@...xnic.net>,
Catalin Marinas <catalin.marinas@....com>,
linux-arch@...r.kernel.org, Arnd Bergmann <arnd@...db.de>,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v3 02/31] arm64: Kernel booting and initialisation
On 09/10/2012 01:53 AM, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 19:29 Sun 09 Sep , Nicolas Pitre wrote:
>> On Sun, 9 Sep 2012, Jean-Christophe PLAGNIOL-VILLARD wrote:
>>
>>> On 17:26 Fri 07 Sep , Catalin Marinas wrote:
>>>> +4. Call the kernel image
>>>> +------------------------
>>>> +
>>>> +Requirement: MANDATORY
>>>> +
>>>> +The decompressed kernel image contains a 32-byte header as follows:
>>>> +
>>>> + u32 magic = 0x14000008; /* branch to stext, little-endian */
>>>> + u32 res0 = 0; /* reserved */
>>>> + u64 text_offset; /* Image load offset */
>>>> + u64 res1 = 0; /* reserved */
>>>> + u64 res2 = 0; /* reserved */
>>> we need to have a magic to known it's a arm64 kernel
>>
>> You have it: it's 0x14000008 at the beginning.
> fragile
Others have commented on the relocatable kernel non-issue. But to this
part, also bear in mind that Catalin pointed out boot standardization
work may change how some AArch64 systems ultimately end up booting.
Thanks,
Jon.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists