We'd like meta-intel master to be able to build with OE-Core kirkstone
as well. But Bitbake version in kirkstone does not recognize addplylib
directive leading to parsing errors.
Remove it for now until there is a better solution available.
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Support for Intel(R) oneAPI DPC++/C++ (icx) compiler is being added. So
remove the support for the classic compiler.
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
The main branch only supports building with kirkstone now so we no
longer need this to tweak paths for older branches.
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
zlib has a new release and this fork hasn't rebased onto that version
yet.
Drop this recipe and use the OE-core version for now.
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Due to the variables rename in the scope of inclusive language, the
layer is not compatible with older versions. This change drops all
versions but kirkstone from LAYERSERIES_COMPAT.
Signed-off-by: Andrei Gherzan <andrei@gherzan.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
The initial version of the recipe for Intel OneAPI IPP library.
IPP is an extensive library of ready-to-use, domain-specific functions
that are highly optimized for diverse Intel architectures.
Signed-off-by: Mariia Vtiurina <mariia.vtiurina@intel.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Building with oe-core gatesgarth is no longer supported. Remove from
LAYERSERIES_COMPAT and remove the LLVM 11 patches as well.
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Added logic to make sure, it does not break with old releases.
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Mark the layer as compatible with honister as well now that OE-Core
has switched to using the new override syntax in master branch.
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
It does not provide any essential dependencies.
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
We'd still like to remain compatible with dunfell and gatesgarth core as well.
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
We need a later version of libva than what is available in oe-core for
the media components.
Create our own copy of the recipe and include it only when someone has
included one of meta-intel MACHINEs.
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
We need a later version of libva than what is available in oe-core for
the media components.
Create our own copy of the recipe and include it only when someone has
included one of meta-intel MACHINEs.
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
libva-utils in oe-core moved to latest release, so no need
to carry in meta-intel anymore.
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
libva in oe-core moved to latest release, so no need to
carry in meta-intel anymore.
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
as meta-intel drop support for 4.19 kernel, this bbappend are no longer
required.
reverts commit 108c6938a9.
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Class 'distro_features_check' has moved to 'features_check', which
does not allow dunfell and latest releases to build against zeus
release.
Inherit class based on LAYERSERIES_CORENAMES.
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Make sure that we use the upgraded version of libva-utils
only when using MACHINE value from meta-intel.
For all other cases, libva-utils from oe-core should be used.
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Make sure that we use the upgraded version of libva
only when using MACHINE value from meta-intel.
For all other cases, libva from oe-core should be used.
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Model Optimizer is a cross-platform command-line tool that facilitates
the transition between the training and deployment environment,
performs static model analysis, and adjusts deep learning models for
optimal execution on end-point target devices.
For more details, see:
https://software.intel.com/en-us/openvino-toolkit/deep-learning-cv
Since the recipe requires bits from meta-python, move this to the
dynamic layers section and add meta-python to BBFILES_DYNAMIC.
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
This layer adds zlib-intel, which PROVIDES zlib. If meta-intel is added to a build but a meta-intel MACHINE isn't used then bitbake will warn that there are multiple candidates for zlib:
NOTE: Multiple providers are available for zlib-native (zlib-native, zlib-intel-native)
Consider defining a PREFERRED_PROVIDER entry to match zlib-native
NOTE: Multiple providers are available for zlib (zlib, zlib-intel)
Consider defining a PREFERRED_PROVIDER entry to match zlib
Silence these warnings by adding PREFERRED_PROVIDER defaults in layer.conf.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
This is a new release of Local Manageability Service.
This open-source release deprecates unsupported lms7 and lms8.
This recipe depends on ACE and MeTee library recipes.
Signed-off-by: Alexander Usyskin <alexander.usyskin@intel.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Common clang is a thin wrapper library around clang. Common clang has
OpenCL-oriented API and is capable to compile OpenCL C kernels to SPIR-V
modules.
This adds a bbappend to clang recipe from meta-clang to build the
necessary components and moves it to dynamic layers so it's built only
when clang-layer is included.
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Remove the concept of the common directory and move all the recipes-* dirs
to the top level as a normal layer would be. layer.conf is updated appropriately
Signed-off-by: Saul Wold <sgw@linux.intel.com>
meta-dpdk / meta-qat:
* Move content from meta-intel/common
* Create new basic README/LICENSE files from meta-intel
* Create new layer.conf files
* Fill out the maintainers files
meta-intel:
* update the maintainers files
* bump the meta-intel layer version
* add layer recommend
No other content changes made in this commit.
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
This means mismatched layers are more clearly identified to the user in
cases where compatibility has not been tested.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
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>
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>
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>
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>
