Re: [Xen-devel] Domain 0 crashed when booting OMAP5 uEVM

[Julien Grall <julien.grall@xxxxxxxxxx>]

On 08/12/2013 03:30 PM, Andrii Anisov wrote:
> 
> 
> 
>     > - Turning on paging -
>     > - Ready -
>     > fdt: node `cpu@0': invalid #address-cells or #size-cellsfdt: node
>     `cpu@1':
>     > - invalid #addref
> 
>     Hum ... this is why Xen can't find the other cpus. Could you paste the
>     content of the node cpus here?
> 
> 
> I bet, something like this:
> 
>         };
>  
>         cpus {
> +               #address-cells = <1>;
> +               #size-cells = <0>;
> +
>                 cpu@0 {
> +                       device_type = "cpu";
>                         compatible = "arm,cortex-a15";
> +                       reg = <0>;
>                         operating-points = <
>                                 /* kHz    uV */
>                                 /* Only for Nominal Samples */
> @@ -48,7 +53,9 @@
>                         clock-latency = <300000>; /* From omap-cpufreq
> driver */
>                 };
>                 cpu@1 {
> +                       device_type = "cpu";
>                         compatible = "arm,cortex-a15";
> +                       reg = <1>;
>                 };
>         };

I thought these nodes was a requirement in the device tree.
Xen relies on these nodes and I guess Linux plan to do the same thing
for multi-platform support.

Perhaps it's a patch to send upstream? :)

Cheers,

-- 
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel