From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from sunset.davemloft.net (unknown [74.93.104.97]) by ozlabs.org (Postfix) with ESMTP id 50142DDEE7 for ; Thu, 14 Feb 2008 09:24:01 +1100 (EST) Date: Wed, 13 Feb 2008 14:24:32 -0800 (PST) Message-Id: <20080213.142432.206908646.davem@davemloft.net> To: galak@kernel.crashing.org Subject: Re: [GIT]: Make LMB code sharable with sparc64. From: David Miller In-Reply-To: References: <20080213.004120.22092044.davem@davemloft.net> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Cc: sparclinux@vger.kernel.org, linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Kumar Gala Date: Wed, 13 Feb 2008 07:12:26 -0600 > Does sparc have the concept of a phys_addr_t? We are in the process > of expanding the lmb support to deal with 36-bit physical addresses on > 32-bit machines. On sparc64, where I intend to use this, unsigned long's are 64-bit. If you use some phys_addr_t type instead to help ppc32 along, that would be perfectly fine with me.