Home
last modified time | relevance | path

Searched full:firmware (Results 1 – 25 of 1513) sorted by relevance

12345678910>>...61

/openbmc/openbmc/poky/meta/recipes-kernel/linux-firmware/
H A Dlinux-firmware_20250509.bb1 SUMMARY = "Firmware files for use with Linux kernel"
3 DESCRIPTION = "Linux firmware is a package distributed alongside the Linux kernel \
4 that contains firmware binary blobs necessary for partial or full functionality \
9 Firmware-Abilis \
10 & Firmware-adsp_sst \
11 & Firmware-agere \
12 & Firmware-amdgpu \
13 & Firmware-amd-ucode \
14 & Firmware-amlogic_vdec \
15 & Firmware-amphion_vpu \
[all …]
/openbmc/openbmc/meta-raspberrypi/recipes-kernel/linux-firmware-rpidistro/
H A Dlinux-firmware-rpidistro_git.bb1 SUMMARY = "Linux kernel firmware files from Raspbian distribution"
2 DESCRIPTION = "Updated firmware files for RaspberryPi hardware. \
4 to linux-firmware for general use."
5 HOMEPAGE = "https://github.com/RPi-Distro/firmware-nonfree"
18 SRC_URI = "git://github.com/RPi-Distro/firmware-nonfree;branch=bookworm;protocol=https \
19 file://0001-Default-43455-firmware-to-standard-variant.patch \
30 # The minimal firmware doesn't work with Raspberry Pi 5, so default to the
31 # standard firmware
36 install -d ${D}${nonarch_base_libdir}/firmware/brcm ${D}${nonarch_base_libdir}/firmware/cypress
38 cp debian/copyright ${D}${nonarch_base_libdir}/firmware/copyright.firmware-nonfree-rpidistro
[all …]
/openbmc/openbmc/meta-raspberrypi/recipes-kernel/bluez-firmware-rpidistro/
H A Dbluez-firmware-rpidistro_git.bb1 SUMMARY = "Linux kernel Bluetooth firmware files from Raspbian distribution"
2 DESCRIPTION = "Updated Bluetooth firmware files for RaspberryPi hardware. \
4 to linux-firmware for general use."
5 HOMEPAGE = "https://github.com/RPi-Distro/bluez-firmware"
10 # changed in linux-firmware.
14 # conflicts with linux-firmware.
16 # [^1]: https://github.com/RPi-Distro/bluez-firmware/issues/1
17 LICENSE = "Firmware-cypress-rpidistro"
24 NO_GENERIC_LICENSE[Firmware-cypress-rpidistro] = "LICENCE.cypress-rpidistro"
27 git://github.com/RPi-Distro/bluez-firmware;branch=bookworm;protocol=https \
[all …]
/openbmc/phosphor-webui/app/common/directives/
H A Dfirmware-list.html4 <p class="inline firmware__active-version">Functional firmware version: {{version}}</p>
24 …iv class="table__row" ng-class="firmware.activationStatus == 'Functional' ? 'firmware__primary' : …
28 …ng-click="!$first && changePriority(firmware.imageId, firmware.Version, firmware.Priority, imageLi…
29 … ng-show="firmware.activationStatus == 'Functional' || firmware.activationStatus == 'Active'">
30 <span class="accessible-text">firmware up in priority</span></div>
32 …List[$index + 1].activationStatus)) && changePriority(firmware.imageId, firmware.Version, firmware…
33 … ng-show="firmware.activationStatus == 'Functional' || firmware.activationStatus == 'Active'">
34 <span class="accessible-text">firmware down in priority</span></div>
38 <span>{{firmware.activationStatus}}</span>
40 <div class="table__cell firmware__version" ng-class="{'active':firmware.isExtended}">
[all …]
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-kernel/broadcom-bt-firmware/
H A Dbroadcom-bt-firmware_12.0.1.1105_p3.bb4 SUMMARY = "Broadcom Bluetooth firmware files"
5 DESCRIPTION = "Firmware for Broadcom Bluetooth devices. Note that in case of BT+WiFi devices, separ…
6 HOMEPAGE = "https://github.com/winterheart/broadcom-bt-firmware"
8 LICENSE = "Firmware-Broadcom-WIDCOMM"
9 NO_GENERIC_LICENSE[Firmware-Broadcom-WIDCOMM] = "LICENSE.broadcom_bcm20702"
12 SRC_URI = "git://github.com/winterheart/broadcom-bt-firmware.git;branch=master;protocol=https"
28 install -d ${D}${nonarch_base_libdir}/firmware/brcm/
29 cp brcm/*.hcd ${D}${nonarch_base_libdir}/firmware/brcm/
32 install -m 0644 LICENSE.broadcom_bcm20702 ${D}${nonarch_base_libdir}/firmware/brcm/
35 install -m 0644 DEVICES.md ${D}${nonarch_base_libdir}/firmware/brcm/
[all …]
/openbmc/docs/designs/
H A Dredfish-resource-supplement-for-pfr.md1 # Redfish resource supplement for Platform Firmware Resilience (PFR)
11 The platform is a collection of fundamental hardware and firmware components
12 needed to boot and operate a system. The Platform Firmware Resiliency(PFR) in
14 resiliency of platform firmware and data against potentially destructive
21 represent the PFR provisioning status such as platform firmware is provisioned
27 Platform Firmware Resilience technology in NIST SP 800-93 provide common
43 - BMC shall provide the way to represent Platform Firmware Resilience
46 - Event logs should be logged to redfish for Platform Firmware Resilience.
50 Different OEM's has there own way of implementing the Platform Firmware
57 Platform Firmware Resilience. It covers only generic redfish ComputerSystem OEM
[all …]
/openbmc/openbmc-test-automation/redfish/update_service/
H A Dtest_firmware_inventory.robot60 [Documentation] Get firmware inventory entries and do health check status.
108 IF '${entry}' == '${actual_count}' Fail BMC version not there in Firmware Inventory
150 [Documentation] Verify the redfish firmware inventory path is updateable.
190 Verify Redfish Software Image And Firmware Inventory Are Same
191 [Documentation] Verify the firmware software inventory is same as software images of managers.
213 Check If Firmware Image Is Same In Firmware Inventory And Redfish Read Operation
214 [Documentation] Check the Redfish firmware inventory path is same as in
215 ... active software image of Redfish managers and firmware inventory of update service.
218 Verify Active Software Image And Firmware Inventory Is Same
221 Check If Backup Firmware Image Is Same In Firmware Inventory And Redfish Read Operation
[all …]
H A Dtest_redfish_image_upload.robot12 # Refer below document to generate bad firmware images for testing.
13 # openbmc/openbmc-test-automation/blob/master/docs/code_update.md#generating-bad-firmware-image-for…
46 [Documentation] Upload a BMC firmware with a bad MANIFEST file.
48 [Template] Redfish Bad Firmware Update
55 [Documentation] Upload a BMC firmware with no kernel image.
57 [Template] Redfish Bad Firmware Update
64 [Documentation] Upload a PNOR firmware with a bad MANIFEST file.
66 [Template] Redfish Bad Firmware Update
73 [Documentation] Upload a PNOR firmware with no kernel Image.
75 [Template] Redfish Bad Firmware Update
[all …]
H A Dtest_bmc_image_switch.robot25 Test Firmware Image Switch Without Powering Host
28 [Template] Firmware Switch Loop
34 Test Firmware Image Switch And Power On Host
37 [Template] Firmware Switch Loop
45 Firmware Switch Loop
46 [Documentation] Wrapper keyword for iteration for firmware side switch.
51 # power_on If YES, boot the system post firmware image switch,
56 Redfish BMC Switch Firmware Side
63 # Power Off for next iteration. Firmware image switch ideally needs to be
78 Redfish BMC Switch Firmware Side
[all …]
/openbmc/openbmc/meta-raspberrypi/recipes-bsp/rpi-eeprom/
H A Drpi-eeprom_git.bb36 # copy firmware files
37 install -d ${D}${base_libdir}/firmware/raspberrypi/bootloader-2711/default
38 install -d ${D}${base_libdir}/firmware/raspberrypi/bootloader-2711/latest
39 install -d ${D}${base_libdir}/firmware/raspberrypi/bootloader-2712/default
40 install -d ${D}${base_libdir}/firmware/raspberrypi/bootloader-2712/latest
42 …install -m 644 ${S}/firmware-2711/default/* ${D}${base_libdir}/firmware/raspberrypi/bootloader-271…
43 …install -m 644 ${S}/firmware-2711/latest/* ${D}${base_libdir}/firmware/raspberrypi/bootloader-2711…
44 …install -m 644 ${S}/firmware-2712/default/* ${D}${base_libdir}/firmware/raspberrypi/bootloader-271…
45 …install -m 644 ${S}/firmware-2712/latest/* ${D}${base_libdir}/firmware/raspberrypi/bootloader-2712…
47 ln -s default ${D}${base_libdir}/firmware/raspberrypi/bootloader-2711/critical
[all …]
/openbmc/openbmc-test-automation/redfish/extended/
H A Dredfish_bmc_code_update.robot7 # Firmware update states:
50 [Documentation] Update the firmware image.
66 # Check if the existing firmware is functional.
68 ... The existing ${image_version} firmware is already functional.
70 ${sw_inv}= Get Functional Firmware BMC image
71 ${nonfunctional_sw_inv}= Get Non Functional Firmware ${sw_inv} False
76 Set Backup Firmware To Functional ${image_version} ${state}
80 Print Timen Performing firmware update ${image_version}.
82 Redfish Update Firmware
85 Redfish BMC Code Update Running And Backup Image With Same Firmware
[all …]
/openbmc/qemu/docs/interop/
H A Dfirmware.json15 # Firmware
27 # Lists the firmware-OS interface types provided by various firmware
30 # @bios: Traditional x86 BIOS interface. For example, firmware built
34 # 1275-1994 standard. Examples for firmware projects that
37 # @uboot: Firmware interface defined by the U-Boot project.
39 # @uefi: Firmware interface defined by the UEFI specification. For
40 # example, firmware built from the edk2 (EFI Development Kit II)
51 # Defines the device types that firmware can be mapped into.
53 # @flash: The firmware executable and its accompanying NVRAM file are to
56 # @kernel: The firmware is to be loaded like a Linux kernel. This is
[all …]
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Software/
H A DApplyOptions.interface.yaml2 To implement the Activation apply options for a newly uploaded firmware
3 image. The apply options property is specific to each firmware update and is
4 used during firmware activation. ApplyOptions usage during firmware
5 activation is implementation specific, not all firmware targets need
6 ApplyOptions. This property is removed after activation of the firmware is
7 done and when the firmware goes to Active state. The default value of this
15 when the firmware image update is getting applied. A value of true
16 indicates the firmware configurations should be cleared along with
17 firmware image activation.
/openbmc/u-boot/doc/uImage.FIT/
H A Dsec_firmware_ppa.its5 * of SEC Firmware and multiple loadable images loaded by the u-boot.
6 * For booting PPA (SEC Firmware), "firmware" is searched and loaded.
9 * respective load offsets from firmware image address.
13 description = "PPA Firmware";
16 firmware@1 {
17 description = "PPA Firmware: <version>";
19 type = "firmware";
34 type = "firmware";
44 description = "PPA Secure firmware";
45 firmware = "firmware@1";
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/State/
H A DHost.interface.yaml30 firmware. A user can determine if a system is in transition by
43 The desired transition for host firmware
47 Host firmware should be off
50 Host firmware should be on
53 Host firmware should be rebooted. Chassis power will be cycled
57 Host firmware be will notified to shutdown and once complete,
58 the host firmware will be rebooted. Chassis power will remain on
62 Host firmware will be rebooted without notification and chassis
67 The current state of the host firmware
71 Host firmware is not running
[all …]
/openbmc/openbmc/meta-arm/kas/
H A Dcorstone1000-image-configuration.yml10 BBMULTICONFIG ?= "firmware"
17 INITRAMFS_IMAGE_BUNDLE:firmware = "1"
18 INITRAMFS_IMAGE:firmware ?= "corstone1000-recovery-image"
19 IMAGE_FSTYPES:firmware:pn-corstone1000-recovery-image = "${INITRAMFS_FSTYPES}"
20 IMAGE_NAME_SUFFIX:firmware = ""
23 INIT_MANAGER:firmware = "mdev-busybox"
24 VIRTUAL-RUNTIME_init_manager:firmware = "busybox"
27 PACKAGE_EXCLUDE:firmware += "kernel-image-*"
30 PACKAGECONFIG:remove:firmware:pn-kmod = "openssl"
41 CORE_IMAGE_EXTRA_INSTALL:firmware += "packagegroup-ts-tests-psa"
[all …]
/openbmc/u-boot/drivers/net/pfe_eth/
H A Dpfe_firmware.c9 * Contains all the functions to handle parsing and loading of PE firmware
24 * PFE elf firmware loader.
25 * Loads an elf firmware image into a list of PE's (specified using a bitmask)
27 * @param pe_mask Mask of PE id's to load firmware to
28 * @param pfe_firmware Pointer to the firmware image
86 * Get PFE firmware from FIT image
88 * @param data pointer to PFE firmware
89 * @param size pointer to size of the firmware
90 * @param fw_name pfe firmware name, either class or tmu
106 printf("PFE Firmware: %s: no such config\n", conf_node_name); in pfe_get_fw()
[all …]
/openbmc/u-boot/arch/arm/cpu/armv8/
H A Dsec_firmware.c22 * Secure firmware load addr
23 * Flags used: 0x1 secure firmware has been loaded to secure memory
24 * 0x2 secure firmware is running
29 #define SEC_FIRMWARE_FIT_IMAGE "firmware"
50 printf("SEC Firmware: %s: no such config\n", conf_node_name); in sec_firmware_get_data()
57 printf("SEC Firmware: No '%s' in config\n", in sec_firmware_get_data()
62 /* Verify secure firmware image */ in sec_firmware_get_data()
64 printf("SEC Firmware: Bad firmware image (bad CRC)\n"); in sec_firmware_get_data()
69 printf("SEC Firmware: Can't get %s subimage data/size", in sec_firmware_get_data()
76 printf("SEC Firmware: Can't get description\n"); in sec_firmware_get_data()
[all …]
H A DKconfig20 Say Y here if there is not any trust firmware to set
28 register may be controlled by EL3/EL2 firmware. To be more
29 precise, by default (if there is EL2/EL3 firmware running)
55 menu "ARMv8 secure monitor firmware"
57 bool "Enable ARMv8 secure monitor firmware framework support"
61 This framework is aimed at making secure monitor firmware load
65 - Address of secure firmware.
66 - Address to hold the return address from secure firmware.
67 - Secure firmware FIT image related information.
69 - The target exception level that secure monitor firmware will
[all …]
/openbmc/openbmc-test-automation/gui/gui_test/operations_menu/
H A Dtest_firmware_sub_menu.robot3 Documentation Test OpenBMC Firmware Update" sub menu of "Operations".
14 ${xpath_firmware_heading} //h1[text()="Firmware"]
16 ${xpath_start_update_button} //*[@data-test-id="firmware-button-startUpdate"]
17 ${xpath_switch_to_running} //*[@data-test-id="firmware-button-switchToRunning"]
21 Verify Navigation To Firmware Page
22 [Documentation] Verify navigation to firmware page.
28 Verify Existence Of All Sections In Firmware Page
29 [Documentation] Verify existence of all sections in firmware page.
33 Page Should Contain Update firmware
39 Verify Existence Of All Buttons In Firmware Page At Host Power Off
[all …]
/openbmc/qemu/docs/devel/migration/
H A Dbest-practices.rst26 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 …]
/openbmc/openbmc/meta-arm/meta-arm/recipes-bsp/images/
H A Dfirmware-deploy-image.bb1 SUMMARY = "Firmware image deploying multi-config firmware"
2 DESCRIPTION = "Image for deploying a firmware set on platforms using multi-config"
13 # Users of this recipe are expected to provide the list of firmware images
20 for firmware in ${FIRMWARE_BINARIES}; do
21 echo "cp -av ${firmware_loc}/${firmware} ${DEPLOYDIR}/"
22 cp -av "${firmware_loc}/${firmware}" ${DEPLOYDIR}/
23 if [ -L "${firmware_loc}/${firmware}" ]; then
24 echo "cp -av ${firmware_loc}/$(readlink ${firmware_loc}/${firmware}) ${DEPLOYDIR}/"
25 cp -av "${firmware_loc}/$(readlink ${firmware_loc}/${firmware})" ${DEPLOYDIR}/
/openbmc/u-boot/drivers/net/fm/
H A Dfdt.c10 * fdt_fixup_fman_firmware -- insert the Fman firmware into the device tree
12 * The binding for an Fman firmware node is documented in
14 * the actual Fman firmware binary data. The operating system is expected to
27 /* The first Fman we find will contain the actual firmware. */ in fdt_fixup_fman_firmware()
33 /* If we already have a firmware node, then also exit silently. */ in fdt_fixup_fman_firmware()
34 if (fdt_node_offset_by_compatible(blob, -1, "fsl,fman-firmware") > 0) in fdt_fixup_fman_firmware()
49 /* Verify the firmware. */ in fdt_fixup_fman_firmware()
52 printf("Data at %p is not an Fman firmware\n", fmanfw); in fdt_fixup_fman_firmware()
57 printf("Fman firmware at %p is too large (size=%u)\n", in fdt_fixup_fman_firmware()
65 printf("Fman firmware at %p has invalid CRC\n", fmanfw); in fdt_fixup_fman_firmware()
[all …]
/openbmc/phosphor-power/tools/power-utils/
H A Daei_updater.hpp24 * @brief A class to handle firmware updates for the AEI PSUs.
26 * This class provides methods to update firmware by writing ISP keys,
27 * validating firmware files, and performing I2C communications. It includes
28 * functions to manage the update process, including downloading firmware blocks
46 * @param imageDir The directory containing the firmware image files.
54 * @brief Initiates the firmware update process.
69 * @brief Writes the mode required for ISP to start firmware programming.
76 * @brief Resets the ISP status to prepare for a firmware update.
83 * @brief Retrieves the path to the firmware file.
90 * @brief Validates the firmware file.
[all …]
/openbmc/openbmc/meta-arm/meta-arm/recipes-bsp/scp-firmware/
H A Dscp-firmware_2.16.0.bb1 SUMMARY = "SCP and MCP Firmware"
2 DESCRIPTION = "Firmware for SCP and MCP software reference implementation"
3 HOMEPAGE = "https://gitlab.arm.com/firmware/SCP-firmware"
9 SRC_URI_SCP_FIRMWARE ?= "gitsm://git.gitlab.arm.com/firmware/SCP-firmware.git;protocol=https"
17 PROVIDES += "virtual/control-processor-firmware"
79 install -d ${D}/firmware
84 … install -D "${B}/${TYPE}/${FW}/bin/${SCP_PLATFORM}-bl1.bin" "${D}/firmware/${FW}_${TYPE}.bin"
85 … install -D "${B}/${TYPE}/${FW}/bin/${SCP_PLATFORM}-bl1.elf" "${D}/firmware/${FW}_${TYPE}.elf"
87 …install -D "${B}/${TYPE}/${FW}/bin/${SCP_PLATFORM}-${FW}-bl1.bin" "${D}/firmware/${FW}_${TYPE}.bin"
88 …install -D "${B}/${TYPE}/${FW}/bin/${SCP_PLATFORM}-${FW}-bl1.elf" "${D}/firmware/${FW}_${TYPE}.elf"
[all …]

12345678910>>...61