Alistair Popple <apopple@xxxxxxxxxxx> writes: > Hi Reza, > > On Thu, 6 Oct 2016 01:36:32 PM Reza Arbab wrote: >> Respect the standard dt "status" property when scanning memory nodes in >> early_init_dt_scan_memory(), so that if the node is unavailable, no >> memory will be added. > > What happens if a kernel without this patch is booted on a system with some > status="disabled" device-nodes? Do older kernels just ignore this memory or do > they try to use it? > > From what I can tell it seems that kernels without this patch will try and use > this memory even if it is marked in the device-tree as status="disabled" which > could lead to problems for older kernels when we start exporting this property > from firmware. The code already looks for "linux,usable-memory" in preference to "reg". Can you use that instead? That would have the advantage that existing kernels already understand it. Another problem with using "status" is we could have device trees out there that have status = disabled and we don't know about it, and by changing the kernel to use that property we break people's systems. Though for memory nodes my guess is that's not true, but you never know ... cheers -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
