summaryrefslogtreecommitdiffstats
path: root/fs/no-block.c
diff options
context:
space:
mode:
authorSrinivas Kandagatla <srinivas.kandagatla@linaro.org>2014-09-23 10:59:09 +0100
committerGrant Likely <grant.likely@linaro.org>2014-09-25 11:55:50 +0100
commit9aacd602f0246f1b1f3c4684b2ab13d0772976f7 (patch)
tree63b98dd512853323f19b82ec7a67fa2fd266cde1 /fs/no-block.c
parent8f73d4b7011061f46ba6f46006b2848b412ff43f (diff)
downloadtalos-obmc-linux-9aacd602f0246f1b1f3c4684b2ab13d0772976f7.tar.gz
talos-obmc-linux-9aacd602f0246f1b1f3c4684b2ab13d0772976f7.zip
of/fdt: fix memory range check
In cases where board has below memory DT node memory{ device_type = "memory"; reg = <0x80000000 0x80000000>; }; Check on the memory range in fdt.c will always fail because it is comparing MAX_PHYS_ADDR with base + size, in fact it should compare it with base + size - 1. This issue was originally noticed on Qualcomm IFC6410 board. Without this patch kernel shows up noticed unnecessary warnings [ 0.000000] Machine model: Qualcomm APQ8064/IFC6410 [ 0.000000] Ignoring memory range 0xffffffff - 0x100000000 [ 0.000000] cma: Reserved 64 MiB at ab800000 as a result the size get reduced to 0x7fffffff which looks wrong. This patch fixes the check involved in generating this warning and as a result it also fixes the wrong size calculation. Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org> [grant.likely: adjust new size calculation also] Signed-off-by: Grant Likely <grant.likely@linaro.org>
Diffstat (limited to 'fs/no-block.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud