From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============5585423447226000835==" MIME-Version: 1.0 From: Ricardo Neri Subject: [PATCH 9/9] core-image-efi-initramfs: Re-enable chipsec Date: Fri, 10 Mar 2017 15:36:21 -0800 Message-ID: <1489188981-23886-10-git-send-email-ricardo.neri-calderon@linux.intel.com> In-Reply-To: <1489188981-23886-1-git-send-email-ricardo.neri-calderon@linux.intel.com> List-Id: To: chipsec@lists.01.org --===============5585423447226000835== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Now that we have bumped to v1.2.5+, and everything builds correctly, re-enable chipsec in our ramdisk. Signed-off-by: Ricardo Neri --- meta-luv/recipes-core/images/core-image-efi-initramfs.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-luv/recipes-core/images/core-image-efi-initramfs.bb b/met= a-luv/recipes-core/images/core-image-efi-initramfs.bb index 8f9aa75..5048946 100644 --- a/meta-luv/recipes-core/images/core-image-efi-initramfs.bb +++ b/meta-luv/recipes-core/images/core-image-efi-initramfs.bb @@ -10,7 +10,7 @@ IMAGE_INSTALL =3D "\ psplash kernel-efi-warnings linux-firmware kexec \ " = -X86_ADDITIONS =3D "python-codecs python-subprocess vmcore-dmesg bits \ +X86_ADDITIONS =3D "chipsec python-codecs python-subprocess vmcore-dmesg bi= ts \ kernel-modules" = IMAGE_INSTALL_append_qemux86 =3D "${X86_ADDITIONS}" -- = 2.7.4 --===============5585423447226000835==--