diff options
| author | Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com> | 2017-08-15 21:13:54 +0300 |
|---|---|---|
| committer | Vineet Gupta <vgupta@synopsys.com> | 2017-09-01 11:26:27 -0700 |
| commit | 9ed68785f7f2b001a6911d64fbd10cfc6fa49b27 (patch) | |
| tree | 57bf1ba37285d0a090eb52d24f15115f58d64e4f /arch/arc/boot/dts/axc001.dtsi | |
| parent | bee91c3a3ce63daf64bb53ae60e6a2fb2961d3d7 (diff) | |
| download | linux-9ed68785f7f2b001a6911d64fbd10cfc6fa49b27.tar.gz linux-9ed68785f7f2b001a6911d64fbd10cfc6fa49b27.tar.bz2 linux-9ed68785f7f2b001a6911d64fbd10cfc6fa49b27.zip | |
ARC: mm: Decouple RAM base address from kernel link address
[Needed for HSDK]
Currently the first page of system (hence RAM base) is assumed to be
@ CONFIG_LINUX_LINK_BASE, where kernel itself is linked.
However is case of HSDK platform, for reasons explained in that patch,
this is not true. kernel needs to be linked @ 0x9000_0000 while DDR
is still wired at 0x8000_0000. To properly account for this 256M of RAM,
we need to introduce a new option and base page frame accountiing off of
it.
Signed-off-by: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
Signed-off-by: Vineet Gupta <vgupta@synopsys.com>
[vgupta: renamed CONFIG_KERNEL_RAM_BASE_ADDRESS => CONFIG_LINUX_RAM_BASE
: simplified changelog]
Diffstat (limited to 'arch/arc/boot/dts/axc001.dtsi')
| -rw-r--r-- | arch/arc/boot/dts/axc001.dtsi | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/arc/boot/dts/axc001.dtsi b/arch/arc/boot/dts/axc001.dtsi index a380ffa1a458..fdc266504ada 100644 --- a/arch/arc/boot/dts/axc001.dtsi +++ b/arch/arc/boot/dts/axc001.dtsi @@ -99,7 +99,7 @@ memory { device_type = "memory"; - /* CONFIG_KERNEL_RAM_BASE_ADDRESS needs to match low mem start */ + /* CONFIG_LINUX_RAM_BASE needs to match low mem start */ reg = <0x0 0x80000000 0x0 0x1b000000>; /* (512 - 32) MiB */ }; |