summaryrefslogtreecommitdiffstats
path: root/Documentation/usb
diff options
context:
space:
mode:
authorSantosh Shilimkar <santosh.shilimkar@ti.com>2013-07-01 14:20:35 -0400
committerGrant Likely <grant.likely@linaro.org>2013-07-24 11:10:01 +0100
commit374d5c9964c10373ba39bbe934f4262eb87d7114 (patch)
tree3ddcb05c32181506d7619d6bffedaa53aee2fc95 /Documentation/usb
parentdcde863297256a9cade5422a2d469ba828f60beb (diff)
downloadop-kernel-dev-374d5c9964c10373ba39bbe934f4262eb87d7114.zip
op-kernel-dev-374d5c9964c10373ba39bbe934f4262eb87d7114.tar.gz
of: Specify initrd location using 64-bit
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" More details on the discussion can be found here: https://lkml.org/lkml/2013/6/20/690 https://lkml.org/lkml/2012/9/13/544 Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com> Acked-by: Rob Herring <rob.herring@calxeda.com> Acked-by: Vineet Gupta <vgupta@synopsys.com> Acked-by: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com> Signed-off-by: Grant Likely <grant.likely@linaro.org>
Diffstat (limited to 'Documentation/usb')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud