Lines Matching refs:microcode
487 This file contains microcode for some devices in a special format. An
519 contains information about the firmware and microcode available in the
522 At present binman only supports a basic FIT with no microcode.
612 it work. It includes U-Boot TPL, microcode, things related to the CSE
868 Entry: u-boot-dtb-with-ucode: A U-Boot device tree file, with the microcode removed
876 contains the microcode. If the microcode is not being collated into one
877 place then the offset and size of the microcode is recorded by this entry,
879 entry deletes the microcode from the device tree (to save space) and makes
1013 Entry: u-boot-spl-with-ucode-ptr: U-Boot SPL with embedded microcode pointer
1016 This is used when SPL must set up the microcode for U-Boot.
1059 Entry: u-boot-tpl-dtb-with-ucode: U-Boot TPL with embedded microcode pointer
1062 This is used when TPL must set up the microcode for U-Boot.
1080 Entry: u-boot-tpl-with-ucode-ptr: U-Boot TPL with embedded microcode pointer
1088 Entry: u-boot-ucode: U-Boot microcode block
1097 U-Boot on x86 needs a single block of microcode. This is collected from
1098 the various microcode update nodes in the device tree. It is also unable
1099 to read the microcode from the device tree on platforms that use FSP
1101 microcode is supplied before there is any SRAM available to use (i.e.
1103 requires the microcode!). To keep things simple, all x86 platforms handle
1104 microcode the same way in U-Boot (even non-FSP platforms). This is that
1106 size of the microcode. This is either passed to the FSP (for FSP
1107 platforms), or used to set up the microcode (for non-FSP platforms).
1109 the microcode into a single blob and accessible without SRAM.
1111 There are two cases to handle. If there is only one microcode blob in
1115 entry (u-boot-dtb-with-ucode) is updated to remove the microcode. This
1116 last step ensures that that the microcode appears in one contiguous
1120 Entry types that have a part to play in handling microcode:
1124 It updates it with the address and size of the microcode so that
1127 Contains u-boot.dtb. It stores the microcode in a
1129 obtain the microcode if needed. If collation is performed, it
1130 removes the microcode from the device tree.
1132 This class. If collation is enabled it reads the microcode from
1138 Entry: u-boot-with-ucode-ptr: U-Boot with embedded microcode pointer
1143 - optional-ucode: boolean property to make microcode optional. If the
1144 u-boot.bin image does not include microcode, no error will
1149 microcode, to allow early x86 boot code to find it without doing anything