On Thu, Jul 28, 2016 at 7:26 AM, Alistair Francis <[email protected]> wrote: > This device tree is required by QEMU to describe the ZCU102 board. > > Signed-off-by: Alistair Francis <[email protected]> > --- > .../device-tree/files/qemu/qemuzcu102-arm.dts | 2410 > ++++++++++++++++++++ > 1 file changed, 2410 insertions(+) > create mode 100644 recipes-bsp/device-tree/files/qemu/qemuzcu102-arm.dts > > diff --git a/recipes-bsp/device-tree/files/qemu/qemuzcu102-arm.dts > b/recipes-bsp/device-tree/files/qemu/qemuzcu102-arm.dts > new file mode 100644 > index 0000000..a7f2fbb > --- /dev/null > +++ b/recipes-bsp/device-tree/files/qemu/qemuzcu102-arm.dts
Such a large device tree like this is going to be hard to maintain. Is there overlap between this qemu specific DT and the kernel includes? if possible it would be very useful to be including what you can from the zynqmp.dtsi. Also generally I like to avoid the dtc decompiled devicetrees as they are hard to read (e.g. phandles are int's, ints are formatted to hex, etc.). Please try to provide the device tree source(s) if possible. Alternatively you can also provide this as a blob from the QEMU sources if that works better? It would allow the tying of QEMU support to the device tree (aka not having to modify meta-xilinx every time you modify QEMU bindings). Something similar is used for the qemumicroblaze machines. Regards, Nathan -- trimmed content -- -- _______________________________________________ meta-xilinx mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-xilinx
