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 1D9CC679FF for ; Sat, 4 Mar 2006 07:31:50 +1100 (EST) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: Linux on PPC Date: Fri, 3 Mar 2006 14:31:49 -0600 Message-ID: From: "Rune Torgersen" To: "David Hawkins" Cc: linuxppc-embedded@ozlabs.org List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , > From: David Hawkins [mailto:dwh@ovro.caltech.edu]=20 > Sent: Friday, March 03, 2006 14:07 > To: Rune Torgersen > Cc: linuxppc-embedded@ozlabs.org > Subject: Re: Linux on PPC >=20 >=20 > >>Right, thats I made sure to say; Physical Memory Map. > >> > >>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=20 > then map those > > chip selects correctly (size, base address, access with and so on) >=20 > Hi Rune, >=20 > Thanks for responding. >=20 > Thats what I meant with 'redefined in hardware'. But yes, redefined > up to the limit of the wiring on the board of course (chip-selects > and bus widths). That's where having the board schematic is > invaluable. > Does that sound right? Yes.