iucode-tool: Add support for MUSL
PATCH 1/2 iucode-tool: Add support for MUSL
iu-code needs the arpg API which is not part of MUSL, so add argp-standalone as a dependency. The arpg library is also required for linking, so add a patch to the Makefile.am
--- ...am-Add-arg-parse-library-for-MUSL-support.patch | 29 ++++++++++++++++++++++ common/recipes-core/microcode/iucode-tool_2.1.1.bb | 6 ++++- 2 files changed, 34 insertions(+), 1 deletion(-) create mode 100644 common/recipes-core/microcode/iucode-tool/0001-Makefile.am-Add-arg-parse-library-for-MUSL-support.patch
common/recipes-core/microcode/iucode-tool/0001-Makefile.am-Add-arg-parse-library-for-MUSL-support.patch new file +29 -0
@@ -0,0 +1,29 @@ +From 5f6826b3a59dedf508d5a6122362d69a4813e8e6 Mon Sep 17 00:00:00 2001 +From: Saul Wold <[email protected]> +Date: Fri, 3 Feb 2017 16:08:51 -0800 +Subject: [PATCH] Makefile.am: Add arg-parse library for MUSL support + +iucode-tool needs argp-standalone when used with MUSL, so add this +patch to the Makefile to link with argp + +Upstream-Status: Pending +Signed-off-by: Saul Wold <[email protected]> +--- + Makefile.am | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/Makefile.am b/Makefile.am +index 415a241..764fb61 100644 +--- a/Makefile.am ++++ b/Makefile.am +@@ -5,6 +5,7 @@ + sbin_PROGRAMS = iucode_tool + man_MANS = iucode_tool.8 + ++iucode_tool_LDADD = -largp + iucode_tool_SOURCES = intel_microcode.h intel_microcode.c iucode_tool.c + EXTRA_DIST = autogen.sh CONTRIBUTING + +-- +2.7.4 +
common/recipes-core/microcode/iucode-tool_2.1.1.bb +5 -1
@@ -16,7 +16,11 @@ LICENSE = "GPLv2+" LIC_FILES_CHKSUM = "file://COPYING;md5=751419260aa954499f7abaabaa882bbe \ file://iucode_tool.c;beginline=1;endline=15;md5=5d8e3639c3b6a80e7d5e0e073933da16" -SRC_URI = "https://gitlab.com/iucode-tool/releases/raw/master/iucode-tool_${PV}.tar.xz" +DEPENDS_append_libc-musl = " argp-standalone" + +SRC_URI = "https://gitlab.com/iucode-tool/releases/raw/master/iucode-tool_${PV}.tar.xz \ + file://0001-Makefile.am-Add-arg-parse-library-for-MUSL-support.patch \ + " SRC_URI[md5sum] = "306d20b43da847812af4bf973f46045d" SRC_URI[sha256sum] = "8f94ec73f5d4d1a6801aaa894fa1c6544d9b27aec16e1a00e18e8241c7e0f6ba"
Signature · 1 line
2.7.4
PATCH 1/1 linux-intel: Add the linux-intel kernel recipe
This introduces the linux-intel kernel recipe for 4.9, this kernel tree is a prodcution tree that contains enabling backports for Intel CPU and Hardware that may be up-streamed in a newer kernel version.
Additional information can be found in this associated wiki page:
https://github.com/01org/linux-intel-4.9/wiki
--- common/recipes-kernel/linux/linux-intel_4.9.bb | 46 ++++++++++++++++++++++++++ 1 file changed, 46 insertions(+) create mode 100644 common/recipes-kernel/linux/linux-intel_4.9.bb
common/recipes-kernel/linux/linux-intel_4.9.bb new file +46 -0
@@ -0,0 +1,46 @@ + +require recipes-kernel/linux/linux-yocto.inc + +KBRANCH ?= "master" +SRCREV_machine ?= "09f886dc5a6945679ed35e6acfbc746f472f0f34" +SRCREV_meta ?= "6fd9dcbb3f0becf90c555a1740d21d18c331af99" + +SRC_URI = "git://github.com/01org/linux-intel-4.9.git;protocol=https;name=machine;branch=${KBRANCH}; \ + git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.9;destsuffix=${KMETA}" + +LINUX_VERSION ?= "4.9.6" + +PV = "${LINUX_VERSION}+git${SRCPV}" + +KMETA = "kernel-meta" +KCONF_BSP_AUDIT_LEVEL = "2" + +KERNEL_FEATURES_INTEL_COMMON = "" + +COMPATIBLE_MACHINE_core2-32-intel-common = "${MACHINE}" +KMACHINE_core2-32-intel-common = "intel-core2-32" +KERNEL_FEATURES_append_core2-32-intel-common = "${KERNEL_FEATURES_INTEL_COMMON}" + +COMPATIBLE_MACHINE_corei7-64-intel-common = "${MACHINE}" +KMACHINE_corei7-64-intel-common = "intel-corei7-64" +KERNEL_FEATURES_append_corei7-64-intel-common = "${KERNEL_FEATURES_INTEL_COMMON}" + +COMPATIBLE_MACHINE_i586-nlp-32-intel-common = "${MACHINE}" +KMACHINE_i586-nlp-32-intel-common = "intel-quark" +KERNEL_FEATURES_append_i586-nlp-32-intel-common = "" + +# For Crystalforest and Romley +KERNEL_MODULE_AUTOLOAD_append_core2-32-intel-common = " uio" +KERNEL_MODULE_AUTOLOAD_append_corei7-64-intel-common = " uio" + +# For FRI2, NUC +KERNEL_MODULE_AUTOLOAD_append_core2-32-intel-common = " iwlwifi" +KERNEL_MODULE_AUTOLOAD_append_corei7-64-intel-common = " iwlwifi" + + +# Functionality flags +KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc" +KERNEL_FEATURES_append = " ${KERNEL_EXTRA_FEATURES}" +KERNEL_FEATURES_append = " ${@bb.utils.contains("TUNE_FEATURES", "mx32", " cfg/x32.scc", "" ,d)}" + +
Signature · 1 line
2.7.4
PATCH 2/2 libva-intel-driver: Update to 1.7.3
In reply to Saul WoldThe upstream has moved their source base from FreeDesktop to github.com/01org
---
.../libva/{libva-intel-driver_1.7.2.bb => libva-intel-driver_1.7.3.bb} | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
rename common/recipes-multimedia/libva/{libva-intel-driver_1.7.2.bb => libva-intel-driver_1.7.3.bb} (89%)common/recipes-multimedia/libva/libva-intel-driver_1.7.3.bb renamed from common/recipes-multimedia/libva/libva-intel-driver_1.7.2.bb +2 -1
@@ -13,7 +13,8 @@ COMPATIBLE_HOST = '(i.86|x86_64).*-linux' DEPENDS = "libva libdrm" -SRC_URI = "http://www.freedesktop.org/software/vaapi/releases/${BPN}/${BPN}-${PV}.tar.bz2" +SRC_URI = "git://github.com/01org/intel-vaapi-driver.git;protocol=https" +SRCREV = "c747c3428cd862869b75e96b737fa61532d6f27f" SRC_URI[md5sum] = "f28ac265f836f7ce881305bd3a282c90" SRC_URI[sha256sum] = "099e7bf6aa826971ec2caff235babf4da995f754e2ca16a73b258671130e67bc"
Signature · 1 line
2.7.4
PATCH 2/2 meta-intel.inc: Enable linux-intel and 4.9 by default for meta-intel hardware
In reply to Saul WoldEnable the linux-intel production kernel for meta-intel by default for 4.9, this will enable using the Intel production kernel.
This is a well tested 4.9 tree that will start to include additional support for the Apollolake and Joule hardware.
--- conf/machine/include/meta-intel.inc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
conf/machine/include/meta-intel.inc +2 -2
@@ -9,8 +9,8 @@ # # Soft set linux-yocto as preferred kernel like x86-base.inc -PREFERRED_PROVIDER_virtual/kernel ??= "linux-yocto" -PREFERRED_VERSION_linux-yocto ?= "4.8%" +PREFERRED_PROVIDER_virtual/kernel ?= "linux-intel" +PREFERRED_VERSION_linux-intel ?= "4.9%" # for Xserver older than 1.13.0 OLD_XSERVER_X86_EXT = "xserver-xorg-extension-dri \
Signature · 1 line
2.7.4
Re: [PATCH 2/2] meta-intel.inc: Enable linux-intel and 4.9 by default for meta-intel hardware
Quoted 16 lines · Saul Wold
Enable the linux-intel production kernel for meta-intel by default for 4.9, this will enable using the Intel production kernel.
This is a well tested 4.9 tree that will start to include additional support for the Apollolake and Joule hardware.
Signed-off-by Saul Wold <[email protected]>--- conf/machine/include/meta-intel.inc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)conf/machine/include/meta-intel.inc +0
-0
conf/machine/include/meta-intel.inc line 12
Quoted 6 lines
conf/machine/include/meta-intel.inc +1
-2@@ -9,8 +9,8 @@ # # Soft set linux-yocto as preferred kernel like x86-base.inc -PREFERRED_PROVIDER_virtual/kernel ??= "linux-yocto" -PREFERRED_VERSION_linux-yocto ?= "4.8%" +PREFERRED_PROVIDER_virtual/kernel ?= "linux-intel"
whats the difference between linux-yocto and linux-intel ?
Quoted 12 lines
conf/machine/include/meta-intel.inc +1
-1+PREFERRED_VERSION_linux-intel ?= "4.9%" # for Xserver older than 1.13.0 OLD_XSERVER_X86_EXT = "xserver-xorg-extension-dri \ --2.7.4
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
✗ patchtest: failure for "linux-intel: Add the linux-int..." and 1 more (rev2)
In reply to Saul Wold== Series Details ==
Series: "linux-intel: Add the linux-int..." and 1 more (rev2)
Revision: 2
URL : https://patchwork.openembedded.org/series/5172/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on the proposed series by patchtest resulting in the following failures:
* Issue Series does not apply on top of target branch [test_series_merge_on_head]
Suggested fix Rebase your series on top of targeted branch
Targeted branch master (currently at b3a74335e1)
If you believe any of these test results are incorrect, please reply to the mailing list ([email protected]) raising your concerns. Otherwise we would appreciate you correcting the issues and submitting a new version of the patchset if applicable. Please ensure you add/increment the version number when sending the new version (i.e. [PATCH] -> [PATCH v2] -> [PATCH v3] -> ...).
---
Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe
Re: [PATCH 2/2] meta-intel.inc: Enable linux-intel and 4.9 by default for meta-intel hardware
In reply to Khem RajQuoted 24 lines · Khem Raj
Quoted 22 lines · Saul Wold
Enable the linux-intel production kernel for meta-intel by default for 4.9,
this will enable using the Intel production kernel.This is a well tested 4.9 tree that will start to include additional
support for the Apollolake and Joule hardware.Signed-off-by Saul Wold <[email protected]>---
conf/machine/include/meta-intel.inc | 4 ++--1 file changed, 2 insertions(+), 2 deletions(-)conf/machine/include/meta-intel.inc +0
-0@@ -9,8 +9,8 @@ #
Quoted 7 lines
conf/machine/include/meta-intel.inc line 12
Quoted 4 lines
conf/machine/include/meta-intel.inc +1
-2# Soft set linux-yocto as preferred kernel like x86-base.inc -PREFERRED_PROVIDER_virtual/kernel ??= "linux-yocto" -PREFERRED_VERSION_linux-yocto ?= "4.8%" +PREFERRED_PROVIDER_virtual/kernel ?= "linux-intel"whats the difference between linux-yocto and linux-intel ?
Sorry for sending this to the wrong list.
This is a valid question, the difference will be faster integration and better testing /validation of upstream (or possibly pending upstream ) patches for Intel Hardware.
Since the kernel will be coming from an Intel Source, it will be fully tested on more hardware that the current linux-yocto kernel gets tested against.
The update rate maybe about the same, with security updates as needed for more severe issues
As other vendors maintain kernels for their meta-vendor specific layer, Intel has chosen to maintain an Intel kernel based on the current LTS version (4.9) plus upstreamed patches. All content will be backports from internally maintained tracking trees being regularly updated.
meta-intel will likely continue to contain the linux-yocto-<latest> for a non-LTS kernel.
Hope that clarifies this.
Sau!
Quoted 13 lines
Quoted 13 lines
conf/machine/include/meta-intel.inc +1
-1+PREFERRED_VERSION_linux-intel ?= "4.9%" # for Xserver older than 1.13.0 OLD_XSERVER_X86_EXT = "xserver-xorg-extension-dri \ --2.7.4
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [PATCH 2/2] meta-intel.inc: Enable linux-intel and 4.9 by default for meta-intel hardware
Quoted 50 lines · Saul Wold
Quoted 24 lines · Khem Raj
Quoted 22 lines · Saul Wold
Enable the linux-intel production kernel for meta-intel by default for 4.9,
this will enable using the Intel production kernel.This is a well tested 4.9 tree that will start to include additional
support for the Apollolake and Joule hardware.Signed-off-by Saul Wold <[email protected]>--- conf/machine/include/meta-intel.inc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)conf/machine/include/meta-intel.inc +0
-0@@ -9,8 +9,8 @@ #Quoted 7 lines
conf/machine/include/meta-intel.inc line 12
Quoted 4 lines
conf/machine/include/meta-intel.inc +1
-2# Soft set linux-yocto as preferred kernel like x86-base.inc -PREFERRED_PROVIDER_virtual/kernel ??= "linux-yocto" -PREFERRED_VERSION_linux-yocto ?= "4.8%" +PREFERRED_PROVIDER_virtual/kernel ?= "linux-intel"whats the difference between linux-yocto and linux-intel ?
Sorry for sending this to the wrong list.
This is a valid question, the difference will be faster integration and better testing /validation of upstream (or possibly pending upstream ) patches for Intel Hardware.
Since the kernel will be coming from an Intel Source, it will be fully tested on more hardware that the current linux-yocto kernel gets tested against.
The update rate maybe about the same, with security updates as needed for more severe issues
As other vendors maintain kernels for their meta-vendor specific layer, Intel has chosen to maintain an Intel kernel based on the current LTS version (4.9) plus upstreamed patches. All content will be backports from internally maintained tracking trees being regularly updated.
Quoted 4 lines
meta-intel will likely continue to contain the linux-yocto-<latest> for a non-LTS kernel.
Hope that clarifies this.
yes it does. So this is not a clone of linux-yocto but based directly on linux-stable.
Quoted 16 lines
Sau!
Quoted 13 lines
Quoted 13 lines
conf/machine/include/meta-intel.inc +1
-1+PREFERRED_VERSION_linux-intel ?= "4.9%" # for Xserver older than 1.13.0 OLD_XSERVER_X86_EXT = "xserver-xorg-extension-dri \ --2.7.4
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [PATCH 2/2] meta-intel.inc: Enable linux-intel and 4.9 by default for meta-intel hardware
Quoted 64 lines · Khem Raj
Quoted 62 lines · Saul Wold
Quoted 27 lines · Khem Raj
Quoted 24 lines · Saul Wold
Enable the linux-intel production kernel for meta-intel by default
for 4.9,
this will enable using the Intel production kernel.This is a well tested 4.9 tree that will start to include additional
support for the Apollolake and Joule hardware.Signed-off-by Saul Wold <[email protected]>---
conf/machine/include/meta-intel.inc | 4 ++--1 file changed, 2 insertions(+), 2 deletions(-)conf/machine/include/meta-intel.inc +0
-0@@ -9,8 +9,8 @@ #Quoted 7 lines
conf/machine/include/meta-intel.inc line 12
Quoted 4 lines
conf/machine/include/meta-intel.inc +1
-2# Soft set linux-yocto as preferred kernel like x86-base.inc -PREFERRED_PROVIDER_virtual/kernel ??= "linux-yocto" -PREFERRED_VERSION_linux-yocto ?= "4.8%" +PREFERRED_PROVIDER_virtual/kernel ?= "linux-intel"whats the difference between linux-yocto and linux-intel ?
Sorry for sending this to the wrong list.
This is a valid question, the difference will be faster integration and
better testing /validation of upstream (or possibly pending upstream )
patches for Intel Hardware.Since the kernel will be coming from an Intel Source, it will be fully
tested on more hardware that the current linux-yocto kernel gets tested
against.The update rate maybe about the same, with security updates as needed
for more severe issuesAs other vendors maintain kernels for their meta-vendor specific layer,
Intel has chosen to maintain an Intel kernel based on the current LTS
version (4.9) plus upstreamed patches. All content will be backports
from internally maintained tracking trees being regularly updated.
Quoted 9 lines
Quoted 5 lines
meta-intel will likely continue to contain the linux-yocto-<latest> for
a non-LTS kernel.Hope that clarifies this.
yes it does. So this is not a clone of linux-yocto but based directly on linux-stable.
Correct, this is based directly on linux-stable and will have patches that are backports from maintained tracking trees. As the new LTS is defined each year, linux-intel and meta-intel will update to that newer version. The older version will continue to be available and be updated with stable updates as they are available.
Sau!
Quoted 20 lines
Quoted 20 lines
Sau!
Quoted 16 lines
Quoted 16 lines
conf/machine/include/meta-intel.inc +1
-1+PREFERRED_VERSION_linux-intel ?= "4.9%" # for Xserver older than 1.13.0 OLD_XSERVER_X86_EXT = "xserver-xorg-extension-dri \ --2.7.4
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-cor
e