From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757267Ab2ILXso (ORCPT ); Wed, 12 Sep 2012 19:48:44 -0400 Received: from devils.ext.ti.com ([198.47.26.153]:49702 "EHLO devils.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757112Ab2ILXsj (ORCPT ); Wed, 12 Sep 2012 19:48:39 -0400 Message-ID: <50511EB5.800@ti.com> Date: Wed, 12 Sep 2012 19:45:57 -0400 From: Cyril Chemparathy User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: Rob Herring CC: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , Subject: Re: [PATCH] of: specify initrd location using 64-bit References: <1347465937-7056-1-git-send-email-cyril@ti.com> <5050EF3F.6030003@gmail.com> In-Reply-To: <5050EF3F.6030003@gmail.com> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 9/12/2012 4:23 PM, Rob Herring wrote: > On 09/12/2012 11:05 AM, Cyril Chemparathy wrote: >> On some PAE architectures, the entire range of physical memory could reside >> outside the 32-bit limit. These systems need the ability to specify the >> initrd location using 64-bit numbers. >> >> This patch globally modifies the early_init_dt_setup_initrd_arch() function to >> use 64-bit numbers instead of the current unsigned long. > > S-o-B? > Sorry about that, will include in v2. [...] >> --- a/arch/arm/mm/init.c >> +++ b/arch/arm/mm/init.c >> @@ -76,7 +76,7 @@ static int __init parse_tag_initrd2(const struct tag *tag) >> __tagtable(ATAG_INITRD2, parse_tag_initrd2); >> >> #ifdef CONFIG_OF_FLATTREE >> -void __init early_init_dt_setup_initrd_arch(unsigned long start, unsigned long end) >> +void __init early_init_dt_setup_initrd_arch(u64 start, u64 end) > > phys_initrd_start/size need to change too. Not sure about similar things > on other arches. > I've fixed phys_initrd_start (not size) in another patch, please see [1]. > Does u-boot need similar fixes? > We aren't there yet :-) We are currently running this platform without u-boot. [1] http://permalink.gmane.org/gmane.linux.kernel/1356713 -- Thanks - Cyril