| /external/chromiumos-config/test/suite_sets/suite_sets/firmware/ |
| D | faft_bios_ro_qual.star | 18 criteria = "Qualify the AP firmware for RO+RW release.",
20 "tast.firmware.BootMode.dev_cold",
21 "tast.firmware.BootMode.dev_gbb_to_rec",
22 "tast.firmware.BootMode.dev_to_rec",
23 "tast.firmware.BootMode.dev_usb_cold",
24 "tast.firmware.BootMode.dev_warm",
25 "tast.firmware.BootMode.normal_cold",
26 "tast.firmware.BootMode.normal_dev",
27 "tast.firmware.BootMode.normal_warm",
28 "tast.firmware.BootMode.rec_cold",
[all …]
|
| D | faft_bios_rw_qual.star | 18 criteria = "Qualify the AP firmware for RW-only release.",
20 "tast.firmware.BootMode.dev_cold",
21 "tast.firmware.BootMode.dev_gbb_to_rec",
22 "tast.firmware.BootMode.dev_to_rec",
23 "tast.firmware.BootMode.dev_usb_cold",
24 "tast.firmware.BootMode.dev_warm",
25 "tast.firmware.BootMode.normal_cold",
26 "tast.firmware.BootMode.normal_dev",
27 "tast.firmware.BootMode.normal_warm",
28 "tast.firmware.BootMode.rec_to_dev",
[all …]
|
| D | faft_ec_fw_qual.star | 18 criteria = "Qualify the EC firmware for RW or RO+RW release.",
24 "tast.firmware.BaseECUpdate",
25 "tast.firmware.BatteryCharging",
26 "tast.firmware.BootBatteryCutoff",
27 "tast.firmware.BootBatteryCutoff.chromeslate",
28 "tast.firmware.BootTime.default",
29 "tast.firmware.BootTime.x86",
30 "tast.firmware.BootTime.zork",
31 "tast.firmware.CheckKeyboardBacklightFunctionality",
32 "tast.firmware.CheckKeyboardBacklightFunctionality.lid_close_and_open",
[all …]
|
| D | faft_pd.star | 20 "tast.firmware.ECPDConnect.dts",
21 "tast.firmware.ECPDConnect.flipcc",
22 "tast.firmware.ECPDConnect.flipcc_dts",
23 "tast.firmware.ECPDConnect.normal",
24 "tast.firmware.ECPDPowerSwap.dts",
25 "tast.firmware.ECPDPowerSwap.dts_stress",
26 "tast.firmware.ECPDPowerSwap.flipcc",
27 "tast.firmware.ECPDPowerSwap.flipcc_dts",
28 "tast.firmware.ECPDPowerSwap.flipcc_dts_stress",
29 "tast.firmware.ECPDPowerSwap.flipcc_stress",
[all …]
|
| /external/autotest/metadata/tests/ |
| D | firmware.star | 13 'firmware/BaseECKeyboard',
18 'firmware/Bmpblk',
23 'firmware/CgptStress',
28 'firmware/ChipFwUpdate',
33 'firmware/ClearTPMOwnerAndReset',
38 'firmware/CompareChipFwToShellBall',
43 'firmware/ConsecutiveBoot',
48 'firmware/ConsecutiveBootPowerButton',
53 'firmware/ConsecutiveLidSwitch',
58 'firmware/CorruptBothFwBodyAB',
[all …]
|
| /external/vboot_reference/ |
| D | Android.bp | 42 "firmware/include",
43 "firmware/lib/include",
44 "firmware/lib/cgptlib/include",
45 "firmware/lib/tpm_lite/include",
46 "firmware/2lib/include",
56 "firmware/include",
57 "firmware/2lib/include",
98 "firmware/lib/tpm2_lite/tlcl.c",
99 "firmware/lib/tpm2_lite/marshaling.c",
106 "firmware/2lib/2api.c",
[all …]
|
| /external/trusty/arm-trusted-firmware/docs/ |
| D | change-log.md | 4 issues in each release of Trusted Firmware-A.
6 ## [2.12.0](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+/refs/tags/…
17 …c303e3](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+/2c303e393befc…
25 …890eab](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+/9890eab574362…
29 …a65e2d](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+/ba65e2d157495…
30 …f2b881](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+/6f2b8810f6d48…
36 …300a4d](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+/7300a4d1676f0…
37 …88a988](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+/188a9888e7b54…
38 …bb8f02](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+/8bb8f02d44d16…
44 …292f24](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+/8292f240e5d3f…
[all …]
|
| /external/linux-firmware/ |
| D | README.md | 1 # About the linux-firmware project
7 <https://gitlab.com/kernel-firmware/linux-firmware.git>
11 <https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/>
17 that tracks licensing and also to let us to update each firmware
28 ## How to use this firmware in your Android product
32 any firmware that you want. Nearly all firmware here is classified with
36 After you've got approval, including this firmware in your Android product
38 wanted to include the r8152 firmware:
44 ## How to get your firmware added
46 In order to get firmware added to this repo, the process is roughly:
[all …]
|
| /external/autotest/server/hosts/ |
| D | cros_firmware.py | 7 Repair actions and verifiers relating to CrOS firmware.
10 with the firmware installed on ChromeOS DUTs, and when necessary, to
11 fix problems by updating or re-installing the firmware.
15 corrupted firmware. The module supplies `FirmwareStatusVerifier`
17 re-install firmware of current faft stable_version via servo
20 designated "stable" firmware version. This module supplies
22 firmware that is out-of-date from the designated version. This model
23 also supplys `GeneralFirmwareRepair` to re-install firmware that
29 and install the stable firmware using `FirmwareVersionVerifier`.
30 * DUTs in pools used for FAFT testing. These check for bad firmware
[all …]
|
| /external/chromiumos-config/test/suite_sets/generated/ |
| D | suites.jsonpb | 2727 "value": "tast.firmware.Config"
2730 "value": "tast.firmware.Flashrom"
2733 "value": "tast.firmware.FlashromWriteProtect"
2736 "value": "tast.firmware.FwupdGetDevices"
2739 "value": "tast.firmware.FwupdPluginStartup"
2742 "value": "tast.firmware.FwupdPluginStartup.uefi"
2745 "value": "tast.firmware.GSCtool"
5590 "value": "Qualify the AP firmware for RO+RW release."
5595 "value": "tast.firmware.BootMode.dev_cold"
5598 "value": "tast.firmware.BootMode.dev_gbb_to_rec"
[all …]
|
| /external/vboot_reference/firmware/2lib/ |
| D | 2recovery_reasons.c | 21 return "RW firmware failed signature check"; in vb2_get_recovery_reason_string()
25 return "TPM error in read-only firmware"; in vb2_get_recovery_reason_string()
27 return "Shared data error in read-only firmware"; in vb2_get_recovery_reason_string()
35 return "RW firmware check not done"; in vb2_get_recovery_reason_string()
37 return "RW firmware developer flag mismatch"; in vb2_get_recovery_reason_string()
39 return "RW firmware recovery flag mismatch"; in vb2_get_recovery_reason_string()
41 return "RW firmware unable to verify keyblock"; in vb2_get_recovery_reason_string()
43 return "RW firmware key version rollback detected"; in vb2_get_recovery_reason_string()
45 return "RW firmware unable to parse data key"; in vb2_get_recovery_reason_string()
47 return "RW firmware unable to verify preamble"; in vb2_get_recovery_reason_string()
[all …]
|
| /external/autotest/server/site_tests/fleet_FirmwareUpdate/ |
| D | fleet_FirmwareUpdate.py | 14 """Test to update OS bundled firmware and validate DUT is in good state."""
20 """Update OS bundled firmware, RW only.
23 host: Target host machine to update firmware.
26 error.TestFail if update firmware cmd return with non-zero code.
28 logging.info("Starting update firmware on %s.", host.hostname)
32 raise error.TestFail("Failed to update firmware.")
35 """Validate DUT is in good state before firmware update.
44 # Ensure the DUT is sshable before firmware update.
46 raise error.TestNAError("DUT is down before firmware update.")
48 # Ensure the DUT can reboot normally before firmware update.
[all …]
|
| /external/coreboot/src/southbridge/intel/common/firmware/ |
| D | Kconfig | 7 Platform uses the Intel Firmware Descriptor to describe the
10 firmware blobs.
14 comment "Intel Firmware"
28 bool "Add Intel ME/TXE firmware"
31 The Intel processor in the selected system requires a special firmware
34 depending on the chip. This firmware might or might not be available
36 have access to the firmware from elsewhere, you can still build
38 that you don't overwrite your ME/TXE firmware on your flash ROM.
50 string "Path to management engine firmware" if !STITCH_ME_BIN
55 bool "Verify the integrity of the supplied ME/TXE firmware"
[all …]
|
| /external/coreboot/src/vendorcode/intel/edk2/edk2-stable202302/MdePkg/Include/Protocol/ |
| D | FirmwareVolumeBlock.h | 2 This file provides control over block-oriented firmware devices.
41 @retval EFI_SUCCESS The firmware volume attributes were
53 The SetAttributes() function sets configurable firmware volume
54 attributes and returns the new settings of the firmware volume.
60 desired firmware volume settings. On
62 settings of the firmware volume. Type
66 @retval EFI_SUCCESS The firmware volume attributes were returned.
70 as declared in the firmware
83 a memory-mapped firmware volume. This function should be called
84 only for memory-mapped firmware volumes.
[all …]
|
| D | FirmwareManagement.h | 2 UEFI Firmware Management Protocol definition
3 Firmware Management Protocol provides an abstraction for device to provide firmware
4 management support. The base requirements for managing device firmware images include
5 identifying firmware image revision level and programming the image into the device.
60 /// A unique number identifying the firmware image within the device. The number is
65 /// A unique GUID identifying the firmware image type.
69 /// A unique number identifying the firmware image.
73 /// A pointer to a null-terminated string representing the firmware image name.
77 /// Identifies the version of the device firmware. The format is vendor specific and new
82 /// A pointer to a null-terminated string representing the firmware image version name.
[all …]
|
| /external/coreboot/src/vendorcode/intel/edk2/edk2-stable202005/MdePkg/Include/Protocol/ |
| D | FirmwareVolumeBlock.h | 2 This file provides control over block-oriented firmware devices.
41 @retval EFI_SUCCESS The firmware volume attributes were
54 The SetAttributes() function sets configurable firmware volume
55 attributes and returns the new settings of the firmware volume.
61 desired firmware volume settings. On
63 settings of the firmware volume. Type
67 @retval EFI_SUCCESS The firmware volume attributes were returned.
71 as declared in the firmware
85 a memory-mapped firmware volume. This function should be called
86 only for memory-mapped firmware volumes.
[all …]
|
| D | FirmwareManagement.h | 2 UEFI Firmware Management Protocol definition
3 Firmware Management Protocol provides an abstraction for device to provide firmware
4 management support. The base requirements for managing device firmware images include
5 identifying firmware image revision level and programming the image into the device.
61 /// A unique number identifying the firmware image within the device. The number is
66 /// A unique GUID identifying the firmware image type.
70 /// A unique number identifying the firmware image.
74 /// A pointer to a null-terminated string representing the firmware image name.
78 /// Identifies the version of the device firmware. The format is vendor specific and new
83 /// A pointer to a null-terminated string representing the firmware image version name.
[all …]
|
| /external/coreboot/src/vendorcode/intel/edk2/edk2-stable202111/MdePkg/Include/Protocol/ |
| D | FirmwareVolumeBlock.h | 2 This file provides control over block-oriented firmware devices.
41 @retval EFI_SUCCESS The firmware volume attributes were
54 The SetAttributes() function sets configurable firmware volume
55 attributes and returns the new settings of the firmware volume.
61 desired firmware volume settings. On
63 settings of the firmware volume. Type
67 @retval EFI_SUCCESS The firmware volume attributes were returned.
71 as declared in the firmware
85 a memory-mapped firmware volume. This function should be called
86 only for memory-mapped firmware volumes.
[all …]
|
| D | FirmwareManagement.h | 2 UEFI Firmware Management Protocol definition
3 Firmware Management Protocol provides an abstraction for device to provide firmware
4 management support. The base requirements for managing device firmware images include
5 identifying firmware image revision level and programming the image into the device.
61 /// A unique number identifying the firmware image within the device. The number is
66 /// A unique GUID identifying the firmware image type.
70 /// A unique number identifying the firmware image.
74 /// A pointer to a null-terminated string representing the firmware image name.
78 /// Identifies the version of the device firmware. The format is vendor specific and new
83 /// A pointer to a null-terminated string representing the firmware image version name.
[all …]
|
| /external/coreboot/src/ec/google/chromeec/ |
| D | Kconfig | 112 the EC firmware. If set, the coreboot build with also
113 build the EC firmware and add it to the image.
121 the PD firmware. If set, the coreboot build with also
122 build the EC firmware and add it to the image.
131 prompt "Chrome EC firmware source"
136 bool "No EC firmware is included"
138 Disable building and including any EC firmware in the image.
141 bool "External EC firmware is included"
143 Include EC firmware binary in the image from an external source.
147 bool "Builtin EC firmware is included"
[all …]
|
| /external/trusty/arm-trusted-firmware/docs/getting_started/ |
| D | image-terminology.rst | 5 images referred to in the Trusted Firmware project.
33 Clearly, many of these images are not BootLoaders, they are simply firmware
40 Trusted Firmware Images
43 Firmware Image Package: ``FIP``
46 This is a packaging format used by TF-A to package firmware images in a single
48 platform-specific and may include TF-A images and other firmware images
57 and authenticate an updateable AP firmware image into an executable RAM
60 AP RAM Firmware: ``AP_BL2``
63 This is the 2nd stage AP firmware. It is currently also known as the "Trusted
64 Boot Firmware". Its primary purpose is to perform any additional initialization
[all …]
|
| /external/coreboot/src/vendorcode/intel/edk2/UDK2017/MdePkg/Include/Protocol/ |
| D | FirmwareVolumeBlock.h | 2 This file provides control over block-oriented firmware devices.
47 @retval EFI_SUCCESS The firmware volume attributes were
60 The SetAttributes() function sets configurable firmware volume
61 attributes and returns the new settings of the firmware volume.
67 desired firmware volume settings. On
69 settings of the firmware volume. Type
73 @retval EFI_SUCCESS The firmware volume attributes were returned.
77 as declared in the firmware
91 a memory-mapped firmware volume. This function should be called
92 only for memory-mapped firmware volumes.
[all …]
|
| D | FirmwareManagement.h | 2 UEFI Firmware Management Protocol definition
3 Firmware Management Protocol provides an abstraction for device to provide firmware
4 management support. The base requirements for managing device firmware images include
5 identifying firmware image revision level and programming the image into the device.
42 /// A unique number identifying the firmware image within the device. The number is
47 /// A unique GUID identifying the firmware image type.
51 /// A unique number identifying the firmware image.
55 /// A pointer to a null-terminated string representing the firmware image name.
59 /// Identifies the version of the device firmware. The format is vendor specific and new
64 /// A pointer to a null-terminated string representing the firmware image version name.
[all …]
|
| /external/chromiumos-config/proto/chromiumos/build/api/ |
| D | firmware_config.proto | 14 // The type of a firmware binary.
25 // Specifies the version of a firmware binary.
32 // Specifies the location of a firmware binary.
36 // The path to the firmware build artifact
38 // Path to the firmware artifact (either local or GS path)
69 // Specifies different firmware payloads to use. This is used in the following
73 // - In the factory to flash the RO firmware.
74 // - F20 firmware provisioning.
76 // Building firmware is configured with the FirmwareBuildConfig message.
80 // The main firmware image. Updates both RO and RW sections.
[all …]
|
| /external/vboot_reference/firmware/2lib/include/ |
| D | 2recovery_reasons.h | 44 /**** Firmware verification (RO) errors (and some EC stuff???) ********/
52 /* TPM error in read-only firmware (deprecated, see 0x54+) */
55 /* Shared data error in read-only firmware */
68 * RW firmware failed signature check (neither RW firmware slot was
75 /* Latest tried RW firmware developer flag mismatch */
78 /* Latest tried RW firmware recovery flag mismatch */
81 /* Latest tried RW firmware keyblock verification failed */
84 /* Latest tried RW firmware key version too old */
87 /* Latest tried RW firmware unable to parse data key */
90 /* Latest tried RW firmware preamble verification failed */
[all …]
|