summaryrefslogtreecommitdiff
path: root/tests/fdtdump.dts
diff options
context:
space:
mode:
authorSimon Glass <sjg@chromium.org>2014-06-18 21:24:32 +1000
committerDavid Gibson <david@gibson.dropbear.id.au>2014-06-18 21:24:48 +1000
commit76a65b14d1bb10f300f518c11aed231575521c2e (patch)
tree08db9c0d2b4e7c032e03a17401dec2071c4045d9 /tests/fdtdump.dts
parentc78ca72e1e89714a7a62a85035e5c505c8ba51f0 (diff)
downloaddevice-tree-compiler-76a65b14d1bb10f300f518c11aed231575521c2e.tar.gz
Add a basic test for fdtdump
We can test fdtdump by comparing its output with the source file that was compiled by dtc. Add a simple test that should at least catch regressions in basic functionality. Signed-off-by: Simon Glass <sjg@chromium.org> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Diffstat (limited to 'tests/fdtdump.dts')
-rw-r--r--tests/fdtdump.dts37
1 files changed, 37 insertions, 0 deletions
diff --git a/tests/fdtdump.dts b/tests/fdtdump.dts
new file mode 100644
index 0000000..b9d917b
--- /dev/null
+++ b/tests/fdtdump.dts
@@ -0,0 +1,37 @@
+/dts-v1/;
+
+/memreserve/ 0 0xe;
+/ {
+ model = "MyBoardName";
+ compatible = "MyBoardName", "MyBoardFamilyName";
+ #address-cells = <0x00000002>;
+ #size-cells = <0x00000002>;
+ cpus {
+ linux,phandle = <0x00000001>;
+ #address-cells = <0x00000001>;
+ #size-cells = <0x00000000>;
+ PowerPC,970@0 {
+ device_type = "cpu";
+ reg = <0x00000000>;
+ linux,boot-cpu;
+ };
+ PowerPC,970@1 {
+ device_type = "cpu";
+ reg = <0x00000001>;
+ };
+ };
+ randomnode {
+ string = "foo", "stuff";
+ bytes = [61 62 63 64 65];
+ child {
+ };
+ };
+ memory@0 {
+ device_type = "memory";
+ reg = <0x00000000 0x00000123 0x00000456 0x87654321>;
+ };
+ chosen {
+ bootargs = "root=/dev/sda2";
+ linux,platform = <0x00000600>;
+ };
+};