Home
last modified time | relevance | path

Searched refs:firmware (Results 1 – 25 of 126) sorted by relevance

123456

/qemu/docs/interop/
A Dfirmware.json25 # Lists the firmware-OS interface types provided by various firmware
69 # firmware files.
114 # requirements that firmware may present.
196 # @verbose-dynamic: When firmware log capture is enabled, the firmware
250 # firmware file can be found.
344 # @filename: Identifies the firmware executable. The firmware executable
360 # @filename: Identifies the firmware executable. The firmware executable
391 # Describes a firmware (or a firmware use case) to management software.
404 # - /usr/share/qemu/firmware -- populated by distro-provided firmware
436 # $ vim /etc/qemu/firmware/50-ovmf.json
[all …]
/qemu/docs/devel/migration/
A Dbest-practices.rst30 on the destination it includes the firmware from the source. Even after
31 resetting a VM, the old firmware is used. Only once QEMU has been restarted
32 is the new firmware in use.
34 - Changes in firmware size can cause changes in the required RAMBlock size
35 to hold the firmware and thus migration can fail. In practice it's best
36 to pad firmware images to convenient powers of 2 with plenty of space
40 emulation code can work with older firmware to allow forward migration.
42 - Care should be taken with newer firmware so that backward migration
45 In some cases it may be best to tie specific firmware versions to specific
47 support. This is also useful when newer versions of firmware outgrow
/qemu/hw/avr/
A Dboot.c61 MemoryRegion *program_mr, const char *firmware) in avr_load_firmware() argument
68 filename = qemu_find_file(QEMU_FILE_TYPE_BIOS, firmware); in avr_load_firmware()
70 error_report("Unable to find %s", firmware); in avr_load_firmware()
88 firmware, entry); in avr_load_firmware()
94 firmware, cpu_len, mcu_cpu_type); in avr_load_firmware()
101 firmware, in avr_load_firmware()
111 firmware); in avr_load_firmware()
A Darduino.c51 if (machine->firmware) { in DECLARE_OBJ_CHECKERS()
53 &ams->mcu.flash, machine->firmware)) { in DECLARE_OBJ_CHECKERS()
/qemu/docs/system/
A Dbootindex.rst4 QEMU can tell QEMU-aware guest firmware (like the x86 PC BIOS)
12 firmware will consider devices for booting the guest OS. If the
44 Given the command above, firmware should try to boot from the e1000 NIC
51 Some firmware has limitations on which devices can be considered for
58 Sometimes, firmware cannot map the device path QEMU wants firmware to
59 boot from to a boot method. It doesn't happen for devices the firmware
60 can natively boot from, but if firmware relies on an option ROM for
62 device, the firmware may not be able to ask the option ROM to boot from
74 firmware implementations normally either support the one or the other,
76 undefined behavior, and thus the guest firmware will likely not boot
A Dtarget-riscv.rst30 operating system or firmware images intended to run on one machine
74 RISC-V CPU firmware
78 firmware boot options:
83 will load the default OpenSBI firmware automatically. The firmware is included
89 QEMU will not automatically load any firmware. It is up to the user to load all
94 Tells QEMU to load the specified file as the firmware.
/qemu/pc-bios/
A DREADME8 firmware implementation. The goal is to implement a 100% IEEE
9 1275-1994 (referred to as Open Firmware) compliant firmware.
19 - VOF (Virtual Open Firmware) is a minimalistic firmware to work with
20 -machine pseries,x-vof=on. When enabled, the firmware acts as a slim shim and
42 (OpenPower Abstraction Layer) firmware for OpenPOWER systems. It can
49 - The "edk2-*.fd.bz2" images are platform firmware binaries and matching UEFI
53 were built at git tag "edk2-stable202302". The firmware binaries bundle parts
60 which conform to the "docs/interop/firmware.json" schema.
65 supported platforms, OpenSBI provides several runtime firmware examples.
79 - hppa-firmware.img (32-bit) and hppa-firmware64.img (64-bit) are firmware
/qemu/docs/system/arm/
A Dsbsa.rst13 specification defines how the firmware reports that to any operating system.
15 It is intended to be a machine for developing firmware and testing
33 Board to firmware interface
37 firmware for non-discoverable information about system components. This
39 (i.e. CPUs and memory). As a result it must have a firmware specifically built
45 QEMU provides the guest EL3 firmware with minimal information about hardware
47 not even a firmware devicetree.
70 The platform version is only for informing platform firmware about
A Db-l475e-iot01a.rst41 option to load a firmware. Example:
45 $ qemu-system-arm -M b-l475e-iot01a -kernel firmware.bin
/qemu/docs/system/ppc/
A Damigang.rst14 firmware to support AmigaOS 4.
28 A firmware binary is necessary for the boot process. It is a modified
39 The BIOS emulator in the firmware is unable to run QEMU‘s standard
57 From the firmware menu that appears select ``Boot sequence`` →
100 emulator in the firmware binary is unable to run QEMU‘s standard
109 At the firmware ``ok`` prompt enter ``boot cd install/pegasos``.
112 firmware ROM using the QEMU built-in minimal Virtual Open Firmware
133 The board has a firmware based on an older U-Boot version with
134 modifications to support booting AmigaOS 4. The firmware ROM is
A Dpowermac.rst33 (GPL v2) portable firmware implementation. The goal is to implement a
34 100% IEEE 1275-1994 (referred to as Open Firmware) compliant firmware.
/qemu/docs/specs/
A Dtpm.rst93 To support measurement logs to be written by the firmware,
95 buffer where the firmware can write its log into. For TPM 2 only a
113 requests and the actions the firmware has to take. The system
114 administrator passes the operation request number to the firmware
116 location that the firmware knows. Upon reboot, the firmware finds the
117 number and sends commands to the TPM. The firmware writes the TPM
122 operations for the firmware to implement. The ACPI interface also
163 | | | | firmware. Used by firmware. |
228 firmware, certain commands, e.g. ``TPM_Startup()``, sent by the
230 the firmware should not use the TPM.
[all …]
A Dacpi_hest_ghes.rst74 (4) QEMU generates the ACPI linker/loader script for the firmware. The
75 firmware pre-allocates memory for "etc/acpi/tables", "etc/hardware_errors"
86 (7) QEMU generates N ADD_POINTER commands for the firmware, which patch
91 "etc/hardware_errors_addr". Through that blob, the firmware can send back
94 for the firmware. The firmware will write back the start address of
A Dppc-spapr-hcalls.rst14 calls which are mostly used as a private interface between the firmware
24 generally provided by the firmware inside the guest to the operating system. It
30 "firmware" blob in the guest is a small stub of a few instructions which
57 This is typically used by the firmware running in the guest.
66 is used by our SLOF firmware to invert the screen.
A Dsev-guest-firmware.rst8 The guest firmware image (OVMF) may contain some configuration entries
10 GUIDed table at a known location in the firmware image. QEMU parses
11 this table when it loads the firmware image into memory, and then QEMU
31 The edk2 firmware code that constructs this structure is in the
119 table describing the hashes of certain firmware configuration device
A Dfw_cfg.rst9 (blobs) that can influence how the firmware configures itself, or may
22 A write to this register sets the index of a firmware configuration
67 The data register allows access to an array of bytes for each firmware
75 Each firmware configuration item has a maximum length of data
81 N bytes of the selected firmware configuration item, as a substring, in
102 the guest-side firmware can not use ACPI to find fw_cfg. However, once the
103 firmware is finished setting up ACPI tables and hands control over to the
137 structure, which makes it easier for guest-side firmware to identify
162 Theoretically, there may be up to 0x4000 generic firmware configuration
214 upper 16 bits are interpreted as an index of a firmware configuration item.
[all …]
/qemu/hw/m68k/
A Dmcf5208.c345 if (machine->firmware) { in mcf5208evb_init()
349 fn = qemu_find_file(QEMU_FILE_TYPE_BIOS, machine->firmware); in mcf5208evb_init()
351 error_report("Could not find ROM image '%s'", machine->firmware); in mcf5208evb_init()
355 error_report("Could not load ROM image '%s'", machine->firmware); in mcf5208evb_init()
367 if (qtest_enabled() || machine->firmware) { in mcf5208evb_init()
/qemu/hw/ppc/
A Damigaone.c107 if (!machine->firmware) { in amigaone_init()
112 machine->firmware); in amigaone_init()
114 error_report("Could not find firmware '%s'", machine->firmware); in amigaone_init()
A Dppc405_boards.c286 if (machine->firmware) { in ppc405_init()
289 machine->firmware); in ppc405_init()
296 error_report("Could not find firmware '%s'", machine->firmware); in ppc405_init()
304 error_report("Could not load PowerPC BIOS '%s'", machine->firmware); in ppc405_init()
313 if (kernel_filename && machine->firmware) { in ppc405_init()
339 } else if (kernel_filename && !machine->firmware) { in ppc405_init()
/qemu/docs/system/i386/
A Damd-memory-encryption.rst42 the firmware. To create this context, guest owner must provide a guest policy,
44 should be treated as a binary blob and must be passed as-is to the SEV firmware.
86 correctly by the firmware. The guest owner may wait to provide the guest
147 * ``firmware_blob`` is the content of the entire firmware flash file (for
148 example, ``OVMF.fd``). Note that you must build a stateless firmware file
150 therefore it is not secure to use a firmware which uses state from an NVRAM
169 three commands communicate with SEV-SNP firmware to generate a fresh memory
171 more details on the SEV-SNP firmware interfaces used by these commands please
175 within the firmware. To create this context, the guest owner must provide a
176 guest policy and other parameters as described in the SEV-SNP firmware
[all …]
/qemu/hw/mips/
A Dmipssim.c181 filename = qemu_find_file(QEMU_FILE_TYPE_BIOS, machine->firmware ?: BIOS_FILENAME); in mips_mipssim_init()
189 machine->firmware && !qtest_enabled()) { in mips_mipssim_init()
191 error_report("Could not load MIPS bios '%s'", machine->firmware); in mips_mipssim_init()
A Dfuloong2e.c263 machine->firmware ?: FULOONG_BIOSNAME); in mips_fuloong2e_init()
273 machine->firmware && !qtest_enabled()) { in mips_fuloong2e_init()
274 error_report("Could not load MIPS bios '%s'", machine->firmware); in mips_fuloong2e_init()
/qemu/hw/arm/
A Dhighbank.c235 if (machine->firmware != NULL) { in calxeda_init()
236 sysboot_filename = qemu_find_file(QEMU_FILE_TYPE_BIOS, machine->firmware); in calxeda_init()
239 error_report("Unable to load %s", machine->firmware); in calxeda_init()
244 error_report("Unable to find %s", machine->firmware); in calxeda_init()
A Ddigic_boards.c71 machine->firmware ?: board->rom0_def_filename); in digic4_board_init()
76 machine->firmware ?: board->rom1_def_filename); in digic4_board_init()
/qemu/docs/system/riscv/
A Dvirt.rst52 with the default OpenSBI firmware image as the -bios. It also supports
54 firmware and U-Boot proper (S-mode), using the standard -bios functionality.
60 S-mode firmware code. It can be configured as read-only, with the
73 For TCG guests only, it is also possible to boot M-mode firmware from
114 exposed as firmware tables etc/acpi/rsdp and etc/acpi/tables.
194 that bundles OpenSBI fw_dynamic firmware and U-Boot proper (S-mode) together,

Completed in 288 milliseconds

123456