aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/ramips/dts/mt7621_wevo_w2914ns-v2.dts
diff options
context:
space:
mode:
authorChuanhong Guo <gch981213@gmail.com>2019-07-10 11:05:41 +0800
committerChuanhong Guo <gch981213@gmail.com>2019-07-11 22:11:21 +0800
commit6d91ddf5175d2eac3c4bc4a404cc0f5dd44cf25b (patch)
tree16eb15416091742ef88a4d8727fd89b4a7e8d4af /target/linux/ramips/dts/mt7621_wevo_w2914ns-v2.dts
parent98d04dc4cf8b7ca9183a75566b299e0ccfac5a68 (diff)
downloadupstream-6d91ddf5175d2eac3c4bc4a404cc0f5dd44cf25b.tar.gz
upstream-6d91ddf5175d2eac3c4bc4a404cc0f5dd44cf25b.tar.bz2
upstream-6d91ddf5175d2eac3c4bc4a404cc0f5dd44cf25b.zip
ramips: mt7621: add support for memory detection
mt7621 has the following memory map: 0x0-0x1c000000: lower 448m memory 0x1c000000-0x2000000: peripheral registers 0x20000000-0x2400000: higher 64m memory detect_memory_region in arch/mips/kernel/setup.c only add the first memory region and isn't suitable for 512m memory detection because it may accidentally read the memory area for peripheral registers. This commit adds memory detection capability for mt7621: 1. add the highmem area when 512m is detected. 2. guard memcmp from accessing peripheral registers: This only happens when some weird user decided to change kernel load address to 256m or higher address. Since this is a quite unusual case, we just skip 512m testing and return 256m as memory size. Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
Diffstat (limited to 'target/linux/ramips/dts/mt7621_wevo_w2914ns-v2.dts')
0 files changed, 0 insertions, 0 deletions