From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.innovsys.com (smtp.innovsys.com [66.115.232.196]) by ozlabs.org (Postfix) with ESMTP id 1BAA3679E9 for ; Sat, 4 Mar 2006 06:51:32 +1100 (EST) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: Linux on PPC Date: Fri, 3 Mar 2006 13:39:25 -0600 Message-ID: From: "Rune Torgersen" To: "David Hawkins" , "Wolfgang Denk" Cc: linuxppc-embedded@ozlabs.org List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , =20 > From: David Hawkins > Sent: Friday, March 03, 2006 10:53 > To: Wolfgang Denk > Cc: linuxppc-embedded@ozlabs.org > Subject: Re: Linux on PPC >=20 > Right, thats I made sure to say; Physical Memory Map. >=20 > For example, on the Artesyn manual on their PrPMC they give a > physical memory map, and in the Yosemite board, there is a > physical memory map. I know many of the memory areas can be > redefined in hardware to have a different memory location, but > its still a physical address. >=20 Still not right. Even the physical memory is software settable. What matters is what chip-select things are hooked up to, and then map those chip selects correctly (size, base address, access with and so on)