diff options
| author | Jianxun Zhang <jianxun.zhang@linux.intel.com> | 2016-08-03 11:04:15 -0700 |
|---|---|---|
| committer | Tom Zanussi <tom.zanussi@linux.intel.com> | 2016-08-03 17:37:11 -0500 |
| commit | daa587ed5c950cdcbc3a4b2561fb92209c0784ec (patch) | |
| tree | abb5681569ce93984f4112dc12559d70c6dbe2f0 /conf/layer.conf | |
| parent | 7d3305235702a7c730ea9af9db6b00156e664194 (diff) | |
| download | meta-intel-daa587ed5c950cdcbc3a4b2561fb92209c0784ec.tar.gz | |
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 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>
Diffstat (limited to 'conf/layer.conf')
0 files changed, 0 insertions, 0 deletions