1 What: /sys/firmware/devicetree/*
2 Date: November 2013
3 Contact: Grant Likely <grant.likely@arm.
4 Description:
5 When using OpenFirmware or a F
6 hardware, the device tree stru
7 directory.
8
9 It is possible for multiple de
10 Some device drivers use a sepa
11 have no attachment to the syst
12 different subdirectory under /
13
14 Userspace must not use the /sy
15 path directly, but instead sho
16 symlink. It is possible that t
17 in the future, but the symlink
18
19 The /proc/device-tree symlink
20 filesystem support, and has la
21 should be compatible with exis
22
23 The contents of /sys/firmware/
24 hierarchy of directories, one
25 directory name is the resolved
26 name plus address). Properties
27 in the directory. The contents
28 binary data from the device tr
29
30 What: /sys/firmware/fdt
31 Date: February 2015
32 KernelVersion: 3.19
33 Contact: Frank Rowand <frowand.list@gmai
34 Description:
35 Exports the FDT blob that was
36 the bootloader. This allows us
37 as kexec to access the raw bin
38 useful when debugging since it
39 made to the blob by the bootlo
40
41 The fact that this node does n
42 /sys/firmware/device-tree is d
43 on arm64 UEFI/ACPI systems to
44 and ACPI entry points, but the
45 and used to configure the syst
46
47 A CRC32 checksum is calculated
48 blob, and verified at late_ini
49 entry is instantiated only if
50 i.e., if the FDT blob has not
51 time. Otherwise, a warning is
52 Users: kexec, debugging
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.