From: grant.likely@linaro.org (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] of: Specify initrd location using 64-bit
Date: Sat, 20 Jul 2013 06:39:45 +0100 [thread overview]
Message-ID: <20130720053945.C7AC63E0C52@localhost> (raw)
In-Reply-To: <51D1F5E2.6070609@gmail.com>
On Mon, 01 Jul 2013 16:34:26 -0500, Rob Herring <robherring2@gmail.com> 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 numbers.
> >
> > This patch globally modifies the early_init_dt_setup_initrd_arch() function to
> > use 64-bit numbers instead of the current unsigned long.
> >
> > There has been quite a bit of debate about whether to use u64 or phys_addr_t.
> > It was concluded to stick to u64 to be consistent with rest of the device
> > tree code. As summarized by Geert, "The address to load the initrd is decided
> > by the bootloader/user and set at that point later in time. The dtb should not
> > be tied to the kernel you are booting"
>
> That was quoting me. Otherwise:
>
> Acked-by: Rob Herring <rob.herring@calxeda.com>
>
> Unless Grant feels compelled to pick this up for 3.11, I think it has to
> wait for 3.12.
Nope, 3.12 is fine. Applied.
g.
next prev parent reply other threads:[~2013-07-20 5:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-01 18:20 [PATCH v2] of: Specify initrd location using 64-bit Santosh Shilimkar
2013-07-01 21:34 ` Rob Herring
2013-07-20 5:39 ` Grant Likely [this message]
2013-07-22 14:50 ` Santosh Shilimkar
2013-07-02 4:17 ` Vineet Gupta
2013-07-22 15:01 ` Jean-Christophe PLAGNIOL-VILLARD
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=20130720053945.C7AC63E0C52@localhost \
--to=grant.likely@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).