Lines Matching refs:microcode
949 This file contains microcode for some devices in a special format. An
985 contains information about the firmware and microcode available in the
988 At present binman only supports a basic FIT with no microcode.
1090 it work. It includes U-Boot TPL, microcode, things related to the CSE
1699 Entry: u-boot-dtb-with-ucode: A U-Boot device tree file, with the microcode removed
1707 contains the microcode. If the microcode is not being collated into one
1708 place then the offset and size of the microcode is recorded by this entry,
1710 entry deletes the microcode from the device tree (to save space) and makes
1917 Entry: u-boot-spl-with-ucode-ptr: U-Boot SPL with embedded microcode pointer
1920 This is used when SPL must set up the microcode for U-Boot.
1994 Entry: u-boot-tpl-dtb-with-ucode: U-Boot TPL with embedded microcode pointer
1997 This is used when TPL must set up the microcode for U-Boot.
2068 Entry: u-boot-tpl-with-ucode-ptr: U-Boot TPL with embedded microcode pointer
2078 Entry: u-boot-ucode: U-Boot microcode block
2087 U-Boot on x86 needs a single block of microcode. This is collected from
2088 the various microcode update nodes in the device tree. It is also unable
2089 to read the microcode from the device tree on platforms that use FSP
2091 microcode is supplied before there is any SRAM available to use (i.e.
2093 requires the microcode!). To keep things simple, all x86 platforms handle
2094 microcode the same way in U-Boot (even non-FSP platforms). This is that
2096 size of the microcode. This is either passed to the FSP (for FSP
2097 platforms), or used to set up the microcode (for non-FSP platforms).
2099 the microcode into a single blob and accessible without SRAM.
2101 There are two cases to handle. If there is only one microcode blob in
2105 entry (u-boot-dtb-with-ucode) is updated to remove the microcode. This
2106 last step ensures that that the microcode appears in one contiguous
2110 Entry types that have a part to play in handling microcode:
2114 It updates it with the address and size of the microcode so that
2117 Contains u-boot.dtb. It stores the microcode in a
2119 obtain the microcode if needed. If collation is performed, it
2120 removes the microcode from the device tree.
2122 This class. If collation is enabled it reads the microcode from
2252 Entry: u-boot-with-ucode-ptr: U-Boot with embedded microcode pointer
2257 - optional-ucode: boolean property to make microcode optional. If the
2258 u-boot.bin image does not include microcode, no error will
2263 microcode, to allow early x86 boot code to find it without doing anything