Re: [meta-intel] [PATCHv5 08/10] rmc: support post-installation hook POSTINSTALL.sh

On Wed, 2016-08-03 at 11:04 -0700, Jianxun Zhang wrote: > 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

Re: [meta-intel] [PATCHv5 07/10] rmc: support broxton-m platform

On Wed, 2016-08-03 at 11:04 -0700, Jianxun Zhang wrote: > Add broxton-m fingerprint and global kernel bootparam fragment > into rmc. > > Signed-off-by: Jianxun Zhang Reviewed-by: Saul Wold > --- >  

Re: [meta-intel] [PATCHv5 05/10] rmc: add recipe and bbclass for RMC feature

On Wed, 2016-08-03 at 11:04 -0700, Jianxun Zhang wrote: > RMC Feature is based on RMC project, systemd-boot, EFI installer > to enable a single generic image, built for multiple platforms, > automatically applies customization and quirks specific to a type > of boards at runtime. > > In another

Re: [meta-intel] [PATCHv5 04/10] EFI installer: deploy board-specific data and kernel cmdline

On Wed, 2016-08-03 at 11:04 -0700, Jianxun Zhang wrote: > 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

Re: [meta-intel] [PATCHv5 03/10] systemd-boot: load board-specific entry and kernel cmdline

On Wed, 2016-08-03 at 11:04 -0700, Jianxun Zhang wrote: > Invoke RMC APIs in this bootloader to query board-specific data > from RMC database(DB) file on ESP. Data can be boot entries or a > global kernel boot command line fragment specific to a type of > board supported in RMC DB. > > Bootloader

Re: [meta-intel] [PATCHv5 01/10] rmc: Add Runtime Machine Configuration (RMC) project

On Wed, 2016-08-03 at 11:04 -0700, Jianxun Zhang wrote: > RMC recipe fetch RMC project and build it more than once in > build time: > > RMC tool is built for host architecture (native). The tool for > host is used to generate RMC database in build time. > > RMC tool is also built for target

[meta-intel] [PATCHv5 08/10] rmc: support post-installation hook POSTINSTALL.sh

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

[meta-intel] [PATCHv5 06/10] rmc: document and examples for RMC feature

Provide a README for RMC feature. Also check in fingerprints and configuration data for several boards as examples for users. They can be used for validation too. Signed-off-by: Jianxun Zhang --- .../rmc/boards/T100-32bit/BOOTENTRY.CONFIG | 2 +

[meta-intel] [PATCHv5 04/10] EFI installer: deploy board-specific data and kernel cmdline

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

[meta-intel] [PATCHv5 03/10] systemd-boot: load board-specific entry and kernel cmdline

Invoke RMC APIs in this bootloader to query board-specific data from RMC database(DB) file on ESP. Data can be boot entries or a global kernel boot command line fragment specific to a type of board supported in RMC DB. Bootloader queries a file blob named BOOTENTRY.CONFIG from RMC DB first. In

[meta-intel] [PATCHv5 05/10] rmc: add recipe and bbclass for RMC feature

RMC Feature is based on RMC project, systemd-boot, EFI installer to enable a single generic image, built for multiple platforms, automatically applies customization and quirks specific to a type of boards at runtime. In another word, you will see a single image behaves differently and

[meta-intel] [PATCHv5 02/10] gnu-efi: Add GUID for SMBIOS 3 entry point structure

UEFI spec has different GUIDs for 32 and 64 bit SMBIOS entry point structure. This change adds definition for 64 bit GUID, so that software linked with gnu-efi can have it for x86_64 architecture. Signed-off-by: Jianxun Zhang ---

[meta-intel] [PATCHv5 00/10] Runtime Machine Configuration (RMC)

Hi Saul, Tom & others, This is the V5 submission of RMC work with new enhancements and fixes over V4 also with some minor adjustments in rmc README file and commit messages. I tried my best to keep doc, commit msg and function consistent when we modify the feature's behavior back and forth. Feel

[meta-intel] [PATCHv5 01/10] rmc: Add Runtime Machine Configuration (RMC) project

RMC recipe fetch RMC project and build it more than once in build time: RMC tool is built for host architecture (native). The tool for host is used to generate RMC database in build time. RMC tool is also built for target architecture, so that scripts in user space can call RMC tool on a running

[meta-intel] [PATCH 1/2] meta-isg: zlib-qat: fix for unpack and patch error

zlib-qat is different from other packages in the way that it has a patch present in a zip file that is unpacked and applied on top of zlib. This results in errors when doing an incremental build using bitbake. To resolve, splitted do_patch into two - one to unpack the qat patch and apply it on

[meta-intel] [PATCH 2/2] meta-isg: openssl-qat: fix for patch error

openssl-qat is different from other packages in the way that it has a patch present in a zip file that is unpacked and applied on top of openssl. This results in patch errors when doing an incremental build using bitbake. To resolve, splitted do_patch into two - one to unpack the qat patch and

[meta-intel] [PATCH 0/2] Fix build with zlib-qat and openssl-qat

Dear Maintainer(s), These patches will fix the unpack and patch error causes due to incremental builds of zlib-qat v0.4.7-002 and openssl-qat v0.4.9-009. These packages needs a patch present in a zip file that is unpacked and applied on top of zlib and openssl respectively. So the work around is