nGraph Library is an open-source C++ library and runtime/compiler suite
for Deep Learning ecosystem. For more details, see:
https://www.intel.ai/ngraph/
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
OE-core has dropped support for 5.0 and introduced 5.2 linux-yocto
reference kernel. Make changes to remain in sync.
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
The library isn't explicitly linking against these libs and loads them
at runtime. Add these to RDEPENDS to make sure these are present.
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
The skylake tune introduced on 04510bfa
Currently disables qemu-usermode by default, due to the lack
of support from QEMU to several of the Intel instruction set
extensions introduced within the few latest generations of
CPU architectures (e.g. QEMU does not support avx2)
While there is a good reason to perform the removal of qemu-usermode
from MACHINE_FEATURES, there are several components within the
build system that rely on it for proper compilation and behavior,
for example anything that uses gobject data introspection or even
the components like the chromium web browser require to run a QEMU
for the target architecture to build successfully.
There is no reason why we can't have those components built without
sacrificing the cpu (most) optimizations.
The process I followed on meta-chromebook to enable an optimized build
and whats being upstreamed by this patch is that by doing some
reverse engineering, I was able to figure out which instruction
set extensions are not compatible with QEMU Skylake-Client, by
performing a bit gcc magic from inside QEMU (target) to get the
available optimizations for the native architecture (which is
actually our target in this case).
These are all (not surprisingly) the avx2 extensions, listed as
follows:
-mno-avx
-mno-avx2
-mno-avx512f
-mno-avx512er
-mno-avx512cd
-mno-avx512pf
-mno-avx512dq
-mno-avx512bw
-mno-avx512vl
-mno-avx512ifma
-mno-avx512vbmi
-mno-avx512vbmi2
-mno-avx512vnni
-mno-avx512bitalg
Specifically disabling these manually (for now), allows us to build an
optimized system for the skylake/skylake based architectures (e.g. KabyLake)
while keeping the capability of using qemu-usermode, as a side note GCC
does show more unavailable optimization tunes, (hence why there might be
some warnings), but getting rid of these specifically seems enough to make
it run happily in qemu-usermode.
Basically the MACHINE_FEATURES variable is able to dictate how we will tune
the build for our device, if qemu-usermode is present, TUNE_CCARGS will
expand as follows:
TUNE_CCARGS=" -m64 -march=skylake -mtune=skylake -mno-avx -mno-avx2
-mno-avx512f -mno-avx512er -mno-avx512cd -mno-avx512pf -mno-avx512dq
-mno-avx512bw -mno-avx512vl -mno-avx512ifma -mno-avx512vbmi -mno-avx512vbmi2
-mno-avx512vnni -mno-avx512bitalg -mfpmath=sse"
Whats this means is that the build will be tuned for skylake architectures,
enabling all possible extensions, (MOVBE, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1,
SSE4.2, POPCNT, AES, PCLMUL, FSGSBASE, RDRND, FMA, BMI, BMI2, F16C, RDSEED,
ADCX, PREFETCHW, CLFLUSHOPT, XSAVEC and XSAVES) minus the ones QEMU is unable
to run, which will result in an illegal instruction error, notice the tune is
kept as skylake.
Whilst, if qemu-usermode is not found on MACHINE_FEATURES, TUNE_CCARGS will
expand to:
TUNE_CCARGS=" -m64 -march=skylake -mtune=generic -mavx2 -mfpmath=sse"
Which is exactly what its set to with the current tune, so this patch should
be harmless, and only extend current functionality, we will still keep
qemu-usermode disabled by default (hence enabling avx2) but the user would
have the capability to decide how the skylake tune will be handled.
As the GCC manual states, we should really try to avoid using mtune=generic
when possible, and this patch allows us to do so [1].
This patch also addresses a problem on which the current skylake tune includes
tune-core2.inc instead of tune-corei7.inc to get the list of AVAILTUNES
and PACKAGE_EXTRA_ARCHS.
Right now, AVAILTUNES are set as follows:
AVAILTUNES=" x86 x86-64 x86-64-x32 i586 i686 core2-32 core2-64 core2-64-x32
skylake-64"
Where the proper set should be (after this patch):
AVAILTUNES=" x86 x86-64 x86-64-x32 i586 i686 core2-32 core2-64 core2-64-x32
corei7-32 corei7-64 corei7-64-x32 skylake-64"
When (if), QEMU gains support for the AVX2 instruction set extensions these
can be easily removed to provide full support for qemu-usermode.
[1] https://gcc.gnu.org/onlinedocs/gcc-9.1.0/gcc/x86-Options.html
Signed-off-by: Alejandro Enedino Hernandez Samaniego <aehs29@gmail.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
The latest version is 2.27.0, not 2.0.27. Also make sure that we are
pointing to the release commit.
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
For LICENSE updates, pleaes check:
https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/backport-iwlwifi.git/commit/COPYING?h=release/core40&id=8307aa7b67e71e4d4abe1693107eba63cfd3702b
More information about this release
can be found here:
https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/backport-iwlwifi.git/log/?h=release/core45
This update is tested on NUC7 having 'Intel(R) Dual Band Wireless AC 8265' wireless module.
Supported firmwares/devices:
iwlwifi-7265D-29.ucode
iwlwifi-7265-17.ucode
iwlwifi-3168-29.ucode
iwlwifi-3160-17.ucode
iwlwifi-7260-17.ucode
iwlwifi-8265-36.ucode
iwlwifi-8000C-36.ucode
iwlwifi-9260-th-b0-jf-b0-46.ucode
iwlwifi-9000-pu-b0-jf-b0-46.ucode
iwlwifi-ty-a0-gf-a0-48.ucode
iwlwifi-so-a0-gf-a0-48.ucode
iwlwifi-so-a0-hr-b0-48.ucode
iwlwifi-so-a0-jf-b0-48.ucode
iwlwifi-cc-a0-48.ucode
iwlwifi-QuQnj-b0-jf-b0-48.ucode
iwlwifi-QuZ-a0-jf-b0-48.ucode
iwlwifi-QuZ-a0-hr-b0-48.ucode
iwlwifi-Qu-b0-jf-b0-48.ucode
iwlwifi-Qu-c0-hr-b0-48.ucode
iwlwifi-QuQnj-a0-hr-a0-48.ucode
iwlwifi-QuQnj-b0-hr-b0-48.ucode
iwlwifi-Qu-b0-hr-b0-48.ucode
iwlwifi-QuQnj-f0-hr-a0-48.ucode
iwlwifi-Qu-a0-jf-b0-48.ucode
iwlwifi-Qu-a0-hr-a0-48.ucode
Most of the above firmwares are provided by below recipe version (20190815):
https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-kernel/linux-firmware/linux-firmware_20190815.bb
SRCREV = "07b925b450bfb4cf3e141c612ec5b104658cd020"
SRC_URI = "git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git"
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Add 64-bit new machine (intel-skylake-64) with -march=skylake
and avx2 instruction-set set up.
We do see a qemu-usermode failure at build time, on setup of
avx2 instruction-set as QEMU does not support AVX instruction
set.
Check this:
https://bugs.launchpad.net/qemu/+bug/1818075
So to bypass this issue disabling qemu-usermode for intel-skylake-64
machine.
Due to above limitation and in order to not affecting existing
machines, this new machine is being proposed to add.
A quick performance comparision between intel-corei7-64 vs intel-skylake-64 machines
Measurements are in time, taken by the benchmark tests. Less is better.
Test/Benchmark intel-corei7-64 intel-skylake-64
(1) CppPerformanceBenchmarks (Test: Math Library)
(1st) 5m 15.70s 4m 36.39s
(2nd) 5m 16.37s 4m 36.51s
(3rd) 5m 15.54s 4m 37.80s
CppPerformanceBenchmarks is a set of C++ compiler performance benchmarks.
(2) AOBench
(1st) 0m 35.07s 0m 28.74s
(2nd) 0m 34.90s 0m 28.72s
(3rd) 0m 34.85s 0m 28.89s
AOBench is a lightweight ambient occlusion renderer, written in C. The
test profile is using a size of 2048 x 2048.
(3) C-Ray
(1st) 320 seconds 232 seconds
(2nd) 320 seconds 232 seconds
(3rd) 321 seconds 232 seconds
C-Ray, a simple raytracer designed to test the floating-point CPU performance.
For this patch, 'bitbake world' gets successfully built with latest poky master.
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Switch the driver configuration MEDIA_BUILD_FATAL_WARNINGS to OFF so
-Werror is not used. Also patch out the use of
-Werror=implicit-function-declaration to prevent errors when building
with gcc9.
| cc1plus: error: '-Werror=' argument
'-Werror=implicit-function-declaration' is not valid for C++ [-Werror]
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
The Intel(R) Graphics Compute Runtime for OpenCL(TM) is an open source
project to converge Intel's development efforts on OpenCL(TM) compute
stacks supporting the GEN graphics hardware architecture.
For more details, see:
https://01.org/compute-runtime
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
* Use clang and lld for native builds to remain in sync with clang layer.
* fix the license field to point to correct block of license in source
file.
* Include patches to ignore warnings being marked as errors when building
with clang and to fix an issue with inclusion of debug functions when
NDEBUG is defined.
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Also include a patch to not build tests to prevent passing the build
flag to every component that is built out of tree.
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Switch to using latest on ocl-release-80 branch and to using
using lld for native builds to remain in sync with clang layer.
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Since this is managed as a separate repository, build it as a separate
component instead of bundling with LLVM/clang.
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Includes below CVE fixed:
CVE-2019-14283
CVE-2019-14284
tag 'v4.14.138': (34 commits)
Linux 4.14.138
spi: bcm2835: Fix 3-wire mode if DMA is enabled
cgroup: Fix css_task_iter_advance_css_set() cset skip condition
cgroup: css_task_iter_skip()'d iterators must be advanced before accessed
cgroup: Include dying leaders with live threads in PROCS iterations
cgroup: Implement css_task_iter_skip()
cgroup: Call cgroup_release() before __exit_signal()
bnx2x: Disable multi-cos feature.
mvpp2: refactor MTU change code
tun: mark small packets as owned by the tap sock
net/mlx5e: Prevent encap flow counter update async to user query
compat_ioctl: pppoe: fix PPPOEIOCSFWD handling
tipc: compat: allow tipc commands without arguments
NFC: nfcmrvl: fix gpio-handling regression
net: sched: Fix a possible null-pointer dereference in dequeue_func()
net: phylink: Fix flow control for fixed-link
net/mlx5: Use reversed order when unregister devices
net: fix ifindex collision during namespace removal
net: bridge: mcast: don't delete permanent entries when fast leave is enabled
net: bridge: delete local fdb on device init failure
...
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
It's useful to have these so someone who is looking at layer index
as an example knows what the component is.
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Otherwise everything after underscore either gets ignored (in case of
devtool) or converted to a hyphen. This ensures that the version is
handled more consistently.
Also add a custom GITTAGREGEX check to check for upstream releases.
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
We include the firmware as part of initramfs image that is used for
live images. Make sure that we include this module for others as well.
Also include the kernel module for all images instead of relying on
"linux-modules" using MACHINE_EXTRA_RRECOMMENDS. Use
MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS instead to pull in i915 module so it
works for all images based on packagegroup-core-boot.
Fixes [YOCTO #13446]
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
For changes, see:
https://github.com/intel/libyami/blob/1.3.2/NEWS
Remove all the patches fixing warnings converted to errors when using
clang. Most of these have been fixed and others are trivial enough to be
ignored. Pass -Wno-error to CXXFLAGS to ignore these.
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Updates -rt patchset to -rt24.
Also updates the meta revision to include changes:
960be421 intel-common-drivers: enable RANDOM_TRUST_CPU for Intel BSPs
bc74ed4e features: add support for RANDOM_TRUST_CPU
a52c1d35 security.cfg: unset HARDENED_USERCOPY_FALLBACK
772b96e0 kver: bump to v4.19.57
4c8cf83d scsi-debug: include core scsi support for standalone inclusion
3017e92f features/security: Add more kernel hardening fragments
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
4.19.62 stable release
This rlease has CVEs fixed:
CVE-2019-14283
CVE-2019-14284
CVE-2019-13631
Linux 4.19.62
platform/x86: SEP BUG fix for lbrcollection
platform/x86: SEP bug fix, use of undeclared var
drm/i915/cfl: Add a new CFL PCI ID.
net: sched: verify that q!=NULL before setting q->flags
mm: vmscan: scan anonymous pages on file refaults
KVM: nVMX: Clear pending KVM_REQ_GET_VMCS12_PAGES when leaving nested
KVM: nVMX: do not use dangling shadow VMCS after guest reset
ext4: allow directory holes
ext4: use jbd2_inode dirty range scoping
jbd2: introduce jbd2_inode dirty range scoping
mm: add filemap_fdatawait_range_keep_errors()
ext4: enforce the immutable flag on open files
ext4: don't allow any modifications to an immutable file
perf/core: Fix race between close() and fork()
perf/core: Fix exclusive events' grouping
MIPS: lb60: Fix pin mappings
gpio: davinci: silence error prints in case of EPROBE_DEFER
dma-buf: Discard old fence_excl on retrying get_fences_rcu for realloc
dma-buf: balance refcount inbalance
net: bridge: stp: don't cache eth dest pointer before skb pull
net: bridge: don't cache ether dest pointer on input
net: bridge: mcast: fix stale ipv6 hdr pointer when handling v6 query
...
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Use a custom regex to make sure we exclude tags starting with something
other than igc and those that include versions starting with 19.
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Upstream doesn't support building for x32. Instread of
patching makefile for x32 and risk runtime failures,
disable the build.
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Upstream doesn't support building for x32. Instread of
patching makefile for x32 and risk runtime failures,
disable the build.
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Upstream doesn't support building for x32. Instread of
patching makefile for x32 and risk runtime failures,
disable the build.
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
mediasdk & media-driver doesn't support building for x32.
Instead of patching makefile to build for x32 and risk runtime
failures, do not include in x32 build.
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
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>
Drop library packaging workarounds - not needed with a new sources.
Signed-off-by: Alexander Usyskin <alexander.usyskin@intel.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Added third party license info:
"ittnotify, 3-clause BSD license
Copyright (c) 2011, Intel Corporation
See full copyright notice and license text in
src/cpu/jit_utils/jitprofiling/LICENSE.BSD"
Release highlights can be found here:
https://github.com/intel/mkl-dnn/releases/tag/v1.0
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Release details can be found here:
https://github.com/intel/hdcp/releases
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
igc needs components from LLVM and clang to be built. Move it to
dynamic-layers/clang-layer so world builds don't fail when clang layer
is not available.
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
