Lines Matching +full:firmware +full:- +full:name
1 What: /sys/firmware/qemu_fw_cfg/
6 sun4*, ppc/mac) are provisioned with a firmware configuration
8 provide configuration data to the guest firmware. Starting
11 useful as an out-of-band, asynchronous mechanism for providing
14 The authoritative guest-side hardware interface documentation
17 https://qemu-project.gitlab.io/qemu/specs/fw_cfg.html
29 /sys/firmware/qemu_fw_cfg/
33 /sys/firmware/qemu_fw_cfg/rev
41 /sys/firmware/qemu_fw_cfg/by_key/32
42 /sys/firmware/qemu_fw_cfg/by_key/33
43 /sys/firmware/qemu_fw_cfg/by_key/34
50 name The 56-byte nul-terminated ASCII string used as the
51 blob's 'file name' in the fw_cfg directory.
56 the parent directory name.
63 **Listing fw_cfg blobs by file name**
67 QEMU developers have traditionally used path name semantics
68 to give each blob a descriptive name. For example::
73 "etc/boot-fail-wait"
74 "etc/system-states"
75 "etc/table-loader"
78 "etc/smbios/smbios-tables"
79 "etc/smbios/smbios-anchor"
84 of directories matching the path name components of fw_cfg
87 /sys/firmware)::
89 qemu_fw_cfg/by_name/bootorder -> ../by_key/38
90 qemu_fw_cfg/by_name/etc/e820 -> ../../by_key/35
91 qemu_fw_cfg/by_name/etc/acpi/rsdp -> ../../../by_key/41
95 "best-effort" basis, as there is no guarantee that components
99 creation of the offending /sys/firmware/qemu_fw_cfg/by_name
103 under the /sys/firmware/qemu_fw_cfg/by_key directory.