package/intel-microcode: install into images for early loading support
Microcode based security mitigation (E.G. MDS) requires that the microcode gets loaded very early. This can be handled by one of: - Concatenating (a subset of) the intel-microcode files and write to kernel/x86/microcode/GenuineIntel.bin in the initrd. Requires that the (first) initrd is external from the kernel and NOT compressed. - Build (a subset of) the intel-microcode files into the kernel using the CONFIG_EXTRA_FIRMWARE option. Install the microcode files into images to support these use cases (E.G. through a post-build script for the initrd, or by pointing CONFIG_EXTRA_FIRMWARE_DIR to ${BR_BINARIES_DIR}, similar to how we include the .cpio image inside the kernel). Notice that there may be licensing concerns when embedded non-GPL firmware in the kernel. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
This commit is contained in:
parent
b7c9a7d602
commit
7c5dfea804
@ -9,6 +9,13 @@ INTEL_MICROCODE_SITE = $(call github,intel,Intel-Linux-Processor-Microcode-Data-
|
||||
INTEL_MICROCODE_LICENSE = PROPRIETARY
|
||||
INTEL_MICROCODE_LICENSE_FILES = license
|
||||
INTEL_MICROCODE_REDISTRIBUTE = NO
|
||||
INTEL_MICROCODE_INSTALL_IMAGES = YES
|
||||
|
||||
define INTEL_MICROCODE_INSTALL_IMAGES_CMDS
|
||||
mkdir -p $(BINARIES_DIR)/intel-ucode
|
||||
$(INSTALL) -m 0644 -t $(BINARIES_DIR)/intel-ucode \
|
||||
$(@D)/intel-ucode/*
|
||||
endef
|
||||
|
||||
define INTEL_MICROCODE_INSTALL_TARGET_CMDS
|
||||
mkdir -p $(TARGET_DIR)/lib/firmware/intel-ucode
|
||||
|
Loading…
Reference in New Issue
Block a user