Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756960Ab2HQJi0 (ORCPT ); Fri, 17 Aug 2012 05:38:26 -0400 Received: from mho-02-ewr.mailhop.org ([204.13.248.72]:24311 "EHLO mho-02-ewr.mailhop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754626Ab2HQJiY (ORCPT ); Fri, 17 Aug 2012 05:38:24 -0400 X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 98.234.237.12 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1+ifZJajAw84mW4YO6jVcF4 Date: Fri, 17 Aug 2012 02:38:22 -0700 From: Tony Lindgren To: Catalin Marinas Cc: "linux-arch@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , Arnd Bergmann , Will Deacon Subject: Re: [PATCH v2 04/31] arm64: MMU definitions Message-ID: <20120817093822.GV11011@atomide.com> References: <1344966752-16102-1-git-send-email-catalin.marinas@arm.com> <1344966752-16102-5-git-send-email-catalin.marinas@arm.com> <20120817090451.GP11011@atomide.com> <20120817092106.GA24389@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120817092106.GA24389@arm.com> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1254 Lines: 28 * Catalin Marinas [120817 02:21]: > On Fri, Aug 17, 2012 at 10:04:52AM +0100, Tony Lindgren wrote: > > * Catalin Marinas [120814 10:57]: > > > The virtual memory layout is described in > > > Documentation/arm64/memory.txt. This patch adds the MMU definitions for > > > the 4KB and 64KB translation table configurations. The SECTION_SIZE is > > > 2MB with 4KB page and 512MB with 64KB page configuration. > > > > > > PHYS_OFFSET is calculated at run-time and stored in a variable (no > > > run-time code patching at this stage). > > > > Care to clarify this part a bit? Is the memory standardized somehow > > now and not needed? Or do we still need to add that for various SoCs > > later on? > > The memory is not standardised but we have FDT to fully specify it. The > PHYS_OFFSET does not need to be defined, it is automatically detected at > boo-time based on the kernel load address and stored in a variable to be > used later. OK nice thanks. Tony -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/