Hi Paul, On 27.07.20 09:20, Paul Menzel wrote: > Making a Kaby Lake-U variant port [1], building an image, I notice the > log say the microcode update files sizes in the FIT table are 0.
IIRC, this is intentional, because the update itself already has a header that specifies its length. If the length were stored redundantly in the FIT, it would just be one more thing that could be wrong. Nico _______________________________________________ coreboot mailing list -- [email protected] To unsubscribe send an email to [email protected]

