summaryrefslogtreecommitdiffstats
path: root/conf/layer.conf
AgeCommit message (Collapse)Author
2017-05-06conf: set recipe maintainersRoss Burton
Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2016-11-02layer.conf: Remove BBMASK'ing itemsSaul Wold
Having BBMASKS and DISTRO_FEATURES causes issue with sstate in certain situations Signed-off-by: Saul Wold <sgw@linux.intel.com>
2016-08-03rmc: Add recipe and bbclass for RMC featureJianxun Zhang
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 intelligently according to the type of board it is running on. To Enable this feature: add the two lines in conf file: DISTRO_FEATURES_append = " rmc" EFI_PROVIDER = "rmc-systemd-boot" Based on Saul Wold's initial work on a feature switch, RMC patches in systemd-boot, installer and gnu-efi aren't built unless the feature is enabled. For a supported board, this feature can : () show and boot with board-specific boot entries in boot menu in live-boot and post-installation. () apply a kernel cmdline fragment to the end of cmdline to boot Linux kernel. This is effective for any boot entry user chooses in boot menu. () create directory and deploy files only for the type of the running board to target's file systems. What left on target after installation is just same as the result from installing a conventional image customized for a single type of hardware. To add support of new boards, a new variable RMC_BOARD_DATA_DIRS is the interface to developers. How-to information will be provided with examples in following patches. 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>
2015-10-27conf: Add a direct path to common recipesJoonas Lahtinen
By adding the direct path to recipes in common directories we allow upper layers to further extend the recipes. Without the patch the extending recipes look like this: require common/recipes-foo/bar/baz.inc With this patch the include can be written like in other layers: require recipes-foo/bar/baz.inc Signed-off-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2015-08-28Remove older platform specific BSPsSaul Wold
The intel-core* BSPs supercede these older BSPs therefore it's time to remove these older platform specific bsps. Bump LAYERVERSION to 3 to allow the Autobuilder to know that these BSPs have been removed. Signed-off-by: Saul Wold <sgw@linux.intel.com>
2014-10-01layer.conf: Avoid conflicts with sub-layersNitin A Kamble
The layer priority is getting ignored because the same set of files are visible in the meta-intel layer as well as any of its sub layers. The layer pattern for recipe files is changed from "^${LAYERDIR}/" to "^${LAYERDIR}/common" to stop unintentionally including the sub-layer recipe files in the meta-intel layer. Fixes Bug: [YOCTO #6552] Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
2014-09-18layer.conf: Bumping LAYERVERSIONElizabeth Flanagan
As we've retired some BSPs we'll need to bump LAYERVERSION so that the autobuilder does not fail out on them. Signed-off-by: Elizabeth Flanagan <elizabeth.flanagan@intel.com> Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
2014-03-26Remove chiefriver, sys940x & n450 BSPsNitin A Kamble
Configuration for the chiefriver, sys940x, sys940x-noemgd, n450 BSPs are deleted. The consolidated BSPs viz intel-corei7-64 and intel-core2-32 support these boards. As part of the usual retirement process, a heads-up email was sent to the meta-intel mailing list requesting any feedback regarding retirement of these BSPs. The community did not had any concerning feedback to reconsider the retirement decision. The MAINTAINERS file and the layer version of the meta-intel layer are updated to reflect removal of the BSPs. Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> CC: Darren Hart <dvhart@linux.intel.com> Reviewed-by: Darren Hart <dvhart@linux.intel.com>
2013-01-07layer.conf: Use .= for adding to BBPATH and += to BBFILESKhem Raj
Fixes parsing errors which is appearing after this commit to meta-openembedded http://cgit.openembedded.org/meta-openembedded/commit/?id=3c21a46020bd0816579648f684c41dbd6333583e This triggers exception NameError: name 'base_contains' is not defined without this change Avoid the immediate expansion operator (:=) which caused base_contains added in the previous commit to fail to expand at the time the meta-intel layer configs are parsed and replace it with one of the append operators (.= or +=) that allows for delayed variable expansion. Signed-off-by: Khem Raj <raj.khem@gmail.com> Acked-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Darren Hart <dvhart@linux.intel.com>
2012-10-12emgd-driver-bin: add custom-licenses dir for emgd recipe LicensesNitin A Kamble
Add a directory common/custom-licenses to store license texts of recipes in meta-intel layer using custom licenses. Adding these licenses text for emgd-driver-bin recipe: - Intel-software-license-emgd-1.14 - Intel-user-space-graphics-driver-binary-license-emgd-1.14 This takes care of this build warning: WARNING: emgd-driver-bin: No generic license file exists for: Intel-binary-only in any provider This addresses one of the issue reported in the bug: [YOCTO #3238] Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
2012-08-15layer.conf: Clarify BBFILES comments regarding recipe-* directoriesTrevor Woerner
The recipes are no longer stored in a "packages" directory but in directories under recipes-*. Signed-off-by: Trevor Woerner <twoerner@gmail.com> Signed-off-by: Darren Hart <dvhart@linux.intel.com>
2011-11-21meta-intel: make meta-intel itself a layerTom Zanussi
meta-intel contains a set of BSP layers, but is not itself a layer. Make it a layer to make it easy to share common intel-specific files between BSPs. Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>