[OS-BUILD PATCH] alsa: fedora configs - enable SOF SoundWire driver
by GitLab Bridge on behalf of perexg
From: Jaroslav Kysela <perex(a)perex.cz>
---
redhat/configs/fedora/generic/CONFIG_SOUNDWIRE_QCOM | 1 +
redhat/configs/fedora/generic/arm/CONFIG_SOUNDWIRE_QCOM | 1 +
.../fedora/generic/x86/CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH | 1 +
redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_RT1308_SDW | 1 +
redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_RT700_SDW | 1 +
redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_RT711_SDW | 1 +
redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_RT715_SDW | 1 +
.../fedora/generic/x86/CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE_LINK | 1 +
8 files changed, 8 insertions(+)
create mode 100644 redhat/configs/fedora/generic/CONFIG_SOUNDWIRE_QCOM
create mode 100644 redhat/configs/fedora/generic/arm/CONFIG_SOUNDWIRE_QCOM
create mode 100644 redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH
create mode 100644 redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_RT1308_SDW
create mode 100644 redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_RT700_SDW
create mode 100644 redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_RT711_SDW
create mode 100644 redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_RT715_SDW
create mode 100644 redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE_LINK
diff --git a/redhat/configs/fedora/generic/CONFIG_SOUNDWIRE_QCOM b/redhat/configs/fedora/generic/CONFIG_SOUNDWIRE_QCOM
new file mode 100644
index 000000000000..c72e10062372
--- /dev/null
+++ b/redhat/configs/fedora/generic/CONFIG_SOUNDWIRE_QCOM
@@ -0,0 +1 @@
+# CONFIG_SOUNDWIRE_QCOM is not set
diff --git a/redhat/configs/fedora/generic/arm/CONFIG_SOUNDWIRE_QCOM b/redhat/configs/fedora/generic/arm/CONFIG_SOUNDWIRE_QCOM
new file mode 100644
index 000000000000..bfb00c97ea86
--- /dev/null
+++ b/redhat/configs/fedora/generic/arm/CONFIG_SOUNDWIRE_QCOM
@@ -0,0 +1 @@
+CONFIG_SOUNDWIRE_QCOM=m
diff --git a/redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH b/redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH
new file mode 100644
index 000000000000..ceb2762c732c
--- /dev/null
+++ b/redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH
@@ -0,0 +1 @@
+CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m
diff --git a/redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_RT1308_SDW b/redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_RT1308_SDW
new file mode 100644
index 000000000000..fcd241a22d7e
--- /dev/null
+++ b/redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_RT1308_SDW
@@ -0,0 +1 @@
+CONFIG_SND_SOC_RT1308_SDW=m
diff --git a/redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_RT700_SDW b/redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_RT700_SDW
new file mode 100644
index 000000000000..0b751eda035e
--- /dev/null
+++ b/redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_RT700_SDW
@@ -0,0 +1 @@
+CONFIG_SND_SOC_RT700_SDW=m
diff --git a/redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_RT711_SDW b/redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_RT711_SDW
new file mode 100644
index 000000000000..2785da6cd2a6
--- /dev/null
+++ b/redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_RT711_SDW
@@ -0,0 +1 @@
+CONFIG_SND_SOC_RT711_SDW=m
diff --git a/redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_RT715_SDW b/redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_RT715_SDW
new file mode 100644
index 000000000000..bbf65bdbd349
--- /dev/null
+++ b/redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_RT715_SDW
@@ -0,0 +1 @@
+CONFIG_SND_SOC_RT715_SDW=m
diff --git a/redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE_LINK b/redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE_LINK
new file mode 100644
index 000000000000..eeadd44c1b4d
--- /dev/null
+++ b/redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE_LINK
@@ -0,0 +1 @@
+CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE_LINK=y
--
GitLab
3 years, 4 months
[OS-BUILD PATCH] [redhat] New configs in net/xfrm
by GitLab Bridge on behalf of jeremycline
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_XFRM_USER_COMPAT:
Transformation(XFRM) user configuration interface like IPsec
used by compatible Linux applications.
If unsure, say N.
Symbol: XFRM_USER_COMPAT [=n]
Type : tristate
Defined at net/xfrm/Kconfig:31
Prompt: Compatible ABI support
Depends on: NET [=y] && INET [=y] && XFRM_USER [=y] && COMPAT_FOR_U64_ALIGNMENT [=y] && HAVE_EFFICIENT_UNALIGNED_ACCESS [=y]
Location:
-> Networking support (NET [=y])
-> Networking options
-> Transformation user configuration interface (XFRM_USER [=y])
Selects: WANT_COMPAT_NETLINK_MESSAGES [=n]
---
Cc: Jiri Benc <jbenc(a)redhat.com>
Cc: Marcelo Leitner <mleitner(a)redhat.com>
Cc: Davide Caratti <dcaratti(a)redhat.com>
Cc: Eric Garver <egarver(a)redhat.com>
Cc: Flavio Leitner <fbl(a)redhat.com>
Cc: Florian Westphal <fwestpha(a)redhat.com>
Cc: Guillaume Nault <gnault(a)redhat.com>
Cc: Hangbin Liu <haliu(a)redhat.com>
Cc: Ivan Vecera <ivecera(a)redhat.com>
Cc: Jarod Wilson <jarod(a)redhat.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi(a)redhat.com>
Cc: Paolo Abeni <pabeni(a)redhat.com>
Cc: Phil Sutter <psutter(a)redhat.com>
Cc: Sabrina Dubroca <sdubroca(a)redhat.com>
Cc: Stefano Brivio <sbrivio(a)redhat.com>
Cc: Xin Long <lxin(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_XFRM_USER_COMPAT | 1 +
.../generic/CONFIG_XFRM_USER_COMPAT | 21 -------------------
2 files changed, 1 insertion(+), 21 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_XFRM_USER_COMPAT
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_XFRM_USER_COMPAT
diff --git a/redhat/configs/common/generic/CONFIG_XFRM_USER_COMPAT b/redhat/configs/common/generic/CONFIG_XFRM_USER_COMPAT
new file mode 100644
index 000000000000..798d10e8e93e
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_XFRM_USER_COMPAT
@@ -0,0 +1 @@
+# CONFIG_XFRM_USER_COMPAT is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_XFRM_USER_COMPAT b/redhat/configs/pending-common/generic/CONFIG_XFRM_USER_COMPAT
deleted file mode 100644
index 7941fd360e9b..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_XFRM_USER_COMPAT
+++ /dev/null
@@ -1,21 +0,0 @@
-# CONFIG_XFRM_USER_COMPAT:
-#
-# Transformation(XFRM) user configuration interface like IPsec
-# used by compatible Linux applications.
-#
-# If unsure, say N.
-#
-# Symbol: XFRM_USER_COMPAT [=n]
-# Type : tristate
-# Defined at net/xfrm/Kconfig:31
-# Prompt: Compatible ABI support
-# Depends on: NET [=y] && INET [=y] && XFRM_USER [=y] && COMPAT_FOR_U64_ALIGNMENT [=y] && HAVE_EFFICIENT_UNALIGNED_ACCESS [=y]
-# Location:
-# -> Networking support (NET [=y])
-# -> Networking options
-# -> Transformation user configuration interface (XFRM_USER [=y])
-# Selects: WANT_COMPAT_NETLINK_MESSAGES [=n]
-#
-#
-#
-# CONFIG_XFRM_USER_COMPAT is not set
--
GitLab
3 years, 4 months
[OS-BUILD PATCH] [redhat] New configs in net/ipv6
by GitLab Bridge on behalf of jmflinuxtx
From: "Justin M. Forbes" <jforbes(a)fedoraproject.org>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_INET6_ESPINTCP:
Support for RFC 8229 encapsulation of ESP and IKE over
TCP/IPv6 sockets.
If unsure, say N.
Symbol: INET6_ESPINTCP [=n]
Type : bool
Defined at net/ipv6/Kconfig:91
Prompt: IPv6: ESP in TCP encapsulation (RFC 8229)
Depends on: NET [=y] && INET [=y] && IPV6 [=y] && XFRM [=y] && INET6_ESP [=m]
Location:
-> Networking support (NET [=y])
-> Networking options
-> TCP/IP networking (INET [=y])
-> The IPv6 protocol (IPV6 [=y])
-> IPv6: ESP transformation (INET6_ESP [=m])
Selects: STREAM_PARSER [=y] && NET_SOCK_MSG [=y] && XFRM_ESPINTCP [=y]
---
Signed-off-by: Justin M. Forbes <jforbes(a)fedoraproject.org>
---
.../common/generic/CONFIG_INET6_ESPINTCP | 1 +
.../generic/CONFIG_INET6_ESPINTCP | 23 -------------------
2 files changed, 1 insertion(+), 23 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_INET6_ESPINTCP
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_INET6_ESPINTCP
diff --git a/redhat/configs/common/generic/CONFIG_INET6_ESPINTCP b/redhat/configs/common/generic/CONFIG_INET6_ESPINTCP
new file mode 100644
index 000000000000..1b4ebe140e27
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_INET6_ESPINTCP
@@ -0,0 +1 @@
+# CONFIG_INET6_ESPINTCP is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_INET6_ESPINTCP b/redhat/configs/pending-common/generic/CONFIG_INET6_ESPINTCP
deleted file mode 100644
index b25df3812966..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_INET6_ESPINTCP
+++ /dev/null
@@ -1,23 +0,0 @@
-# CONFIG_INET6_ESPINTCP:
-#
-# Support for RFC 8229 encapsulation of ESP and IKE over
-# TCP/IPv6 sockets.
-#
-# If unsure, say N.
-#
-# Symbol: INET6_ESPINTCP [=n]
-# Type : bool
-# Defined at net/ipv6/Kconfig:91
-# Prompt: IPv6: ESP in TCP encapsulation (RFC 8229)
-# Depends on: NET [=y] && INET [=y] && IPV6 [=y] && XFRM [=y] && INET6_ESP [=m]
-# Location:
-# -> Networking support (NET [=y])
-# -> Networking options
-# -> TCP/IP networking (INET [=y])
-# -> The IPv6 protocol (IPV6 [=y])
-# -> IPv6: ESP transformation (INET6_ESP [=m])
-# Selects: STREAM_PARSER [=y] && NET_SOCK_MSG [=y] && XFRM_ESPINTCP [=y]
-#
-#
-#
-# CONFIG_INET6_ESPINTCP is not set
--
2.26.2
3 years, 5 months
Fwd: heads up regarding some v5.10 changes
by Peter Robinson
FYI:
---------- Forwarded message ---------
From: Ard Biesheuvel <ardb(a)kernel.org>
Date: Sat, Oct 31, 2020 at 10:22 AM
Subject: heads up regarding some v5.10 changes
To: <cross-distro(a)lists.linaro.org>, Arnd Bergmann <arnd(a)arndb.de>,
Peter Jones <pjones(a)redhat.com>
Hello all,
Just a note to whomever is subscribed to this list regarding some
changes in v5.10 that may affect distros' kernel deployments:
efivars
-------
efivars is the ancient predecessor to efivarFs, that allows access to
EFI variables via sysfs (but with some restrictions). This has been
deprecated since before ARM even had UEFI support, and it is no longer
going to be enabled going forward. EFI pstore has been rewritten to no
longer rely on it, and on x86, the module is still available, but no
longer gets loaded automatically. On !x86, it is no longer built at
all. As far as I could figure out (and I did ask around as well), this
is highly unlikely to regress anything, and on x86, the module can
still be loaded manually if needed (or enabled as a builtin)
deprecated crypto
-----------------
Some crypto drivers have been made to depend on
CONFIG_CRYPTO_USER_API_ENABLE_OBSOLETE, which is only available if the
crypto AF_ALG socket API is enabled, as the algorithms are never used
by the kernel itself. However, none of these ciphers are known to be
relied upon by user space either (via AF_ALG), and so I strongly
recommend the distros incorporate
# CONFIG_CRYPTO_USER_API_ENABLE_OBSOLETE is not set
into their v5.10+ kernel configs so that these deprecated algorithms
are simply dropped from the build (the algos are arc4, tea, khazad,
SEED and anubis, others may follow in the future, e.g., md4/5). Note
that iwd/libell used to rely on the kernel's ecb(arc4) implementation,
but this is no longer the case.
kexec/kdump tools
-----------
To make the kernel's PE/COFF header spec compliant, the stext symbol
will be aligned to 64 KB regardless of the page size the kernel was
built with. As far as I can tell looking at the debian source of the
associated tooling, the symbol value of stext is used to infer the
page size, so this will no longer work.
_______________________________________________
cross-distro mailing list
cross-distro(a)lists.linaro.org
https://lists.linaro.org/mailman/listinfo/cross-distro
3 years, 5 months
[OS-BUILD PATCH] Allow kernel-tools to build without selftests
by GitLab Bridge on behalf of dzickusrh
From: Don Zickus <dzickus(a)redhat.com>
While debugging LTO issues, I disabled kernel-selftests
temporarily. This exposed an issue in turbostat that
required libcap to compile. Add the BuildRequires to
the spec file.
I don't expect this scenario to happen at all. This
fix is for completeness and less headaches in the future.
Signed-off-by: Don Zickus <dzickus(a)redhat.com>
---
redhat/kernel.spec.template | 1 +
1 file changed, 1 insertion(+)
diff --git a/redhat/kernel.spec.template b/redhat/kernel.spec.template
index 7cbfb9c139eb..2d15d843e86b 100644
--- a/redhat/kernel.spec.template
+++ b/redhat/kernel.spec.template
@@ -499,6 +499,7 @@ BuildRequires: numactl-devel
%endif
%if %{with_tools}
BuildRequires: gettext ncurses-devel
+BuildRequires: libcap-devel libcap-ng-devel
%ifnarch s390x
BuildRequires: pciutils-devel
%endif
--
GitLab
3 years, 5 months
[OS-BUILD PATCH] Fix LTO issues with kernel-tools
by GitLab Bridge on behalf of dzickusrh
From: Don Zickus <dzickus(a)redhat.com>
There are two parts to this fix. One is using the recommended way
to disable LTO. The other is to make it work for the kernel.spec
file.
Various kernel-tool programs (like perf) can not handle LTO yet, so
they are disabled.
This is done with '%define _lto_cflags {nil}'.
However that doesn't quite work for the kernel for the %install
section. It works for the %build section.
Oddly, back at the birth of dist-git, the initial kernel.spec
file was imported with a line at the top
%global __spec_install_pre %{___build_pre}
For whatever reason, the kernel was deemed special and that line
pre-built the %install scripts _before_ the lto_cflags could
dynamically be disabled.
Moving the _lto_cflags line above the _pre line disables LTO
for both the %build and %install sections of the spec file.
However, because that _pre line is unintiutive and caused hours
of debugging headache, I hacked up the output to see what the
%__spec_install_pre and ___build_pre looked like at the
beginning of the %install section. The idea was __build_pre
is what we want going forward.
Of the 20 or so env vars defined, the only differences besides
the LTO flags was -fcommon. This made sense because
_legacy_common_support is also set (enabled -fcommon) after
the _pre line. Therefore the %install section was correctly
using -fno-common.
In other words having
%global __spec_install_pre %{___build_pre}
is now useless after 10 years. Let's just get rid of
that and save future headaches and issues and use the
recommended way of disabling LTO.
Cc: Jeff Law <law(a)redhat.com>
Signed-off-by: Don Zickus <dzickus(a)redhat.com>
---
redhat/kernel.spec.template | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/redhat/kernel.spec.template b/redhat/kernel.spec.template
index 7cbfb9c139eb..439c22be33c9 100644
--- a/redhat/kernel.spec.template
+++ b/redhat/kernel.spec.template
@@ -1,5 +1,4 @@
-# We have to override the new %%install behavior because, well... the kernel is special.
-%global __spec_install_pre %{___build_pre}
+%global _lto_cflags %{nil}
# Short-term fix so the package builds with GCC 10.
# This should go away soon.
--
GitLab
3 years, 5 months
