[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Bug in devicetree_for_each_node() in xen/arch/arm/bootfdt.c ?
Hi, On 23/06/2015 10:44, David Vrabel wrote: On 23/06/15 00:02, Chris (Christopher) Brand wrote:I’ve been trying to figure out why Xen only reports 2GB on my ARM platform that actually has 3GB, and I think I’ve found a bug, but I’m not familiar enough with the Xen code to fix it. The relevant parts of my dts are: /dts-v1/; / { model = "Broadcom STB (7445d0)"; compatible = "brcm,bcm7445d0", "brcm,brcmstb"; #address-cells = <0x2>; #size-cells = <0x2>; interrupt-parent = <0x1>; memory { #address-cells = <0x1>; #size-cells = <0x1>; device_type = "memory"; reg = <0x0 0x0 0x0 0x40000000 0x0 0x40000000 0x0 0x40000000>;It's been a while since I've looked at device tree stuff but I think you need 64-bit values for this reg property because the parent node has #address-cells == 0x2 and #size-cells == 0x2. I think they are already on 64-bit values, otherwise you would have a bank starting at 0 of a size 0 which seems odd. Anyway, the format of this memory node is not supported on Xen and I wasn't able to find a bindings somewhere. Will extend my point by answering to his mail. Cheers, -- Julien Grall _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |