From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Wed, 4 Apr 2007 09:29:05 -0700 From: "Mark A. Greer" To: Segher Boessenkool Subject: Re: [RFC 3/3] powerpc: Add DTS file for the Motorola PrPMC2800 platform Message-ID: <20070404162905.GD21314@mag.az.mvista.com> References: <20070328011924.GA1586@mag.az.mvista.com> <20070328012206.GD1586@mag.az.mvista.com> <9696D7A991D0824DBA8DFAC74A9C5FA302BDAB3E@az33exm25.fsl.freescale.net> <20070329003550.GB25652@localhost.localdomain> <20070402181553.GH2132@mag.az.mvista.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 In-Reply-To: Cc: linuxppc-dev , Dale Farnsworth , Yoder Stuart-B08248 List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, Apr 04, 2007 at 01:18:41PM +0200, Segher Boessenkool wrote: > >Agreed. Dale Farnsworth suggested a 'ranges' type property at the top > >level that's used for phys->virt mappings. That is much cleaner IMHO > >and eliminates the need to parse hash tables or add ioremap code to the > >bootwrapper. > > I suggest you implement the standard "mmu" binding instead, > or the part that is relevant to you anyway: > > /chosen/mmu contains the ihandle for an "mmu" node (for > flat trees, you use a phandle instead); > > that node has properties, quoting from the base OF spec: > > “available” > The property values are as defined for the standard “reg” format, > with single-cell virtual addresses. The regions of virtual address > space denote the virtual address space that is currently unallocated > by the Open Firmware and is available for use by client programs. > > “existing” > The value of this property defines the regions of virtual address > space managed by the MMU in whose package this property is defined > without regard to whether or not these regions are currently in use. > The encodings of virt and len are MMU-specific. > > Have a look at the PowerPC binding to find out about that specific > encoding. Cool, thanks for the pointer Segher. Mark