summaryrefslogtreecommitdiff
path: root/arch/arm/boot/dts/bcm4708-netgear-r6250.dts
diff options
context:
space:
mode:
authorRafał Miłecki <rafal@milecki.pl>2016-12-07 08:56:54 +0100
committerFlorian Fainelli <f.fainelli@gmail.com>2017-01-18 17:18:03 -0800
commita252ccd3d2327556c6331e926abd82f4bfe4ce52 (patch)
treec5760e7105793ed781d957cffa78f16e170ed81e /arch/arm/boot/dts/bcm4708-netgear-r6250.dts
parent849af7f45862b7b059276c1d0333ac781861bd9c (diff)
downloadlwn-a252ccd3d2327556c6331e926abd82f4bfe4ce52.tar.gz
lwn-a252ccd3d2327556c6331e926abd82f4bfe4ce52.zip
ARM: dts: BCM5301X: Specify all RAM by including an extra block
The first 128 MiB of RAM can be accessed using an alias at address 0x0. In theory we could access whole RAM using 0x80000000 - 0xbfffffff range (up to 1 GiB) but it doesn't seem to work on Northstar. For some reason (hardware setup left by the bootloader maybe?) 0x80000000 - 0x87ffffff range can't be used. I reproduced this problem on: 1) Buffalo WZR-600DHP2 (BCM47081) 2) Netgear R6250 (BCM4708) 3) D-Link DIR-885L (BCM47094) So it seems we're forced to access first 128 MiB using alias at 0x0 and the rest using real base address + 128 MiB offset which is 0x88000000. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> Acked-by: Jon Mason <jon.mason@broadcom.com> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
Diffstat (limited to 'arch/arm/boot/dts/bcm4708-netgear-r6250.dts')
-rw-r--r--arch/arm/boot/dts/bcm4708-netgear-r6250.dts3
1 files changed, 2 insertions, 1 deletions
diff --git a/arch/arm/boot/dts/bcm4708-netgear-r6250.dts b/arch/arm/boot/dts/bcm4708-netgear-r6250.dts
index 8519548584f1..b9f66c0fae27 100644
--- a/arch/arm/boot/dts/bcm4708-netgear-r6250.dts
+++ b/arch/arm/boot/dts/bcm4708-netgear-r6250.dts
@@ -21,7 +21,8 @@
};
memory {
- reg = <0x00000000 0x08000000>;
+ reg = <0x00000000 0x08000000
+ 0x88000000 0x08000000>;
};
leds {