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
28 /sys/firmware/qemu_fw_cfg/
32 /sys/firmware/qemu_fw_cfg/rev
40 /sys/firmware/qemu_fw_cfg/by_key/32
41 /sys/firmware/qemu_fw_cfg/by_key/33
42 /sys/firmware/qemu_fw_cfg/by_key/34
49 name The 56-byte nul-terminated ASCII string used as the
50 blob's 'file name' in the fw_cfg directory.
55 the parent directory name.
62 **Listing fw_cfg blobs by file name**
66 QEMU developers have traditionally used path name semantics
67 to give each blob a descriptive name. For example::
72 "etc/boot-fail-wait"
73 "etc/system-states"
74 "etc/table-loader"
77 "etc/smbios/smbios-tables"
78 "etc/smbios/smbios-anchor"
83 of directories matching the path name components of fw_cfg
86 /sys/firmware)::
88 qemu_fw_cfg/by_name/bootorder -> ../by_key/38
89 qemu_fw_cfg/by_name/etc/e820 -> ../../by_key/35
90 qemu_fw_cfg/by_name/etc/acpi/rsdp -> ../../../by_key/41
94 "best-effort" basis, as there is no guarantee that components
98 creation of the offending /sys/firmware/qemu_fw_cfg/by_name
102 under the /sys/firmware/qemu_fw_cfg/by_key directory.