From mboxrd@z Thu Jan 1 00:00:00 1970 From: jonathan@jonmasters.org (Jon Masters) Date: Mon, 10 Sep 2012 16:28:57 -0400 Subject: [PATCH v3 02/31] arm64: Kernel booting and initialisation In-Reply-To: <20120910055339.GC31430@game.jcrosoft.org> References: <1347035226-18649-1-git-send-email-catalin.marinas@arm.com> <1347035226-18649-3-git-send-email-catalin.marinas@arm.com> <20120909172046.GB31430@game.jcrosoft.org> <20120910055339.GC31430@game.jcrosoft.org> Message-ID: <504E4D89.3020203@jonmasters.org> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org 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.