Re: [PATCH v2] of: Specify initrd location using 64-bit

2013-07-22 Thread Jean-Christophe PLAGNIOL-VILLARD
On 14:20 Mon 01 Jul , Santosh Shilimkar 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_set

Re: [PATCH v2] of: Specify initrd location using 64-bit

2013-07-22 Thread Santosh Shilimkar
On Saturday 20 July 2013 01:39 AM, Grant Likely wrote: > On Mon, 01 Jul 2013 16:34:26 -0500, Rob Herring wrote: >> On 07/01/2013 01:20 PM, Santosh Shilimkar wrote: >>> On some PAE architectures, the entire range of physical memory could reside >>> outside the 32-bit limit. These systems need the

Re: [PATCH v2] of: Specify initrd location using 64-bit

2013-07-20 Thread Grant Likely
On Mon, 01 Jul 2013 16:34:26 -0500, Rob Herring wrote: > On 07/01/2013 01:20 PM, Santosh Shilimkar 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 nu

Re: [PATCH v2] of: Specify initrd location using 64-bit

2013-07-01 Thread Vineet Gupta
On 07/01/2013 11:52 PM, Santosh Shilimkar 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_

Re: [PATCH v2] of: Specify initrd location using 64-bit

2013-07-01 Thread Rob Herring
On 07/01/2013 01:20 PM, Santosh Shilimkar 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