From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from nommos.sslcatacombnetworking.com (nommos.sslcatacombnetworking.com [67.18.224.114]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTP id AE041DDF5B for ; Thu, 8 Feb 2007 18:16:21 +1100 (EST) In-Reply-To: <989B956029373F45A0B8AF02970818900D440B@zch01exm26.fsl.freescale.net> References: <989B956029373F45A0B8AF02970818900D440B@zch01exm26.fsl.freescale.net> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <6C343491-B877-4D7D-A46D-B078862160F6@kernel.crashing.org> From: Kumar Gala Subject: Re: [PATCH 1/4] ucc_geth: Change private immrbar_virt_to_phys to generic iopa Date: Thu, 8 Feb 2007 01:16:19 -0600 To: "Li Yang-r58472" Cc: netdev@vger.kernel.org, Tabi Timur-B04825 , linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Feb 8, 2007, at 1:06 AM, Li Yang-r58472 wrote: >>> MURAM is a mmio region so it don't share the characteristic of main >>> memory that phy_addr = virt_addr - PAGE_OFFSET. While they can >>> both be >>> mapped through page table using iopa(). >> >> Right, so when do you know if you'll be using MURAM or normal >> memory? Why not just keep around a token that is the physical >> address at the point you make the decision of MURAM vs normal memory. > > Yes, that can be a way. But as the virt to phy mapping is only used > once, it's nothing bad to do it this way. The problem as I stated before with using iopa() is that its not supported across platforms. - k