Since Quark is getting depercated remove reference and WKS file
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
This is an early step to removing the meta-quark machine type, as
the Quark processor has been EOL'ed by Intel, this release will
remove it from the kernel recipes
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
This commit adds the 4.14.0-LTS kernel, but does not change the
PREFERRED_VERSION. This will be updated later, to use this kernel
set PREFERRED_VERSION in your local.conf or distro.conf files
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
This has a SRCREV update to bring linux-intel to HEAD with some
audio and pnp patches.
The refactor moves the selection of branch to the versioned recipe
so we can have a shared linux-intel-lts repo with multiple LTS version
branches.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Non-Intel* machines did not get COMPATIBLE_MACHINE set at all, allowing
the package to be built when it probably shouldn't have been. For
example, it would be built when the MACHINE was set to qemux86. This
caused lttng-modules to fail because lttng-modules only gets patched
for our kernel when an Intel MACHINE was being used in order to maintain
Yocto Project Compatibility status.
By setting the default it fails when an invalid MACHINE is used. Note
that while qemux86 is not a compatible MACHINE, the kernel itself does
have the necessary components to run under qemu.
Also change the COMPATIBLE_MACHINE overrides to use the x86-intel-common
override instead of machine-specific overrides since they all have the
same value.
[YOCTO #12278].
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Saul Wold <sgw@linux.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>
do_uefiapp_deploy copies files into the /boot directory of the rootfs
and thus, like do_rootfs, should run under pseudo so that the files
end up being owned by root.
This did not trigger the uid leak check, perhaps because the task runs
later.
For some (still unknown reason), sometimes the installed files did end
up being owned by root, which tripped up a swupd test because the
system update randomly included unexpected changes to bootx64.efi or
rmc.db. With this change, they are owned by root consistently.
Signed-off-by: Patrick Ohly <patrick.ohly@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
meta-tlk gets moved to a standalone layer since it's can't be
properly made Yocto Project Compatible, move it out of meta-intel
to allow meta-intel to be fully Compatible.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Adding the special override limits the impact of the append to
just when we are building for meta-intel machines
Signed-off-by: Saul Wold <sgw@linux.intel.com>
This reverts commit 075b81ae1b.
The audio backports in "c27cfdc linux-intel/4.9: Update kernel SRCREVs"
fixed the broken snd_soc_skl module, fixing the issue this was working
around.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
We never hit this because we're usually only building core-image-rt with
the -rt kernel.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Depmod during do_install is irrelevant when cross-compiling.
Remove the depmod steps during do_install.
Signed-off-by: sweeaun <swee.aun.khor@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Depmod during do_install is irrelevant when cross-compiling.
Remove the depmod steps during do_install.
Signed-off-by: sweeaun <swee.aun.khor@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
oe-selftest leaves python bytecode around for the selftests it
has found making git status dirty.
Add .gitignore that hides those files from git. While we're at it,
ignore some other common patterns too.
Signed-off-by: Mikko Ylinen <mikko.ylinen@linux.intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
This patch is only used with the Intel Production kernel as it has a back
port of the HRTimer code which iwlwifi uses so modify the kernel version check.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
With the SRCREV bump in OE-core, all the firmware bits we need are
already included so we don't need this anymore.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Its important to keep backport-iwlwifi in sync with the proper firmware,
otherwise it may stop working with no immediately obvious cause.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Instead, pin to the latest commit in the release branch.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Use the new x86-x32 override to set the EFI_PROVIDER to grub-efi
which can build without any external libraries, thus just build
in 64bit mode without x32 libraries.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
The Quick Assist Software is specific to certain Intel hardware
and not needed by all, it should be a standalone additional software
layer and not part of the core Intel (meta-intel) BSP.
This is done in part for better Yocto Project Layer Compatibility
Signed-off-by: Saul Wold <sgw@linux.intel.com>
DPDK is now a Linux Foundation project and as such not completely
Intel based, therefore move this to it's own layer so that others
can use.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
linux-intel change summary:
* Revert "x86/acpi: Restore the order of CPU IDs"
* Bluetooth driver fix
* DRM update
yocto-kernel-cache change summary:
* Fix warnings with core2-32
* Add BRCFMAC_PCIE to support some broadcomm wifi drivers
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
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>
