From: Cyril Chemparathy <cyril@ti.com>
To: Rob Herring <robherring2@gmail.com>
Cc: <devicetree-discuss@lists.ozlabs.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-c6x-dev@linux-c6x.org>, <linux-kernel@vger.kernel.org>,
<linux-mips@linux-mips.org>, <linux@openrisc.net>,
<linuxppc-dev@lists.ozlabs.org>,
<microblaze-uclinux@itee.uq.edu.au>, <x86@kernel.org>,
<david.daney@cavium.com>, <benh@kernel.crashing.org>,
<bigeasy@linutronix.de>, <grant.likely@secretlab.ca>,
<paul.gortmaker@windriver.com>, <paulus@samba.org>,
<hpa@zytor.com>, <m.szyprowski@samsung.com>, <jonas@southpole.se>,
<linux@arm.linux.org.uk>, <nico@linaro.org>, <a-jacquiot@ti.com>,
<mingo@redhat.com>, <suzuki@in.ibm.com>,
<mahesh@linux.vnet.ibm.com>, <linus.walleij@linaro.org>,
<arnd@arndb.de>, <msalter@redhat.com>, <rob.herring@calxeda.com>,
<tglx@linutronix.de>, <blogic@openwrt.org>, <dhowells@redhat.com>,
<monstr@monstr.eu>, <ralf@linux-mips.org>, <tj@kernel.org>
Subject: Re: [PATCH] of: specify initrd location using 64-bit
Date: Wed, 12 Sep 2012 19:45:57 -0400 [thread overview]
Message-ID: <50511EB5.800@ti.com> (raw)
In-Reply-To: <5050EF3F.6030003@gmail.com>
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
WARNING: multiple messages have this Message-ID (diff)
From: Cyril Chemparathy <cyril@ti.com>
To: Rob Herring <robherring2@gmail.com>
Cc: devicetree-discuss@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org,
linux-c6x-dev@linux-c6x.org, linux-kernel@vger.kernel.org,
linux-mips@linux-mips.org, linux@openrisc.net,
linuxppc-dev@lists.ozlabs.org, microblaze-uclinux@itee.uq.edu.au,
x86@kernel.org, david.daney@cavium.com, benh@kernel.crashing.org,
bigeasy@linutronix.de, grant.likely@secretlab.ca,
paul.gortmaker@windriver.com, paulus@samba.org, hpa@zytor.com,
m.szyprowski@samsung.com, jonas@southpole.se,
linux@arm.linux.org.uk, nico@linaro.org, a-jacquiot@ti.com,
mingo@redhat.com, suzuki@in.ibm.com, mahesh@linux.vnet.ibm.com,
linus.walleij@linaro.org, arnd@arndb.de, msalter@redhat.com,
rob.herring@calxeda.com, tglx@linutronix.de, blogic@openwrt.org,
dhowells@redhat.com, monstr@monstr.eu, ralf@linux-mips.org,
tj@kernel.org
Subject: Re: [PATCH] of: specify initrd location using 64-bit
Date: Wed, 12 Sep 2012 19:45:57 -0400 [thread overview]
Message-ID: <50511EB5.800@ti.com> (raw)
Message-ID: <20120912234557.FAYoqF2DFj7zrzDnqgZaMCo4ZtirfLyhBI7H_kAroAY@z> (raw)
In-Reply-To: <5050EF3F.6030003@gmail.com>
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
WARNING: multiple messages have this Message-ID (diff)
From: Cyril Chemparathy <cyril@ti.com>
To: Rob Herring <robherring2@gmail.com>
Cc: linux-mips@linux-mips.org, x86@kernel.org,
david.daney@cavium.com, linux@openrisc.net,
paul.gortmaker@windriver.com, paulus@samba.org, hpa@zytor.com,
m.szyprowski@samsung.com, jonas@southpole.se,
linus.walleij@linaro.org, linux@arm.linux.org.uk,
linux-c6x-dev@linux-c6x.org, nico@linaro.org, a-jacquiot@ti.com,
mingo@redhat.com, suzuki@in.ibm.com, mahesh@linux.vnet.ibm.com,
bigeasy@linutronix.de, arnd@arndb.de,
microblaze-uclinux@itee.uq.edu.au,
devicetree-discuss@lists.ozlabs.org, msalter@redhat.com,
rob.herring@calxeda.com, tglx@linutronix.de,
linux-arm-kernel@lists.infradead.org, blogic@openwrt.org,
dhowells@redhat.com, monstr@monstr.eu,
linux-kernel@vger.kernel.org, ralf@linux-mips.org, tj@kernel.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] of: specify initrd location using 64-bit
Date: Wed, 12 Sep 2012 19:45:57 -0400 [thread overview]
Message-ID: <50511EB5.800@ti.com> (raw)
In-Reply-To: <5050EF3F.6030003@gmail.com>
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
WARNING: multiple messages have this Message-ID (diff)
From: cyril@ti.com (Cyril Chemparathy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] of: specify initrd location using 64-bit
Date: Wed, 12 Sep 2012 19:45:57 -0400 [thread overview]
Message-ID: <50511EB5.800@ti.com> (raw)
In-Reply-To: <5050EF3F.6030003@gmail.com>
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
WARNING: multiple messages have this Message-ID (diff)
From: Cyril Chemparathy <cyril@ti.com>
To: Rob Herring <robherring2@gmail.com>
Cc: devicetree-discuss@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org,
linux-c6x-dev@linux-c6x.org, linux-kernel@vger.kernel.org,
linux-mips@linux-mips.org, linux@openrisc.net,
linuxppc-dev@lists.ozlabs.org, microblaze-uclinux@itee.uq.edu.au,
x86@kernel.org, david.daney@cavium.com, benh@kernel.crashing.org,
bigeasy@linutronix.de, grant.likely@secretlab.ca,
paul.gortmaker@windriver.com, paulus@samba.org, hpa@zytor.com,
m.szyprowski@samsung.com, jonas@southpole.se,
linux@arm.linux.org.uk, nico@linaro.org, a-jacquiot@ti.com,
mingo@redhat.com, suzuki@in.ibm.com, mahesh@linux.vnet.ibm.com,
linus.walleij@linaro.org, arnd@arndb.de, msalter@redhat.com,
rob.herring@calxeda.com, tglx@linutronix.de, blogic@openwrt.orgd
Subject: Re: [PATCH] of: specify initrd location using 64-bit
Date: Wed, 12 Sep 2012 19:45:57 -0400 [thread overview]
Message-ID: <50511EB5.800@ti.com> (raw)
In-Reply-To: <5050EF3F.6030003@gmail.com>
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
next prev parent reply other threads:[~2012-09-12 23:47 UTC|newest]
Thread overview: 110+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-12 16:05 [PATCH] of: specify initrd location using 64-bit Cyril Chemparathy
2012-09-12 16:05 ` Cyril Chemparathy
2012-09-12 16:05 ` Cyril Chemparathy
2012-09-12 16:05 ` Cyril Chemparathy
2012-09-12 16:16 ` Geert Uytterhoeven
2012-09-12 16:16 ` Geert Uytterhoeven
2012-09-12 16:16 ` Geert Uytterhoeven
2012-09-12 18:02 ` Cyril Chemparathy
2012-09-12 18:02 ` Cyril Chemparathy
2012-09-12 18:02 ` Cyril Chemparathy
2012-09-12 18:02 ` Cyril Chemparathy
2012-09-12 18:02 ` Cyril Chemparathy
2012-09-12 19:58 ` Sebastian Andrzej Siewior
2012-09-12 19:58 ` Sebastian Andrzej Siewior
2012-09-12 19:58 ` Sebastian Andrzej Siewior
2012-09-12 22:08 ` Rob Herring
2012-09-12 22:08 ` Rob Herring
2012-09-12 22:08 ` Rob Herring
2012-09-13 6:47 ` Sebastian Andrzej Siewior
2012-09-13 6:47 ` Sebastian Andrzej Siewior
2012-09-13 6:47 ` Sebastian Andrzej Siewior
2012-09-13 21:02 ` Rob Herring
2012-09-13 21:02 ` Rob Herring
2012-09-13 21:02 ` Rob Herring
2012-09-12 20:23 ` Rob Herring
2012-09-12 20:23 ` Rob Herring
2012-09-12 20:23 ` Rob Herring
2012-09-12 20:31 ` Nicolas Pitre
2012-09-12 20:31 ` Nicolas Pitre
2012-09-12 20:31 ` Nicolas Pitre
2012-09-12 20:56 ` Rob Herring
2012-09-12 20:56 ` Rob Herring
2012-09-12 20:56 ` Rob Herring
2012-09-12 20:56 ` Rob Herring
2012-09-12 23:45 ` Cyril Chemparathy [this message]
2012-09-12 23:45 ` Cyril Chemparathy
2012-09-12 23:45 ` Cyril Chemparathy
2012-09-12 23:45 ` Cyril Chemparathy
2012-09-12 23:45 ` Cyril Chemparathy
-- strict thread matches above, loose matches on Subject: below --
2013-06-21 0:52 [PATCH] of: Specify " Santosh Shilimkar
2013-06-21 0:52 ` Santosh Shilimkar
2013-06-21 0:52 ` Santosh Shilimkar
2013-06-21 0:52 ` Santosh Shilimkar
2013-06-21 0:52 ` Santosh Shilimkar
2013-06-21 4:39 ` Vineet Gupta
2013-06-21 4:39 ` Vineet Gupta
2013-06-21 4:39 ` Vineet Gupta
2013-06-21 4:39 ` Vineet Gupta
2013-06-21 4:39 ` Vineet Gupta
2013-06-21 8:23 ` James Hogan
2013-06-21 8:23 ` James Hogan
2013-06-21 8:23 ` James Hogan
2013-06-21 8:23 ` James Hogan
2013-06-21 8:23 ` James Hogan
2013-06-21 17:12 ` Santosh Shilimkar
2013-06-21 17:12 ` Santosh Shilimkar
2013-06-21 17:12 ` Santosh Shilimkar
2013-06-21 17:12 ` Santosh Shilimkar
2013-06-21 17:12 ` Santosh Shilimkar
2013-06-21 9:04 ` Sebastian Andrzej Siewior
2013-06-21 9:04 ` Sebastian Andrzej Siewior
2013-06-21 9:04 ` Sebastian Andrzej Siewior
2013-06-21 9:04 ` Sebastian Andrzej Siewior
2013-06-21 17:20 ` Santosh Shilimkar
2013-06-21 17:20 ` Santosh Shilimkar
2013-06-21 17:20 ` Santosh Shilimkar
2013-06-21 17:20 ` Santosh Shilimkar
2013-06-21 17:20 ` Santosh Shilimkar
2013-06-27 20:54 ` Rob Herring
2013-06-27 20:54 ` Rob Herring
2013-06-27 20:54 ` Rob Herring
2013-06-27 20:54 ` Rob Herring
2013-06-28 7:54 ` Sebastian Andrzej Siewior
2013-06-28 7:54 ` Sebastian Andrzej Siewior
2013-06-28 7:54 ` Sebastian Andrzej Siewior
2013-06-28 7:54 ` Sebastian Andrzej Siewior
2013-06-28 9:59 ` Grant Likely
2013-06-28 9:59 ` Grant Likely
2013-06-28 9:59 ` Grant Likely
2013-06-28 9:59 ` Grant Likely
2013-06-28 13:49 ` Jean-Christophe PLAGNIOL-VILLARD
2013-06-28 13:49 ` Jean-Christophe PLAGNIOL-VILLARD
2013-06-28 13:49 ` Jean-Christophe PLAGNIOL-VILLARD
2013-06-28 13:49 ` Jean-Christophe PLAGNIOL-VILLARD
2013-06-28 23:43 ` Santosh Shilimkar
2013-06-28 23:43 ` Santosh Shilimkar
2013-06-28 23:43 ` Santosh Shilimkar
2013-06-28 23:43 ` Santosh Shilimkar
2013-06-28 23:43 ` Santosh Shilimkar
2013-06-29 8:34 ` Geert Uytterhoeven
2013-06-29 8:34 ` Geert Uytterhoeven
2013-06-29 8:34 ` Geert Uytterhoeven
2013-06-29 8:34 ` Geert Uytterhoeven
2013-07-01 7:48 ` Sebastian Andrzej Siewior
2013-07-01 7:48 ` Sebastian Andrzej Siewior
2013-07-01 7:48 ` Sebastian Andrzej Siewior
2013-07-01 7:48 ` Sebastian Andrzej Siewior
2013-07-01 7:59 ` Geert Uytterhoeven
2013-07-01 7:59 ` Geert Uytterhoeven
2013-07-01 7:59 ` Geert Uytterhoeven
2013-07-01 7:59 ` Geert Uytterhoeven
2013-07-01 8:09 ` Sebastian Andrzej Siewior
2013-07-01 8:09 ` Sebastian Andrzej Siewior
2013-07-01 8:09 ` Sebastian Andrzej Siewior
2013-07-01 8:09 ` Sebastian Andrzej Siewior
2013-07-01 13:58 ` Santosh Shilimkar
2013-07-01 13:58 ` Santosh Shilimkar
2013-07-01 13:58 ` Santosh Shilimkar
2013-07-01 13:58 ` Santosh Shilimkar
2013-07-01 13:58 ` Santosh Shilimkar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50511EB5.800@ti.com \
--to=cyril@ti.com \
--cc=a-jacquiot@ti.com \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=bigeasy@linutronix.de \
--cc=blogic@openwrt.org \
--cc=david.daney@cavium.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dhowells@redhat.com \
--cc=grant.likely@secretlab.ca \
--cc=hpa@zytor.com \
--cc=jonas@southpole.se \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-c6x-dev@linux-c6x.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux@arm.linux.org.uk \
--cc=linux@openrisc.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=m.szyprowski@samsung.com \
--cc=mahesh@linux.vnet.ibm.com \
--cc=microblaze-uclinux@itee.uq.edu.au \
--cc=mingo@redhat.com \
--cc=monstr@monstr.eu \
--cc=msalter@redhat.com \
--cc=nico@linaro.org \
--cc=paul.gortmaker@windriver.com \
--cc=paulus@samba.org \
--cc=ralf@linux-mips.org \
--cc=rob.herring@calxeda.com \
--cc=robherring2@gmail.com \
--cc=suzuki@in.ibm.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.