On 7/11/14, 11:59, "Kamble, Nitin A" <[email protected]> wrote:
>From: Nitin A Kamble <[email protected]> > >Consumes the intel-earlyload-microcode-image to generate an initrd which >is >extended with the earlyload microcode support. > >This recipe now generates this additional initrd image: > core-image-minimal-initramfs-${MACHINE}.cpio.gz.ucode > >Signed-off-by: Nitin A Kamble <[email protected]> >--- > common/recipes-core/images/core-image-minimal-initramfs.bbappend | 3 +++ > 1 file changed, 3 insertions(+) > create mode 100644 >common/recipes-core/images/core-image-minimal-initramfs.bbappend > >diff --git >a/common/recipes-core/images/core-image-minimal-initramfs.bbappend >b/common/recipes-core/images/core-image-minimal-initramfs.bbappend >new file mode 100644 >index 0000000..d836400 >--- /dev/null >+++ b/common/recipes-core/images/core-image-minimal-initramfs.bbappend >@@ -0,0 +1,3 @@ >+inherit image-ucode >+ >+IMAGE_FSTYPES_meta-intel = "cpio.gz.ucode" >-- >1.8.1.4 > Hrm.... A meta-intel override... Do we need to introduce a layer override, or would the intel-common overrides be sufficient? It would reduce the complexity a bit. I do see the value in the layer override though as it applies to the BSPs that are not yet intel-common - or won't ever be. So.. Acked-by: Darren Hart <[email protected]> -- Darren Hart Open Source Technology Center [email protected] Intel Corporation -- _______________________________________________ meta-intel mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-intel
