tree: fddaacf4a6eaa79b106dd138bc4005da3edcf2ee [path history] [tgz]
  1. synthetic/
  2. banana-pi-f3.dtb
  3. banana-pi-f3.dts
  4. BUILD.gn
  5. crosvm-arm.dtb
  6. crosvm-arm.dts
  7. khadas-vim3.dtb
  8. khadas-vim3.dts
  9. muntjac.dtb
  10. muntjac.dts
  11. qemu-arm-gic2.dtb
  12. qemu-arm-gic2.dts
  13. qemu-arm-gic3.dtb
  14. qemu-arm-gic3.dts
  15. qemu-riscv.dtb
  16. qemu-riscv.dts
  17. README.md
  18. sifive-hifive-unmatched.dtb
  19. sifive-hifive-unmatched.dts
  20. vision-five-2.dtb
  21. vision-five-2.dts
zircon/kernel/lib/devicetree/testing/data/README.md

Devicetree Data

This directory contains devicetree source (.dts) and binary (.dtb) files for use in devicetree tests. Every ‘dtb’ file is obtained from a device, and the respective ‘.dts’ file is decompiled from the binary format.

It is important that ‘dtb’s in this directory reflect the contents of real or virtual hardware. This blobs may be constructed by bootloaders, may be broken in different ways and recompiling them from the decompiled ‘dts’ is not guaranteed to provide bit-for-bit equality.

When adding a new binary file, it shall be named after the board and include any meaningul information, such as ‘qemu-gic3’. Added files should be decompiled using the devicetree compiler application, and submitted together with the corresponding binary file.

Devicetree Synthetic Data

The ‘synthetic’ directory contains devicetree source (.dts) for use in devicetree tests. Unlike the data contained in this directory, the synthetic ‘dtb’ are compiled from handwritten ‘dts’ files.