| /qemu/docs/interop/ |
| H A D | firmware.json | 14 # = Firmware
25 # Lists the firmware-OS interface types provided by various firmware
28 # @bios: Traditional x86 BIOS interface. For example, firmware built
32 # 1275-1994 standard. Examples for firmware projects that
35 # @uboot: Firmware interface defined by the U-Boot project.
37 # @uefi: Firmware interface defined by the UEFI specification. For
38 # example, firmware built from the edk2 (EFI Development Kit II)
49 # Defines the device types that firmware can be mapped into.
51 # @flash: The firmware executable and its accompanying NVRAM file are to
54 # @kernel: The firmware is to be loaded like a Linux kernel. This is
[all …]
|
| /qemu/docs/devel/migration/ |
| H A D | best-practices.rst | 26 Firmware chapter
30 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
[all …]
|
| /qemu/pc-bios/ |
| H A D | README | 8 firmware implementation. The goal is to implement a 100% IEEE
9 1275-1994 (referred to as Open Firmware) compliant firmware.
14 - SLOF (Slimline Open Firmware) is a free IEEE 1275 Open 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
21 QEMU implements parts of the IEEE 1275 Open Firmware interface.
42 (OpenPower Abstraction Layer) firmware for OpenPOWER systems. It can
62 - The "edk2-*.fd.bz2" images are platform firmware binaries and matching UEFI
66 were built at git tag "edk2-stable202302". The firmware binaries bundle parts
73 which conform to the "docs/interop/firmware.json" schema.
[all …]
|
| /qemu/docs/system/ |
| H A D | bootindex.rst | 4 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
|
| H A D | target-riscv.rst | 30 operating system or firmware images intended to run on one machine
75 RISC-V CPU firmware
79 firmware boot options:
84 will load the default OpenSBI firmware automatically. The firmware is included
90 QEMU will not automatically load any firmware. It is up to the user to load all
95 Tells QEMU to load the specified file as the firmware.
|
| H A D | target-sparc.rst | 59 OpenBIOS is a free (GPL v2) portable firmware implementation. The goal
60 is to implement a 100% IEEE 1275-1994 (referred to as Open Firmware)
61 compliant firmware.
|
| /qemu/docs/system/ppc/ |
| H A D | amigang.rst | 14 firmware to support AmigaOS 4.
26 Firmware section in Eyetech AmigaOne/Mai Logic Teron (``amigaone``)
29 A firmware binary is necessary for the boot process. It is a modified
40 The BIOS emulator in the firmware is unable to run QEMU‘s standard
58 If a firmware menu appears, select ``Boot sequence`` → ``Amiga Multiboot Options``
83 Firmware section in Genesi/bPlan Pegasos II (``pegasos2``)
86 The Pegasos II board has an Open Firmware compliant ROM based on
101 emulator in the firmware binary is unable to run QEMU‘s standard
110 At the firmware ``ok`` prompt enter ``boot cd install/pegasos``.
113 firmware ROM using the QEMU built-in minimal Virtual Open Firmware
[all …]
|
| H A D | powermac.rst | 28 Firmware chapter
33 (GPL v2) portable firmware implementation. The goal is to implement a
34 100% IEEE 1275-1994 (referred to as Open Firmware) compliant firmware.
|
| /qemu/tests/functional/ |
| H A D | test_aarch64_sbsaref.py | 27 - Trusted Firmware v2.12.0
53 As firmware runs at a higher privilege level than the hypervisor we
78 # https://github.com/ARM-software/arm-trusted-firmware/blob/v2.8.0/\
81 # design/firmware-design.html#cold-boot
84 wait_for_console_pattern(self, "Booting Trusted Firmware")
88 # Trusted Boot Firmware
95 # Non-trusted Firmware
96 wait_for_console_pattern(self, "UEFI firmware (version 1.0")
|
| /qemu/docs/system/arm/ |
| H A D | sbsa.rst | 13 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
|
| /qemu/hw/avr/ |
| H A D | boot.c | 61 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()
86 firmware, entry); in avr_load_firmware()
92 firmware, cpu_len, mcu_cpu_type); in avr_load_firmware()
99 firmware, in avr_load_firmware()
108 error_report("Unable to load firmware image %s as ELF or raw binary", in avr_load_firmware()
109 firmware); in avr_load_firmware()
|
| H A D | boot.h | 23 * @firmware: Path to the firmware file (raw binary or ELF format)
25 * Load a firmware supplied by the machine or by the user with the
31 MemoryRegion *mr, const char *firmware);
|
| /qemu/docs/specs/ |
| H A D | fw_cfg.rst | 2 QEMU Firmware Configuration (fw_cfg) Device
9 (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
107 Firmware Configuration Items
135 Firmware configuration items stored at selector keys 0x0020 or higher
[all …]
|
| H A D | ppc-spapr-hcalls.rst | 14 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
26 Firmware) and is still used by PAPR and LoPAR to provide various services that
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.
|
| H A D | tpm.rst | 62 The bios/firmware may read the ``"etc/tpm/config"`` fw_cfg entry for
93 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
108 TPM 2. This interface requires ACPI and firmware support. (see the
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
124 ACPI code is generated by QEMU, yet the firmware needs to implement
[all …]
|
| /qemu/include/hw/riscv/ |
| H A D | boot_opensbi.h | 47 * address as the FW_DYNAMIC firmware. In this case, the relocation
52 * to the FW_DYNAMIC firmware as the preferred boot HART.
55 * stage can set it to -1UL which will force the FW_DYNAMIC firmware
77 * address as the FW_DYNAMIC firmware. In this case, the relocation
82 * to the FW_DYNAMIC firmware as the preferred boot HART.
85 * stage can set it to -1UL which will force the FW_DYNAMIC firmware
|
| /qemu/hw/hppa/ |
| H A D | machine.c | 210 fw_cfg_add_file(fw_cfg, "/etc/firmware-min-version", in create_fw_cfg()
342 * Last creation step: Add SCSI discs, NICs, graphics & load firmware
350 const char *firmware = machine->firmware; in machine_HP_common_init_tail() local
421 /* Load firmware. Given that this is not "real" firmware, in machine_HP_common_init_tail()
424 firmware on 64-bit machines by default if not specified in machine_HP_common_init_tail()
427 if (!firmware) { in machine_HP_common_init_tail()
428 firmware = lasi_dev ? "hppa-firmware.img" : "hppa-firmware64.img"; in machine_HP_common_init_tail()
430 firmware_filename = qemu_find_file(QEMU_FILE_TYPE_BIOS, firmware); in machine_HP_common_init_tail()
432 error_report("no firmware provided"); in machine_HP_common_init_tail()
441 error_report("could not load firmware '%s'", firmware_filename); in machine_HP_common_init_tail()
[all …]
|
| /qemu/tests/qtest/ |
| H A D | prom-env-test.c | 2 * Test Open-Firmware-based machines.
12 * This test is used to check that some Open Firmware based machines (i.e.
14 * first put some Forth code into the "boot-command" Open Firmware environment
16 * in memory. Then we start the guest so that the firmware can boot and finally
52 * The pseries firmware boots much faster without the default in test_machine()
|
| /qemu/docs/system/i386/ |
| H A D | amd-memory-encryption.rst | 15 AMD secure processor (AMD-SP), which is present in AMD SOCs. Firmware running
42 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
172 see the SEV-SNP Firmware ABI.
[all …]
|
| /qemu/docs/ |
| H A D | igd-assign.txt | 31 guest via fw_cfg, where guest firmware can set up guest OpRegion with it.
46 "Guest firmware" section.
130 Guest firmware
132 Guest firmware is responsible for setting up OpRegion and Base of Data Stolen
134 fw_cfg requirements on the VM firmware:
143 recommended that firmware should make use of this fw_cfg entry for any
151 Firmware must allocate a reserved memory below 4GB with required 1MB
162 no need for guest firmware to allocate data stolen memory in guest address
183 customer, or you can try extracting it from your host firmware using
194 When using OVMF as guest firmware, you may encounter the following warning:
[all …]
|
| /qemu/hw/core/ |
| H A D | uboot_image.h | 43 IH_OS_U_BOOT, /* Firmware */
51 IH_OS_ARM_TRUSTED_FIRMWARE, /* ARM Trusted Firmware */
54 IH_OS_EFI, /* EFI Firmware (e.g. GRUB2) */
127 * "Firmware Images" are binary images containing firmware (like
147 IH_TYPE_FIRMWARE, /* Firmware Image */
175 IH_TYPE_FIRMWARE_IVT, /* Firmware Image with HABv4 IVT */
176 IH_TYPE_PMMC, /* TI Power Management Micro-Controller Firmware */
|
| /qemu/docs/devel/ |
| H A D | uefi-vars.rst | 15 requests must pass the sanity checks. (Parts of) the firmware must
17 by the firmware. On x86 this has been implemented using System
22 Communication with the firmware code running in SMM mode works by
44 privilege level for the firmware to protect itself, i.e. it does not
|
| /qemu/roms/ |
| H A D | Makefile | 45 # tag our firmware builds
71 @echo " efi -- update UEFI (edk2) platform firmware"
75 @echo " hppa-firmware -- update 32- and 64-bit hppa firmware"
179 …cp opensbi/build/platform/generic/firmware/fw_dynamic.bin ../pc-bios/opensbi-riscv32-generic-fw_dy…
185 …cp opensbi/build/platform/generic/firmware/fw_dynamic.bin ../pc-bios/opensbi-riscv64-generic-fw_dy…
203 hppa-firmware:
205 cp seabios-hppa/out/hppa-firmware.img ../pc-bios/
|
| /qemu/hw/ppc/ |
| H A D | amigaone.c | 45 * Firmware binary available at
49 * BIOS emulator in firmware cannot run QEMU vgabios and hangs on it, use
56 /* AmigaOS calls this routine from ROM, use this if no firmware loaded */
297 /* Firmware uses this area for startup */ in amigaone_init()
313 /* allocate and load firmware */ in amigaone_init()
317 if (!machine->firmware) { in amigaone_init()
322 machine->firmware); in amigaone_init()
324 error_report("Could not find firmware '%s'", machine->firmware); in amigaone_init()
329 error_report("Could not load firmware '%s'", filename); in amigaone_init()
|
| /qemu/linux-headers/linux/ |
| H A D | psp-sev.h | 40 * SEV Firmware status code
45 * there was an error that prevented the SEV firmware from being called.
100 * @build: firmware build id for API version
184 * @build_id: firmware build id for the API version
189 * @guest_count: the number of guest currently managed by the firmware
245 * @data: Opaque data provided by AMD KDS (as described in SEV-SNP Firmware ABI
|