iucode-tool needs the arpg API which is not part of MUSL, so add argp-standalone as
a dependency. The arpg library is also required for linking, so add a patch to
the Makefile.am, which is added again based on tclib being MUSL
Signed-off-by: Saul Wold <sgw@linux.intel.com>
The license info changed due to update of year and formatting
They also changed the toplevel directory in the tarball from
iucode_tool -> iucode-tool
CVE: CVE-2017-0357
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Move script to the files/intel-x86-common sub-dir which will be used
based on the added override in MACHINEOVERRIDES
Signed-off-by: Saul Wold <sgw@linux.intel.com>
foo
Signed-off-by: Saul Wold <sgw@linux.intel.com>
RMC installer copies RMC entries after copying default entries. But
default entries aren't overwritten when RMC entries have different file
names from them, so they will be kept on target after installation.
RMC Bootloader skips loading default entries when it can get RMC entries
from RMC database file. However, RMC database file isn't deployed onto
target in installation by design.
As a result, default entries show up along with deployed RMC entries once
target reboots after installation.
We cannot get rid of these default entries in RMC deployment section because
it doesn't know which entry file should be removed.
An easier way is not to deploy default entries when any boot entry files
assumingly from RMC are already deployed at a later step. Similar logic
applies to loader.conf too.
Signed-off-by: Jianxun Zhang <jianxun.zhang@linux.intel.com>
Reviewed-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
POSTINSTALL.sh provides developer a final chance to retouch
almost anything deployed on target before unmounting partitions
and reboot at the end of an installation session.
RMC installer executes this script if it can be queried from
RMC database file for the running board.
Some steps to make system bootable still happen after this hook.
Signed-off-by: Jianxun Zhang <jianxun.zhang@linux.intel.com>
Reviewed-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Extend the existing init-install-efi.sh in OE to call RMC tool
so that it can deploy file blobs and a global kernel cmdline
fragment associated to the type of current running board.
At first, it tries to retrieve a special configuration file
INSTALLER.CONFIG associated to the board from RMC database file
on ESP.
If the config file is fetched successfully, installer parses
configuration file to know which file blobs should be deployed
from database to target, also with other necessary information
like FS attributes of deployed file.
If a rule in config file is to create a directory, installer
creates it accordingly. Developer must direct installer to create
new directory first if destination of a file is in that directory
by adding a '/' at the end of a line.
The below is an example of INSTALLER.CONFIG. It directs installer to
deploy a boot entry boot.conf to EFI partition, create a
directory /etc/mylib/ on target's rootfs, and deploy a config
file mylib.conf in the created directory. The first several lines
started with '#' are comment.
efi_entry_dir:root:disk:770:/boot/loader/entries/
boot.conf:root:disk:770:/boot/loader/entries/rmcboot.conf
mylibdir:root:root:770:/tgt_root/etc/mylib/
mylib.conf:root:root:660:/tgt_root/etc/mylib/mylib.conf
When installer cannot get config file for the type of running board,
it skips any board-specific deployment. If a command fails at any
step, installer simply moves to the next.
After all the boot entries are deployed, installer seeks a config file
KBOOTPARAM from RMC database file. In success, it appends the content
of KBOOTPARAM to the end of kernel command line of every deployed
entry. KBOOTPARAM works as a global kernel command line fragment
specific to the type of running board.
The installer is copied and modified from OE:
./recipes-core/initrdscripts/files/init-install-efi.sh:
(OE-Core rev: 031c2f6ced917a81b4f39dca371773d0275ddf73)
Signed-off-by: Jianxun Zhang <jianxun.zhang@linux.intel.com>
Reviewed-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Dates changed in Licence file required CHKSUM update
From the OpenXT Project ( http://openxt.org )
refs: OXT-668
Signed-off-by: Christopher Clark <christopher.clark6@baesystems.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Bump to version 1.3. Upstream has relocated the project to GitLab.com
which this takes into account as well.
Signed-off-by: Doug Goldstein <cardoe@cardoe.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Bumped version to 20150121. Dropped runtime dependency on iucode-tool
which is used to generate the cpio or trim down the data file based on
your CPU. While it can also be used to load the microcode that is not
the recommended method for Linux 3.9 and newer instead you should use
the kernel's built-in early microcode loading facilities.
Signed-off-by: Doug Goldstein <cardoe@cardoe.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Previously iucode-tool was marked as x86-specific but this recipe also
needs to be marked as it depends on iucode-tool.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
The microcode data file released by Intel has microcode for many Intel
processors, which by default all get installed onto the target image.
In some situations it may desirable to choose microcode for only a
selected processor or processors. This change provides an easier way
to filter and select only the microcode of interest for BSPs from
recipe space.
A new variable, UCODE_FILTER_PARAMETERS, is introduced, which can be
defined to contain parameters to the iucode_tool which will filter the
microcode of interest for the BSP under consideration. More
information on the iucode-tool parameters is available here:
http://manned.org/iucode-tool.
This filtering makes the generated microcode files very
machine-specific, hence making the recipe machine-specific. BSPs using
the common Intel kernel will not be using the filtered microcode, and
will be able to share the intel-microcode packages with the common
Intel package arch for the recipe.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Acked-by: Darren Hart <dvhart@linux.intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
The iucode-tool is needed for applying microcode updates from
userland.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
package_deb doesn't yet handle non-ASCII characters in control files, so remove
a unicode "registered trademark" character.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
This recipe provides the microcode datafile for Intel Processors.
The recipe provides:
1. microcode.dat file for microcode updating from user space with the
iucode-tool utility.
2. the microcode cpio file which gets bundled with the initrd to support
microcode loading at early boot time.
[ YOCTO #5114 ]
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Acked-by: Darren Hart <dvhart@linux.intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
iucode_tool is a program to manipulate Intel i686 and X86-64 processor
microcode update collections, and to use the kernel facilities to update
the microcode on Intel system processors.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-Off-By: Nitin A Kamble <nitin.a.kamble@intel.com>
Reviewed-by: Darren Hart <dvhart@linux.intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Remove openssl-qat-module and zlib-qat-module recipes and any
references to them from meta-intel.
This is to remove recipes for obsolete and unmaintained software
ingredients related to QAT.
Signed-off-by Ong Boon Leong <boon.leong.ong@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
This adds a new recipe to build the Intel Quick Assist
Technology Memory Management Module for Zlib.
Signed-off-by: Kishore Bodke <kishore.k.bodke@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
The parted 3.0 release introduced some API changes such as the removal
of mkpartfs. This updates init-install.sh to use mkpart instead.
Fixes [YOCTO #1387]
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Add a /common dir to contain code shared by multiple BSPs in the
meta-intel repo, along with a couple recipes to live there
temporarily.
In this case, there are two BSPs that need to share the common grub2
and associated initramfs-live-install changes (sugarbay and
jasperforest).
The grub2 and associated initramfs-live-install changes will soon be
submitted to the main poky repo, but for now it makes more sense to
keep them here - they're needed for live-install of the two BSPs
mentioned, but they contain a couple hacks that need to be addressed
and are untested with anything else.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
