Lines Matching refs:fw_cfg
2 QEMU Firmware Configuration (fw_cfg) Device
37 As of QEMU v2.4, writes to the fw_cfg data register are no
100 The fw_cfg device is defined with ACPI ID ``QEMU0002``. Since we expect
101 ACPI tables to be passed into the guest through the fw_cfg device itself,
102 the guest-side firmware can not use ACPI to find fw_cfg. However, once the
104 guest kernel, the latter can use the fw_cfg ACPI node for a more accurate
113 The presence of the fw_cfg selector and data registers can be verified
115 and reading four bytes from the data register. If the fw_cfg device is
138 and retrieve them. The format of this file directory (from ``fw_cfg.h`` in
141 struct FWCfgFiles { /* the entire file directory fw_cfg item */
147 uint32_t size; /* size of referenced fw_cfg item, big-endian */
148 uint16_t select; /* selector key of fw_cfg item, big-endian */
150 char name[56]; /* fw_cfg item name, NUL-terminated ascii */
183 not replace the existing fw_cfg interface, it is an add-on. This interface
247 Since v2.4, "file" fw_cfg items (i.e., items with selector keys above
248 ``FW_CFG_FILE_FIRST``, and with a corresponding entry in the fw_cfg file
252 -fw_cfg [name=]<item_name>,file=<path>
256 -fw_cfg [name=]<item_name>,string=<string>
258 Since v5.1, QEMU allows some objects to generate fw_cfg-specific content,
263 -fw_cfg [name=]<item_name>,gen_id=<generated_id>
290 All externally provided fw_cfg items are read-only to the guest.