Configuration
- mt8195_demo: fix the HDMI device name
- USB-Audio: ALC1220 - add support for Gigabyte TRX40 Aorus Pro WiFi Rev 1.2
- ucm2: MediaTek: mt8195-demo: Add Initial support
- ucm2: rk3399-gru-sound: Add missing symlink from conf.d tree
- USB-Audio: Optimize regex for realtek-alc4080
- USB-Audio: Add ALC4080 ID for Asus Z690-I Gaming Wifi
- ucm2 profile for MOTU M4 interface
- ucm2: Rockchip/max98090: add symlink to VEYRON-I2S
- ucm2: Rockchip/max98090: add JackControl and PlaybackVolume
- Added basic support for ALC4082 on ASUS ROG Maximus Z690 Hero.
- ucm2: direct profile - allow to override the card name
- ucm2 profile for Behringer Flow8
- Steinberg UR44: fix the direction for steinberg_ur44_mono_in
- Steinberg UR44: fix the Line2 channel mapping (2nd)
- Steinberg UR44: fix the Line2 channel mapping
(From OE-Core rev: 66e9a57aeeab9f87106d5565ac28342d38a6eb33)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changelog:
=========
Core
- Release v1.2.7.1
- conf: Use ino64_t to save and compare inode numbers
Control API
- control: eld - fix the decoding for older hw
I/O API
- output: include stdarg.h
PCM API
- pcm: dmix - Add error handler for `fgets`
Use Case Manager API
- ucm: list also hardware configs (hw:X) in uc_mgr_scan_master_configs() fcn
Configuration
- conf: Use ino64_t to save and compare inode numbers
(From OE-Core rev: fd6bf61bd5401a099372661f77f3abd9d0242d67)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Drop backports; one of them (0009) is present only
on the master branch and not on 2.13 branch, and so
stays in the recipe.
(From OE-Core rev: 1002941b76e0a0351e85a20e3e8d0a6a2254449c)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Commit e1382583cd50 ("perf: sort-pmuevents: don't drop elements") tried
to fix a case where the array terminator elements were dropped from the
sorted list breaking the build, but it only worked for the case where
the terminator is the only element of the array. When the array has other
elements the terminator will still be silently dropped, causing invalid
memory accesses at runtime when the perf utility iterates over the array.
Fix this by treating any unmatched entry as an array terminator and also
add a comment to make it a little more clear how things are ending up at
the right position in the sorted list.
(From OE-Core rev: 69c35a48c5100b884f1b633142b07222b9390e92)
Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Without `--with-gcc-arch=generic` libffi looks up the cpuid to automatically determine
which mtune/march to use. This makes the native sstate-cache unuseable since it's
possible to have a newer cpu building the recipe and the library being pulled from
another older cpu which doesn't have the instruction.
(From OE-Core rev: cddaecac1fdd4d033c2ff8ccaf1d60e1c598d5b7)
Signed-off-by: Maxime Roussin-Bélanger <maxime.roussinbelanger@gmail.com>
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This recipe (a VCS plugin for Hatch) is needed by the new
python3-jsonschema to build.
(From OE-Core rev: 62cb0c78e2ea4cfbb7bb961abd9b8faaa2100379)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Recipes in core are now needing to use the Hatch build system, so
move the hatchling recipe and class from meta-oe to oe-core.
(From OE-Core rev: 846e806181f1349be29cbce78c5041735dfd7e6f)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is a dependency of the Hatch build system, to be added as
python3-hatchling.
(From OE-Core rev: 857f324314d10c6cfe4613ec5dc865a2df0dc2e2)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is a dependency of the Hatch build system, to be added as
python3-hatchling.
(From OE-Core rev: 781da7200711e45da8b63654dd4508fce62580b8)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Failure message is shown in boot logs when trying to
mount lvm as automounter does not handle cases where
lvm is mounted. This simply skips lvm while automounting
to avoid failure message in boot logs.
(From OE-Core rev: b1d18072ed9a8b0bca0f20f8e5deefa73ab6acbe)
Signed-off-by: Ansar Rasool <ansar_rasool@mentor.com>
Signed-off-by: Muhammad Hamza <muhammad_hamza@mentor.com>
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Automounting does not work cleanly in case systemd as well as
udev rules are being used simultaneously and in most cases
race conditions and unknown behavior can come up.
In case we're running on top of systemd we need to make sure
that systemd-udevd knows that udev is in play as well and
mounting should be done using shared flags. Also as we're
using mount from sources other than systemd-mount in current
scripts this is the most manageable fix to automounting
problems.
(From OE-Core rev: 1e770416b4c9a0468404fb64d55114d93e84763b)
Signed-off-by: Awais Belal <awais_belal@mentor.com>
Signed-off-by: Muhammad Hamza <muhammad_hamza@mentor.com>
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
fdisk from util-linux (2.31.1) and above allows the user to
manipulate an already mounted device. In order to achieve this
functionality it issues a BLKRRPART (block device re-read part)
ioctl and in response the kernel generates remove/change/add
events if the device is not mounted (manually unmounted etc)
which are caught and processed by udev. This causes our auto-mounter
to remount everything because it does not keep track and things
go out of control.
Differentiating between types of remove events such as the one
described above (generated by BLKRRPART) and one where the device
is physically plugged out is only possible using the DEVPATH variable
which is cleaned up only when the device is actually plugged-out.
This fixes the above anomaly by only mounting a device in add event
which is cleaned up properly (tmp cache deleted) in the remove event
or is not present in the tmp cache while making use of the DEVPATH
variable during the remove action.
(From OE-Core rev: 11a5e6c17535438ea1e7a8403ed260c8b3a22bc8)
Signed-off-by: Awais Belal <awais_belal@mentor.com>
Signed-off-by: Muhammad Hamza <muhammad_hamza@mentor.com>
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Doing this will allow to fetch the exact name created by the
auto-mounter during the remove action where depending on the
scenario utilities such as the blkid might not be usable due
to actual device not being present on the system.
(From OE-Core rev: 496b76f8775a620c1d449eb6f62a41656abf2a9b)
Signed-off-by: Awais Belal <awais_belal@mentor.com>
Signed-off-by: Muhammad Hamza <muhammad_hamza@mentor.com>
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This alters the mountpoints such that if a device has a LABEL or
a PARTLABEL, it will be mounted at e.g.:
/run/media/$LABEL-<device-node>
/run/media/$PARTLABEL-<device-node>
/run/media/rootfs-sda2
otherwise the device will be mounted at e.g.:
/run/media/<device-node>
/run/media/sda1
The <device-node> appended with LABEL or PARTLABEL makes sure that
the mountpoint is unique, therefore, avoids overlapping mounts.
(From OE-Core rev: a9a0a0967832445f1bcc65d58f95343d1b562e1b)
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
Signed-off-by: Muhammad Hamza <muhammad_hamza@mentor.com>
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Drop patches which are not needed anymore.
Rebase musl specific patches to aboid fuzz warnings
(From OE-Core rev: 3275cc6c2ecfd70ba134b49363c9cecbb0c2c0b2)
Signed-off-by: Pavel Zhukov <pavel.zhukov@huawei.com>
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Specific provider (ie. RPM or IPK) does "provide" just itself as a
package to the system. This will cause the "-dev" package, which
refers to the generic signing-keys and not the provider specific,
to miss the dependency.
Error case (RPM) when populating sdk:
Error:
Problem: conflicting requests
- nothing provides signing-keys = 1.0-r0 needed by signing-keys-dev-1.0-r0.noarch
(try to add '--skip-broken' to skip uninstallable packages)
Examining signing-keys-rpm packages in PROVIDES we have indeed:
signing-keys-rpm = 1.0-r0
But in signing-keys-dev: in REQUIRES:
signing-keys-1.0-r0
This MR will fix the situation by removing the RDEPENDS for
the -dev package
(From OE-Core rev: ecdba906c3c8bc21e33b4a2651a762c40487149b)
Signed-off-by: Federico Pellegrin <fede@evolware.org>
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This test uses find_unused_port() which is inherently racey, so retry
it a few times before failing.
[ YOCTO #14840 ]
(From OE-Core rev: efac044cabdbe77556a0b9903595fd602f39ac8d)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Currently the sysext binary is packaged in systemd-utils and
the service systemd-sysext.service in systemd package. Add a
PACKAGECONFIG for sysext to actively choose if it is going to
be installed or not, default off. If installed it will be added
to systemd package.
(From OE-Core rev: 98cc5639d74dc71aa1352b50f97ed832245d3c3b)
Signed-off-by: Peter Bergin <peter@berginkonsult.se>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Operations such as mkfs fail on devices that are not
switched to the actual rootfs before switch_root is
called. The kernel interprets these devices as still
being used even after unmounting and errors such as
below are seen when the target is fully booted
root@v1000:~# umount /dev/sdb1
root@v1000:~# mkfs.ext4 /dev/sdb1
mke2fs 1.43.8 (1-Jan-2018)
/dev/sdb1 contains a ext4 file system
last mounted on Wed Nov 28 07:33:54 2018
Proceed anyway? (y,N) y
/dev/sdb1 is apparently in use by the system; will not make a filesystem here!
(From OE-Core rev: ec53ffd01972d1be2d6a28de828b3f0b80dc1e61)
Signed-off-by: Awais Belal <awais_belal@mentor.com>
Signed-off-by: Muhammad Hamza <muhammad_hamza@mentor.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
0001-fsck-main.c-add-missing-include.patch
removed since it's included in 1.5.
License-Update: license switch to GPL-2.0+ OR Apache-2.0
for better 3rd-party integration.
Changelog:
==========
* This release includes the following updates:
- (fsck.erofs) support filesystem extraction (Igor Ostapenko);
- support ztailpacking inline feature for compressed files (Yue Hu);
- (dump.erofs) support listing directories;
- more liberofs APIs (including iterate APIs) (me, Kelvin Zhang);
- use mtime to allow more control over the timestamps (David Anderson);
- switch to GPL-2.0+ OR Apache-2.0 dual license for liberofs;
- various bugfixes and cleanups;
(From OE-Core rev: bb87788832ad64079609e4f554e4d55a14f0aa94)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Eliminated the ptest deprecation warnings for the error:
DeprecationWarning: _int_ returned non-int (type SizedInteger).
The ability to return an instance of a strict subclass of int is deprecated,
and may be removed in a future version of Python.
return SizedInteger(value).setBitLength(len(value))
Patch from git upstream repo:
db8f1a7930
(From OE-Core rev: ac674d95820137306e7c71f4275d92cf4fedf39d)
Signed-off-by: Yulong (Kevin) Liu <yulong.liu@windriver.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add ability to parse instance-specific conf files when
enabling an instance of a templated unit during postinstall.
(From OE-Core rev: baa0ecf3271008cf60cd830c54a71f191aebb81c)
Signed-off-by: Nick Potenski <nick.potenski@garmin.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Ignored CVEs aren't patched, but do not apply in our configuration
for some reason. Up till now they were only partially supported
and reported as "Patched".
This patch adds separate reporting of Ignored CVEs. The variable
CVE_CHECK_REPORT_PATCHED now manages reporting of both patched
and ignored CVEs.
(From OE-Core rev: c773102d4828fc4ddd1024f6115d577e23f1afe4)
Signed-off-by: Marta Rybczynska <marta.rybczynska@huawei.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changelog:
=========
Use obstack.c and obstack.h from gcc-10.2.0 libiberty.
Add AC_CONFIG_HEADERS to configure.ac and make ./bootstrap.sh create config.h.in.
(From OE-Core rev: a34986755a57b6467e78eb91042bb46f588b6856)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
