From: Rob Herring <robherring2@gmail•com>
To: Nicolas Pitre <nicolas.pitre@linaro•org>
Cc: linux-mips@linux-mips•org, x86@kernel•org,
david.daney@cavium•com, bigeasy@linutronix•de,
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, a-jacquiot@ti•com,
mahesh@linux•vnet.ibm.com, mingo@redhat•com, suzuki@in•ibm.com,
Cyril Chemparathy <cyril@ti•com>,
linux@openrisc•net, 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 15:56:24 -0500 [thread overview]
Message-ID: <5050F6F8.6000008@gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1209121629260.28681@xanadu.home>
On 09/12/2012 03:31 PM, Nicolas Pitre wrote:
> On Wed, 12 Sep 2012, 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?
>>
>>> ---
>>> arch/arm/mm/init.c | 2 +-
>>> arch/c6x/kernel/devicetree.c | 3 +--
>>> arch/microblaze/kernel/prom.c | 3 +--
>>> arch/mips/kernel/prom.c | 3 +--
>>> arch/openrisc/kernel/prom.c | 3 +--
>>> arch/powerpc/kernel/prom.c | 3 +--
>>> arch/x86/kernel/devicetree.c | 3 +--
>>> drivers/of/fdt.c | 10 ++++++----
>>> include/linux/of_fdt.h | 3 +--
>>> 9 files changed, 14 insertions(+), 19 deletions(-)
>>>
>>> diff --git a/arch/arm/mm/init.c b/arch/arm/mm/init.c
>>> index ad722f1..579792c 100644
>>> --- 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.
>
> size ?
phys_initrd_size. Arguably, we'll never have a >4GB initrd with a PAE
system or perhaps run into other issues first (like space to decompress
it), but technically the DTS could specify one.
Rob
next prev parent reply other threads:[~2012-09-12 20:56 UTC|newest]
Thread overview: 27+ 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:16 ` Geert Uytterhoeven
2012-09-12 18:02 ` Cyril Chemparathy
2012-09-12 19:58 ` Sebastian Andrzej Siewior
2012-09-12 22:08 ` Rob Herring
2012-09-13 6:47 ` Sebastian Andrzej Siewior
2012-09-13 21:02 ` Rob Herring
2012-09-12 20:23 ` Rob Herring
2012-09-12 20:31 ` Nicolas Pitre
2012-09-12 20:56 ` Rob Herring [this message]
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 4:39 ` Vineet Gupta
2013-06-21 8:23 ` James Hogan
2013-06-21 17:12 ` Santosh Shilimkar
2013-06-21 9:04 ` Sebastian Andrzej Siewior
2013-06-21 17:20 ` Santosh Shilimkar
2013-06-27 20:54 ` Rob Herring
2013-06-28 7:54 ` Sebastian Andrzej Siewior
2013-06-28 9:59 ` Grant Likely
2013-06-28 13:49 ` Jean-Christophe PLAGNIOL-VILLARD
2013-06-28 23:43 ` Santosh Shilimkar
2013-06-29 8:34 ` Geert Uytterhoeven
2013-07-01 7:48 ` Sebastian Andrzej Siewior
2013-07-01 7:59 ` Geert Uytterhoeven
2013-07-01 8:09 ` Sebastian Andrzej Siewior
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=5050F6F8.6000008@gmail.com \
--to=robherring2@gmail$(echo .)com \
--cc=a-jacquiot@ti$(echo .)com \
--cc=arnd@arndb$(echo .)de \
--cc=bigeasy@linutronix$(echo .)de \
--cc=blogic@openwrt$(echo .)org \
--cc=cyril@ti$(echo .)com \
--cc=david.daney@cavium$(echo .)com \
--cc=devicetree-discuss@lists$(echo .)ozlabs.org \
--cc=dhowells@redhat$(echo .)com \
--cc=hpa@zytor$(echo .)com \
--cc=jonas@southpole$(echo .)se \
--cc=linus.walleij@linaro$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-c6x-dev@linux-c6x$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mips@linux-mips$(echo .)org \
--cc=linux@arm$(echo .)linux.org.uk \
--cc=linux@openrisc$(echo .)net \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=m.szyprowski@samsung$(echo .)com \
--cc=mahesh@linux$(echo .)vnet.ibm.com \
--cc=microblaze-uclinux@itee$(echo .)uq.edu.au \
--cc=mingo@redhat$(echo .)com \
--cc=monstr@monstr$(echo .)eu \
--cc=msalter@redhat$(echo .)com \
--cc=nicolas.pitre@linaro$(echo .)org \
--cc=paul.gortmaker@windriver$(echo .)com \
--cc=paulus@samba$(echo .)org \
--cc=ralf@linux-mips$(echo .)org \
--cc=rob.herring@calxeda$(echo .)com \
--cc=suzuki@in$(echo .)ibm.com \
--cc=tglx@linutronix$(echo .)de \
--cc=tj@kernel$(echo .)org \
--cc=x86@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox