Thread (2 messages) flat view 2 messages, 2 authors, 2012-07-12
DORMANTno replies REVIEWED: 1 (0M)

1 review trailer.

[PATCH v2] arm: Handle >4GB memory sizes in device tree and mem=size@start option

From: Will Deacon <hidden>
Date: 2012-07-12 16:36:24

On Wed, Jul 11, 2012 at 10:39:48AM +0100, Peter Maydell wrote:
The memory regions which are passed to arm_add_memory() from
device tree blobs via early_init_dt_add_memory_arch() can
have sizes which are larger than will fit in a 32 bit integer,
so switch to using a phys_addr_t to hold them, to avoid
silently dropping the top 32 bits of the size. Similarly, use
phys_addr_t in early_mem() so that mem=size at start command line
options specifying more than 4GB behave sensibly.

Signed-off-by: Peter Maydell <redacted>
---
Changes v1->v2:
 * fixed spacing round '-'
 * made early_mem() handle large sizes too
Acked-by: Will Deacon <redacted>

Please can you put this into the patch system?

Will
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help