There was a patch back-ported into the linux-intel kernel that
also requires a patch to lttng-modules for the updated API.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
The COMPATIBLE_MACHINE entry for qat recipes is set to 'null'. This
will prevent arbitrary machines from trying to use the qat functionality.
A compatible MACHINE must define itself as such for the qat recipes.
Embedding BSP specific knowledge into the recipe will cause the recipe to
slowly get out of date.
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
The COMPATIBLE_MACHINE entry for dpdk recipes is set to 'null'. This
will prevent arbitrary machines from trying to use the dpdk functionality.
A compatible MACHINE must define itself as such for the dpdk recipes. Also
the BSP aware target machine was similarly moved to the BSP. Embedding BSP
specific knowledge into the recipe will cause the recipe to slowly get out
of date.
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
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>
GitHub has confirmed that the /archive/ tarballs that are generated on demand
from git tags are not persistant and can change over time.
This is no longer an academic problem as this has been observed occuring.
libyami doesn't have any official maintainer-generated tarballs, so switch to
fetching over git.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
GitHub has confirmed that the /archive/ tarballs that are generated on demand
from git tags are not persistant and can change over time.
This is no longer an academic problem as this has been observed occuring.
thermald doesn't have any official maintainer-generated tarballs, so switch to
fetching over git.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
This new image recipe creates an image from the artifacts
obtained after building core-image-tiny-initramfs, it boots
directly to a tiny rootfs provided by initrd
Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
Includes stable updates from v4.4.77 to v4.4.87, and adds the fix to the
recently disclosed Bluetooth vulnerability.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
FILESEXTRAPATHS was being added to unconditionally. Use the
intel-x86-common MACHINEOVERRIDE to fix the issue.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
FILESEXTRAPATHS was being added to unconditionally. Use the
intel-x86-common MACHINEOVERRIDE instead.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
FILESEXTRAPATHS was being being added to globally. Fix by using the
intel-x86-common MACHINEOVERRIDE.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
FILESEXTRAPATHS was being set globally. Use the intel-x86-common
MACHINEOVERRIDE to fix this issue.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
do_compile and do_deploy were being appended to unconditionally. Fix the
issue by using the intel-x86-common MACHINEOVERRIDE.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
FILESEXTRAPATHS was being set globally for every linux-yocto recipe. Use
the intel-x86-common MACHINEOVERRIDE on each to fix the issue.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Fix yocto project compatibility issue: was using raw _appends, without a
machineoverride.
Fix not pinning to a specific commit ID. The firmware could be updated,
which would change the hash and break the build temporarily.
Fix naming. There are several similarly named firmware blobs (e.g.,
iwlwifi-8265-31) so not using the real name of the blob was confusing.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
This updates the kernel cache srcrev to HEAD with a version update tag
The RT kernel is updated to RT patch 4.9.47-rt37
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Like the last few releases, just float on OE-core's SRCREVs.
There is no reason the linux-yocto 4.12 kernel shouldn't work on our
hardware, and in my quick testing, it does.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Since it's possible for other BSPs to also use the DPDK, this can
allow that BSP to be repsonsible for handling it if there is a more
optimized version.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Some toolchains may have configured itself with ssp in
such cases just removing -fstack-protector-strong is not
enough to disable ssp, additionally disabling it on
cmdline is required too
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Now that the backport-iwlwifi packages play nicely with the normal
modules we don't need to remove their files.
Also we discovered that backport-iwlwifi breaks non-Intel wifi, so only
have it as an option rather than the default.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
This updates the meta SRCREV to include the following fixes:
1341c53 Mikko Ylinen intel-common: disable ixgbe modules
6514df4 Mikko Ylinen ktypes/standard: enable CONFIG_CRYPTO_CCM and GCM
ad71574 Mikko Ylinen skylake/audio: enable CONFIG_CRC8 to build soundwire driver
0dd1939 Bruce Ashfield wifi: drop BRCMFMAC_PROTO_MSGBUF, since it is selected
And both the kernel SRCREV to included some patches including:
core: x86/acpi: Restore the order of CPU IDs
Signed-off-by: Saul Wold <sgw@linux.intel.com>
snd-soc-skl module init fails with an error:
snd_soc_skl 0000:00:0e.0: ipc: set large config fail, err: -110
but the module remains loaded. An alternative driver 'snd-hda-intel'
is also loaded but snd-soc-skl is "used".
The end result is soundcards are missing (due to the failure)
on, e.g., Intel 570x/Joule.
As snd-soc-skl is known to be problematic, let's blacklist that
and prefer snd-hda-intel to get audio working.
Signed-off-by: Mikko Ylinen <mikko.ylinen@linux.intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
This was based on the secureboot selftests in meta-refkit:
3bf04941a3/meta-refkit/lib/oeqa/selftest/cases/secureboot.py
It had to be modified a bit to work in meta-intel, as we can't depend on
efivar which resides in meta-openembedded. Instead, in order to test
that secureboot is enabled, we first try to boot with an unsigned, then
image signed with incorrect keys, and search for a "Security Violation"
error message in each log. If the image booted successfully or that
error did not occur, something went wrong and the third test becomes
invalid. The third test is simply booting an image that is signed with
the enrolled keys, getting to a login screen and running a simple
command.
Note that these tests can be quite time consuming, as we have to wait
for the first two tests to timeout, and the timeout values have to be
somewhat high as it sometimes takes a while for the ovmf firmware to
come up.
Original work by Mikko Ylinen and Patrick Ohly.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
This patch adds two image recipes and several keys for use in secureboot
selftests. One image is an unsigned comboapp with a startup.nsh file
calling bootx64.efi. The other is a comboapp image signed with the
refkit keys by default. These are the same keys enrolled in the ovmf
firmware. Also included is another set of keys to sign the image with
that do not match the ovmf firmware's enrolled keys.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
This patch adds a couple secureboot elements to ovmf that originated
from refkit. It includes a patch that adds a certificate to the ovmf's
enrolled keys, and an image recipe which calls the enrollkeys app.
Original work by Mikko Ylinen and Patrick Ohly.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
This allows for setting a different kernel config URI without having
to completely reset the main SRC_URI for the kernel also.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
A recent update to OE-core revealed the missing runtime dependency:
ERROR: lms8-8.0.0-7-r0 do_package_qa: QA Issue: /usr/bin/notifyDesktop.sh
contained in package lms8 requires /bin/bash, but no providers found in
RDEPENDS_lms8? [file-rdeps]
But it turns out that notifyDesktop doesn't actually require bash:
$ checkbashisms.pl notifyDesktop.sh
could not find any possible bashisms in bash script notifyDesktop.sh
So just change the shebang line to /bin/sh.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
CC: mikko.ylinen@linux.intel.com
CC: anand.vastrad@intel.com
Signed-off-by: Saul Wold <sgw@linux.intel.com>
A machine configuration file wasn't the correct place to put this in the
first place. It should be in a bbappend, which we now have.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Modify core-image-minimal-initramfs to use the initramfs-framework init
scripts instead of the old ones when using an Intel MACHINE type.
The initramfs-framework scripts are preferred, as they allow for booting
on both live and real images and are more modular, allowing additions
via new modules.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
sbsigntool does not currently work with openssl version 1.1 which was
just added to OE-core, so depend on version 1.0.* instead.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
From Mikko:
gitsm fetcher does not work well with download cache
(submodules never get to the local source mirror) and each
builds ends up cloning ccan.
Move to use git fetcher (with https protocol) for both sbsigntool
and ccan independently to speed up fetching and to get the
mirroring benefits.
The gitsm fetcher limitations are reported in YOCTO #11594.
Signed-off-by: Mikko Ylinen <mikko.ylinen@linux.intel.com>
This syncs us up with the sbsigntool recipe in meta-refkit.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Enable muslx32 build for efilinux. Using -m64 instead of -mx32 in
TUNE_CCARGS as efi needed to be built for 64 bits.
Signed-off-by: sweeaun <swee.aun.khor@intel.com>
[Fixed whitespace error]
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
meta-intel maintains a recipe that installs iwlwifi's LinuxCore wifi
driver releases. For some iwfwifi LinuxCore supported wireless chips, the
best/latest firmware blobs are found in the iwlwifi's linux-firmware.git fork.
See: https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/core_release
This bbappend fetches the -31.ucode (currently, for Intel Wireless 8260
only!) that is the best match for the iwlwifi LinuxCore release built. The
bbappend can later be extended to pull in firmware blobs for other chips too.
Fixes: [YOCTO #11925]
Signed-off-by: Mikko Ylinen <mikko.ylinen@linux.intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Upgrade xf86-video-mga version to 1.6.5. Adapt block/wakeupHandler
signature for ABI 23 patch has been removed as the change already
available from Upstream 1.6.5.
Signed-off-by: sweeaun <swee.aun.khor@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Clang detects more warnings as errors and these fixes address it
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
These patches are interesting from upstreaming point of view as well
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
The scripts run in install target are relevant (and working)
only if the driver installation is run on the build host.
To fix build errors on some setups we add a patch that
skips the scripts completely when cross-compiling.
Signed-off-by: Mikko Ylinen <mikko.ylinen@linux.intel.com>
[sgw - Added missing Upstream-Status]
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Use the "m64" to parse the flag of x86-64 toolchains.
Signed-off-by: Guojian Zhou <guojian.zhou@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Since everything is installed into /usr when usrmerge is enabled,
don't rm /usr! Also the is not needed for anything do
don't create it in the first place.
[YOCTO #11882]
Signed-off-by: Saul Wold <sgw@linux.intel.com>
