Jianxun Zhang b9f9710ba4 rmc: Don't install boot entries when RMC entries exist ... 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>		2016-08-03 17:43:30 -05:00
..
initrdscripts	rmc: Don't install boot entries when RMC entries exist	2016-08-03 17:43:30 -05:00
microcode	intel-microcode: Update to the 20160714 version	2016-07-22 09:18:05 -05:00