linux/meta-intel.git/common/recipes-core, branch pyro

intel-microcode: Update to latest 20170511

2017-05-16T15:05:07+00:00

This update also updated the licence checksum as the date has changed The core content of the license has not changed Signed-off-by: Saul Wold

initrdscripts: add support for NVME target install

2017-05-11T02:29:32+00:00

Add awareness of /dev/nvme* block devices to install scripts. As presently written, installer knows only of /dev/sd* and /dev/mmcblk* block devices. Building upon scaffolding put in place by Awais in... 80ec9f627915 ("initrdscripts: handle mmc device as installer medium") (From OE-Core rev: b5a036ce958e3fe24690531712071abc14b48033) Signed-off-by: Joe Konno Signed-off-by: Ross Burton Signed-off-by: Richard Purdie (From Poky rev: 85c9b9f9c602459b32f8f301b161c9a3f6f14d4e) Ported the changes from poky meta layer into BSP layer. As the original commit was changing 2 files, this has been rework for meta-intel layer. [YOCTO #11367] Signed-off-by: Chang Rebecca Swee Fun Signed-off-by: Ng, Wei Tee Signed-off-by: Saul Wold

thermald,iucode-tool,libyami: Add UPSTREAM_CHECK_ variables

2017-05-09T15:29:50+00:00

These variables are used by checkpkg task to figure out if there are a new version of the upstream software. Signed-off-by: Aníbal Limón Signed-off-by: Saul Wold

core-image-tiny-initramfs: Choose WKS_FILE correctly between architectures

2017-03-07T20:22:22+00:00

Signed-off-by: Alejandro Hernandez

iucode-tool: Add support for MUSL

2017-02-10T15:52:49+00:00

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

iucode-tool: Upgrade to 2.1.1

2017-01-24T22:30:59+00:00

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 Signed-off-by: California Sullivan

initramfs-live-install-efi: Make use of new override

2016-11-02T23:31:53+00:00

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 foo Signed-off-by: Saul Wold

rmc: Don't install boot entries when RMC entries exist

2016-08-03T22:43:30+00:00

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 Reviewed-by: Saul Wold Signed-off-by: Tom Zanussi

rmc: Add support for POSTINSTALL.sh post-installation hook

2016-08-03T22:39:16+00:00

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 Reviewed-by: Saul Wold Signed-off-by: Tom Zanussi

EFI installer: Deploy board-specific data and kernel cmdline

2016-08-03T22:37:11+00:00

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 Reviewed-by: Saul Wold Signed-off-by: Tom Zanussi