Date: Wed, 15 Mar 2006 16:13:35 -0500
From: Benjamin LaHaise <bcrl@kvack.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Vivek Goyal <vgoyal@in.ibm.com>,
       linux kernel mailing list <linux-kernel@vger.kernel.org>,
       Fastboot mailing list <fastboot@lists.osdl.org>,
       "Eric W. Biederman" <ebiederm@xmission.com>,
       Morton Andrew Morton <akpm@osdl.org>, gregkh@suse.de
Subject: Re: [RFC][PATCH] Expanding the size of "start" and "end" field in "struct resource"
Message-ID: <20060315211335.GD25361@kvack.org>
References: <20060315193114.GA7465@in.ibm.com> <20060315205306.GC25361@kvack.org> <46E23BE4-4353-472B-90E6-C9E7A3CFFC15@kernel.crashing.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <46E23BE4-4353-472B-90E6-C9E7A3CFFC15@kernel.crashing.org>
User-Agent: Mutt/1.4.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1005
Lines: 24

On Wed, Mar 15, 2006 at 03:05:30PM -0600, Kumar Gala wrote:
> I disagree.  I think we need to look to see what the "bloat" is  
> before we go and make start/end config dependent.

Eh?  32 bit kernels get used in embedded systems, which includes those 
with only 8MB of RAM.  The upper 32 bits will never be anything other 
than 0.

> It seems clear that drivers dont handle the fact that "start"/"end"  
> change an 32-bit vs 64-bit archs to begin with.  By making this even  
> more config dependent seems to be asking for more trouble.

You can't get a non-32 bit value on a 32 bit platform, so why should a 
driver be expected to handle anything?

		-ben
-- 
"Time is of no importance, Mr. President, only life is important."
Don't Email: <dont@kvack.org>.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/