On Fri, 2014-06-20 at 11:52 -0700, [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..ee3e18d
> --- /dev/null
> +++ b/common/recipes-core/images/core-image-minimal-initramfs.bbappend
> @@ -0,0 +1,3 @@
> +inherit image-ucode
> +
> +IMAGE_FSTYPES = "cpio.gz.ucode"

This takes effect for *all* machines/distros and is therefore not an
acceptable thing to be doing, at the very least this needs to be x86
only using some form of override. 

It again makes me think that using image generation for that image type
is perhaps not the best option...

Cheers,

Richard

-- 
_______________________________________________
meta-intel mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-intel

Reply via email to