From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754721AbcAHKYC (ORCPT ); Fri, 8 Jan 2016 05:24:02 -0500 Received: from smarthost01c.mail.zen.net.uk ([212.23.1.5]:55293 "EHLO smarthost01c.mail.zen.net.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754497AbcAHKWg (ORCPT ); Fri, 8 Jan 2016 05:22:36 -0500 Message-ID: <1452248544.3006.2.camel@linaro.org> Subject: Re: [Question] Any restriction for the location of initramdisk? From: "Jon Medhurst (Tixy)" To: Masahiro Yamada Cc: linux-arm-kernel , Russell King - ARM Linux , Linux Kernel Mailing List , Arnd Bergmann Date: Fri, 08 Jan 2016 10:22:24 +0000 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.9-1+b1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Originating-smarthost01c-IP: [82.69.122.217] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2016-01-08 at 16:16 +0900, Masahiro Yamada wrote: > Hi. > > > I know DTB should be located within the reach of the kernel > so that the kernel can get access to it at the early boot stage. > In other words, DTB should be put in the low memory area. > > Does initramdisk has the similar restriction? I assume so, as that's what Documentation/arm/Booting says ... 5. Load initramfs. ------------------ Existing boot loaders: OPTIONAL New boot loaders: OPTIONAL If an initramfs is in use then, as with the dtb, it must be placed in a region of memory where the kernel decompressor will not overwrite it while also with the region which will be covered by the kernel's low-memory mapping. A safe location is just above the device tree blob which itself will be loaded just above the 128MiB boundary from the start of RAM as recommended above. -- Tixy