| Message ID | 20250326202817.64437-1-hiagofranco@gmail.com |
|---|---|
| Headers | show |
| Series | linux-firmware: upgrade 20240909 -> 20250311 | expand |
On Wed, Mar 26, 2025 at 1:29 PM Hiago De Franco <hiagofranco@gmail.com> wrote: > > From: Hiago De Franco <hiago.franco@toradex.com> > > Update the linux-firmware recipe to the most recent upstream tag. > > This is basically a backport of the commits from master into styhead, > related to the linux-firmware recipe. Sorry I missed seeing this yesterday. The final release of styhead is now in QA, there are no further releases planned. If this changes for any reason I will consider this series. The project weekly status report publishes the complete schedule of releases for all branches. Steve > > Commit 30ea609d3357 ("meta/meta-selftest: Fix variable assignment > whitespace") changes a lot of files (linux-firmware included), but they > are all related to missing whitespaces to improve redability, this is > the reason I have decided to cherry-pick this commit as well. > > v2: > - As requested, I converted the v1 patch into backports from oe-core master. > v1: > - https://lore.kernel.org/openembedded-core/20250325215115.10430-1-hiagofranco@gmail.com/ > > Alex Kiernan (1): > linux-firmware: Add RTL8723DS blobs into ${PN}-rtl8723 > > Dmitry Baryshkov (16): > linux-firmware: add battmgr.jsn to ${PN}-qcom-qcm6490-audio > linux-firmware: split qcm6490 ZAP shader to separate package > linux-firmware: split sa8775p ZAP shader to separate package > linux-firmware: make ${PN}-qcom-adreno-a663 depend on -a660 > linux-firmware: package IPA firmware for Qualcomm QCM6490 platforms > linux-firmware: RPROVIDE qcs6490 firmware packages by qcm6490 ones > linux-firmware: upgrade 20241017 -> 20241110 > linux-firmware: package Qualcomm X1 Elite audio DSP firmware > linux-firmware: package QCS615 Adreno ZAP shader > linux-firmware: upgrade 20241110 -> 20241210 > linux-firmware: package firmware for Qualcomm AIC100 and QDU100 > linux-firmware: upgrade 20241210 -> 20250109 > linux-firmware: split the qca6390 firmware > linux-firmware: further split qca61x4 package > linux-firmware: fix qca-qca61x4-usb package contents > linux-firmware: make linux-firmware-qcom-qcm6490-wifi provide > -qcs6490- > > Marc Ferland (5): > linux-firmware: split ath10k firmwares in separate packages > linux-firmware: split ath11k firmwares in separate packages > linux-firmware: split amdgpu firmwares in separate packages > linux-firmware: split ath12k firmwares in separate packages > linux-firmware: split qca firmwares in separate packages > > Richard Purdie (1): > meta/meta-selftest: Fix variable assignment whitespace > > Vivek Puar (6): > linux-firmware: add new fw file to ${PN}-qcom-adreno-a660 > linux-firmware: Add qcom-qcm6490-{audio,compute} firmware packages > linux-firmware: Add qcom-adreno-a663 package > linux-firmware: upgrade 20250109 -> 20250211 > linux-firmware: upgrade 20250211 -> 20250311 > linux-firmware: update qca-qca61x4-usb package contents > > Zoltan Boszormenyi (1): > linux-firmware: Fix packaging of some subpackages > > Zoltán Böszörményi (1): > linux-firmware: Upgrade to 20241017 and allow compressing firmware > > .../sysdig/sysdig-selftest_0.28.0.bb | 2 +- > .../bbclasses/systemd-and-sysvinit.bb | 2 +- > .../recipes-test/bbclasses/systemd-only.bb | 2 +- > .../recipes-test/gitrepotest/gitrepotest.bb | 2 +- > .../selftest-users/acreategroup.bb | 2 +- > .../selftest-users/bcreategroup.bb | 2 +- > .../selftest-users/ccreategroup.bb | 2 +- > .../selftest-users/dcreategroup.bb | 2 +- > meta/classes-global/base.bbclass | 2 +- > meta/classes-recipe/autotools.bbclass | 2 +- > meta/classes-recipe/cargo.bbclass | 2 +- > meta/classes-recipe/go.bbclass | 4 +- > meta/classes-recipe/gtk-icon-cache.bbclass | 2 +- > meta/classes-recipe/kernel.bbclass | 2 +- > meta/classes-recipe/python3native.bbclass | 6 +- > meta/classes-recipe/python_pyo3.bbclass | 12 +- > meta/classes-recipe/rust.bbclass | 8 +- > meta/classes-recipe/setuptools3.bbclass | 2 +- > .../classes-recipe/setuptools3_legacy.bbclass | 2 +- > meta/conf/documentation.conf | 2 +- > meta/recipes-bsp/u-boot/u-boot-tools.inc | 2 +- > meta/recipes-connectivity/connman/connman.inc | 4 +- > .../inetutils/inetutils_2.5.bb | 2 +- > meta/recipes-core/coreutils/coreutils_9.5.bb | 2 +- > meta/recipes-core/glibc/glibc-package.inc | 2 +- > .../glibc/glibc-y2038-tests_2.40.bb | 2 +- > meta/recipes-core/meta/meta-environment.bb | 2 +- > meta/recipes-core/musl/musl_git.bb | 2 +- > meta/recipes-core/newlib/newlib.inc | 2 +- > meta/recipes-core/os-release/os-release.bb | 2 +- > meta/recipes-core/ovmf/ovmf-shell-image.bb | 2 +- > meta/recipes-core/ovmf/ovmf_git.bb | 6 +- > .../packagegroup-rust-cross-canadian.bb | 2 +- > meta/recipes-core/picolibc/picolibc.inc | 2 +- > .../binutils/binutils-2.43.1.inc | 2 +- > meta/recipes-devtools/cmake/cmake_3.30.2.bb | 2 +- > .../nativesdk-icecc-toolchain_0.1.bb | 2 +- > .../libtool/libtool-2.5.2.inc | 2 +- > .../perl/libxml-parser-perl_2.47.bb | 2 +- > .../python/python3-attrs_24.2.0.bb | 2 +- > .../python/python3-pygobject_3.48.2.bb | 2 +- > .../recipes-devtools/python/python3_3.12.9.bb | 2 +- > meta/recipes-devtools/rust/rust_1.79.0.bb | 2 +- > .../asciidoc/asciidoc_10.2.1.bb | 2 +- > .../baremetal-helloworld_git.bb | 2 +- > .../go-examples/go-helloworld_0.1.bb | 2 +- > meta/recipes-extended/gzip/gzip.inc | 4 +- > .../logrotate/logrotate_3.22.0.bb | 2 +- > .../perl/libxml-namespacesupport-perl_1.12.bb | 2 +- > meta/recipes-extended/shadow/shadow.inc | 2 +- > meta/recipes-extended/timezone/timezone.inc | 2 +- > .../libadwaita/libadwaita_1.5.3.bb | 2 +- > meta/recipes-graphics/mesa/mesa.inc | 26 +- > .../xorg-lib/xcb-util-errors_1.0.1.bb | 2 +- > .../xorg-proto/xorgproto_2024.1.bb | 2 +- > .../cryptodev/cryptodev-module_1.14.bb | 2 +- > .../cryptodev/cryptodev-tests_1.14.bb | 2 +- > ...20240909.bb => linux-firmware_20250311.bb} | 869 +++++++++++++----- > meta/recipes-kernel/linux/kernel-devsrc.bb | 2 +- > meta/recipes-kernel/linux/linux-yocto-dev.bb | 6 +- > .../linux/linux-yocto-rt_6.10.bb | 6 +- > .../linux/linux-yocto-rt_6.6.bb | 6 +- > meta/recipes-kernel/linux/linux-yocto.inc | 4 +- > meta/recipes-kernel/linux/linux-yocto_6.10.bb | 12 +- > meta/recipes-kernel/linux/linux-yocto_6.6.bb | 12 +- > .../lttng/lttng-modules_2.13.14.bb | 2 +- > .../make-mod-scripts/make-mod-scripts_1.0.bb | 2 +- > meta/recipes-kernel/perf/perf.bb | 2 +- > .../gstreamer/gstreamer1.0-meta-base.bb | 4 +- > meta/recipes-sato/l3afpad/l3afpad_git.bb | 2 +- > meta/recipes-support/apr/apr_1.7.5.bb | 2 +- > meta/recipes-support/gnutls/gnutls_3.8.6.bb | 2 +- > meta/recipes-support/gpgme/gpgme_1.23.2.bb | 2 +- > meta/recipes-support/vte/vte_0.76.3.bb | 4 +- > 74 files changed, 783 insertions(+), 324 deletions(-) > rename meta/recipes-kernel/linux-firmware/{linux-firmware_20240909.bb => linux-firmware_20250311.bb} (66%) > > -- > 2.39.5 >
Hi Steve, On Thu, Mar 27, 2025 at 07:54:53AM -0700, Steve Sakoman wrote: > On Wed, Mar 26, 2025 at 1:29 PM Hiago De Franco <hiagofranco@gmail.com> wrote: > > > > From: Hiago De Franco <hiago.franco@toradex.com> > > > > Update the linux-firmware recipe to the most recent upstream tag. > > > > This is basically a backport of the commits from master into styhead, > > related to the linux-firmware recipe. > > Sorry I missed seeing this yesterday. > > The final release of styhead is now in QA, there are no further > releases planned. > > If this changes for any reason I will consider this series. > > The project weekly status report publishes the complete schedule of > releases for all branches. All right, thanks for letting me know. I did not realise that. I think the real work is on scarthgap and kirkstone, which I will send another series. Can you comment if this is the right approach for kirkstone and scarhgap as well? From what I understood, I need to backport these patches for the other LTS branches as well, without breaking the compatibility. Is this correct? > > Steve > Cheers, Hiago.
Hi Hiago, On 3/27/25 5:19 PM, Hiago De Franco wrote: > Hi Steve, > > On Thu, Mar 27, 2025 at 07:54:53AM -0700, Steve Sakoman wrote: >> On Wed, Mar 26, 2025 at 1:29 PM Hiago De Franco <hiagofranco@gmail.com> wrote: >>> >>> From: Hiago De Franco <hiago.franco@toradex.com> >>> >>> Update the linux-firmware recipe to the most recent upstream tag. >>> >>> This is basically a backport of the commits from master into styhead, >>> related to the linux-firmware recipe. >> >> Sorry I missed seeing this yesterday. >> >> The final release of styhead is now in QA, there are no further >> releases planned. >> >> If this changes for any reason I will consider this series. >> >> The project weekly status report publishes the complete schedule of >> releases for all branches. > > All right, thanks for letting me know. I did not realise that. > > I think the real work is on scarthgap and kirkstone, which I will send > another series. Can you comment if this is the right approach for > kirkstone and scarhgap as well? > > From what I understood, I need to backport these patches for the other > LTS branches as well, without breaking the compatibility. Is this > correct? > Will let Steve confirm but seems right to me. As for the compatibility part, for firmware files being split into a new package, I would suggest to have the "old" package the firmware used to be in have an RDEPENDS on the new package so that anything that was requesting the old package still gets the firmware, except from the new package, but it gets brought in the image via the RDEPENDS mechanism. That could be the case for a bunch of files moved out of the catch-all -misc packages for example. For when firmware files are moved from one package to another that already has other files that's a different topic. I would assume we simply do not backport that part of the change and keep the firmware in its original package. Cheers, Quentin
On Thu, Mar 27, 2025 at 9:19 AM Hiago De Franco <hiagofranco@gmail.com> wrote: > > Hi Steve, > > On Thu, Mar 27, 2025 at 07:54:53AM -0700, Steve Sakoman wrote: > > On Wed, Mar 26, 2025 at 1:29 PM Hiago De Franco <hiagofranco@gmail.com> wrote: > > > > > > From: Hiago De Franco <hiago.franco@toradex.com> > > > > > > Update the linux-firmware recipe to the most recent upstream tag. > > > > > > This is basically a backport of the commits from master into styhead, > > > related to the linux-firmware recipe. > > > > Sorry I missed seeing this yesterday. > > > > The final release of styhead is now in QA, there are no further > > releases planned. > > > > If this changes for any reason I will consider this series. > > > > The project weekly status report publishes the complete schedule of > > releases for all branches. > > All right, thanks for letting me know. I did not realise that. > > I think the real work is on scarthgap and kirkstone, which I will send > another series. Can you comment if this is the right approach for > kirkstone and scarhgap as well? > > From what I understood, I need to backport these patches for the other > LTS branches as well, without breaking the compatibility. Is this > correct? In theory, yes. However after seeing the extent of changes required to bring styhead up to date (31 patches!) I fear that the changes for older releases will be way more extensive than I feel comfortable with. I don't see how we can assert that compatibility will be maintained with that level of change. Especially since our automated testing of the linux-firmware package is pretty minimal :-( So I'm not inclined to take such a patchset, since I think the risk outweighs the benefit. Steve
On Thu, 27 Mar 2025 at 18:12, Hiago De Franco via lists.openembedded.org <hiagofranco=gmail.com@lists.openembedded.org> wrote: > What do you reccomend? Should I try to keep the patch with minimal > differences as possible? You might consider adding this to meta-lts-mixins? Alex
On Thu, Mar 27, 2025 at 06:29:18PM +0100, Alexander Kanavin wrote: > On Thu, 27 Mar 2025 at 18:12, Hiago De Franco via > lists.openembedded.org <hiagofranco=gmail.com@lists.openembedded.org> > wrote: > > > What do you reccomend? Should I try to keep the patch with minimal > > differences as possible? > > You might consider adding this to meta-lts-mixins? This would be another option, but before going into this direction, I am still wondering if the bump on Scarthgap is valid. From the git history I can see this recipe was already bumped in the past, until it got to 20240909, inside Scarthgap. From the bugfixing point of view, it would be good to incorporate these changes into Scarthgap directly. I am not sure how is the policy/procedure to bump a LTS branch, maybe you guys can help me understand this a little bit. Then I will be happy to propose a patch and try to work this out ;-) > > Alex Thanks again, Hiago.
Hi Hiago, On 3/27/25 8:01 PM, Hiago De Franco wrote: > On Thu, Mar 27, 2025 at 06:29:18PM +0100, Alexander Kanavin wrote: >> On Thu, 27 Mar 2025 at 18:12, Hiago De Franco via >> lists.openembedded.org <hiagofranco=gmail.com@lists.openembedded.org> >> wrote: >> >>> What do you reccomend? Should I try to keep the patch with minimal >>> differences as possible? >> >> You might consider adding this to meta-lts-mixins? > > This would be another option, but before going into this direction, I > am still wondering if the bump on Scarthgap is valid. > > From the git history I can see this recipe was already bumped in the > past, until it got to 20240909, inside Scarthgap. From the bugfixing > point of view, it would be good to incorporate these changes into > Scarthgap directly. I am not sure how is the policy/procedure to bump a > LTS branch, maybe you guys can help me understand this a little bit. > Then I will be happy to propose a patch and try to work this out ;-) > https://wiki.yoctoproject.org/wiki/Stable_Release_and_LTS#Stable/LTS_Patch_Acceptance_Policies In any case, it needs to go through TSC (https://wiki.yoctoproject.org/wiki/TSC) before being accepted I believe. To reach TSC, it needs to be suggested by the release maintainer as far as I understood. That would be Steve Sakoman at the moment, c.f. https://wiki.yoctoproject.org/wiki/Releases. Steve said no for styhead (no further release) and no for scarthgap (not comfortable with the amount of changes and potential breakage). I personally believe a simple no on the mailing list can still be appealed by trying to convince the other person until a full stop no is given or consensus is reached, so you may try to find ways to limit the possibility of breakage, especially unforeseen ones so Steve would be more comfortable with the changes, essentially figuring out what would make the release maintainer more comfortable with the patches. But the current situation is, no desire to accept the patches into scarthgap via the main branch. Cheers, Quentin
On Fri, Mar 28, 2025 at 10:26:49AM +0100, Quentin Schulz wrote: > https://wiki.yoctoproject.org/wiki/Stable_Release_and_LTS#Stable/LTS_Patch_Acceptance_Policies > > In any case, it needs to go through TSC > (https://wiki.yoctoproject.org/wiki/TSC) before being accepted I believe. To > reach TSC, it needs to be suggested by the release maintainer as far as I > understood. That would be Steve Sakoman at the moment, c.f. > https://wiki.yoctoproject.org/wiki/Releases. Steve said no for styhead (no > further release) and no for scarthgap (not comfortable with the amount of > changes and potential breakage). I personally believe a simple no on the > mailing list can still be appealed by trying to convince the other person > until a full stop no is given or consensus is reached, so you may try to > find ways to limit the possibility of breakage, especially unforeseen ones > so Steve would be more comfortable with the changes, essentially figuring > out what would make the release maintainer more comfortable with the > patches. But the current situation is, no desire to accept the patches into > scarthgap via the main branch. Got it, thanks Quentin! Thanks for sharing the links as well. I will try a v3 in the next days, see if I can make something that makes everybody comfortable with, otherwise I also might consider the other layer suggested by Alexander. > > Cheers, > Quentin Cheers, Hiago.
From: Hiago De Franco <hiago.franco@toradex.com> Update the linux-firmware recipe to the most recent upstream tag. This is basically a backport of the commits from master into styhead, related to the linux-firmware recipe. Commit 30ea609d3357 ("meta/meta-selftest: Fix variable assignment whitespace") changes a lot of files (linux-firmware included), but they are all related to missing whitespaces to improve redability, this is the reason I have decided to cherry-pick this commit as well. v2: - As requested, I converted the v1 patch into backports from oe-core master. v1: - https://lore.kernel.org/openembedded-core/20250325215115.10430-1-hiagofranco@gmail.com/ Alex Kiernan (1): linux-firmware: Add RTL8723DS blobs into ${PN}-rtl8723 Dmitry Baryshkov (16): linux-firmware: add battmgr.jsn to ${PN}-qcom-qcm6490-audio linux-firmware: split qcm6490 ZAP shader to separate package linux-firmware: split sa8775p ZAP shader to separate package linux-firmware: make ${PN}-qcom-adreno-a663 depend on -a660 linux-firmware: package IPA firmware for Qualcomm QCM6490 platforms linux-firmware: RPROVIDE qcs6490 firmware packages by qcm6490 ones linux-firmware: upgrade 20241017 -> 20241110 linux-firmware: package Qualcomm X1 Elite audio DSP firmware linux-firmware: package QCS615 Adreno ZAP shader linux-firmware: upgrade 20241110 -> 20241210 linux-firmware: package firmware for Qualcomm AIC100 and QDU100 linux-firmware: upgrade 20241210 -> 20250109 linux-firmware: split the qca6390 firmware linux-firmware: further split qca61x4 package linux-firmware: fix qca-qca61x4-usb package contents linux-firmware: make linux-firmware-qcom-qcm6490-wifi provide -qcs6490- Marc Ferland (5): linux-firmware: split ath10k firmwares in separate packages linux-firmware: split ath11k firmwares in separate packages linux-firmware: split amdgpu firmwares in separate packages linux-firmware: split ath12k firmwares in separate packages linux-firmware: split qca firmwares in separate packages Richard Purdie (1): meta/meta-selftest: Fix variable assignment whitespace Vivek Puar (6): linux-firmware: add new fw file to ${PN}-qcom-adreno-a660 linux-firmware: Add qcom-qcm6490-{audio,compute} firmware packages linux-firmware: Add qcom-adreno-a663 package linux-firmware: upgrade 20250109 -> 20250211 linux-firmware: upgrade 20250211 -> 20250311 linux-firmware: update qca-qca61x4-usb package contents Zoltan Boszormenyi (1): linux-firmware: Fix packaging of some subpackages Zoltán Böszörményi (1): linux-firmware: Upgrade to 20241017 and allow compressing firmware .../sysdig/sysdig-selftest_0.28.0.bb | 2 +- .../bbclasses/systemd-and-sysvinit.bb | 2 +- .../recipes-test/bbclasses/systemd-only.bb | 2 +- .../recipes-test/gitrepotest/gitrepotest.bb | 2 +- .../selftest-users/acreategroup.bb | 2 +- .../selftest-users/bcreategroup.bb | 2 +- .../selftest-users/ccreategroup.bb | 2 +- .../selftest-users/dcreategroup.bb | 2 +- meta/classes-global/base.bbclass | 2 +- meta/classes-recipe/autotools.bbclass | 2 +- meta/classes-recipe/cargo.bbclass | 2 +- meta/classes-recipe/go.bbclass | 4 +- meta/classes-recipe/gtk-icon-cache.bbclass | 2 +- meta/classes-recipe/kernel.bbclass | 2 +- meta/classes-recipe/python3native.bbclass | 6 +- meta/classes-recipe/python_pyo3.bbclass | 12 +- meta/classes-recipe/rust.bbclass | 8 +- meta/classes-recipe/setuptools3.bbclass | 2 +- .../classes-recipe/setuptools3_legacy.bbclass | 2 +- meta/conf/documentation.conf | 2 +- meta/recipes-bsp/u-boot/u-boot-tools.inc | 2 +- meta/recipes-connectivity/connman/connman.inc | 4 +- .../inetutils/inetutils_2.5.bb | 2 +- meta/recipes-core/coreutils/coreutils_9.5.bb | 2 +- meta/recipes-core/glibc/glibc-package.inc | 2 +- .../glibc/glibc-y2038-tests_2.40.bb | 2 +- meta/recipes-core/meta/meta-environment.bb | 2 +- meta/recipes-core/musl/musl_git.bb | 2 +- meta/recipes-core/newlib/newlib.inc | 2 +- meta/recipes-core/os-release/os-release.bb | 2 +- meta/recipes-core/ovmf/ovmf-shell-image.bb | 2 +- meta/recipes-core/ovmf/ovmf_git.bb | 6 +- .../packagegroup-rust-cross-canadian.bb | 2 +- meta/recipes-core/picolibc/picolibc.inc | 2 +- .../binutils/binutils-2.43.1.inc | 2 +- meta/recipes-devtools/cmake/cmake_3.30.2.bb | 2 +- .../nativesdk-icecc-toolchain_0.1.bb | 2 +- .../libtool/libtool-2.5.2.inc | 2 +- .../perl/libxml-parser-perl_2.47.bb | 2 +- .../python/python3-attrs_24.2.0.bb | 2 +- .../python/python3-pygobject_3.48.2.bb | 2 +- .../recipes-devtools/python/python3_3.12.9.bb | 2 +- meta/recipes-devtools/rust/rust_1.79.0.bb | 2 +- .../asciidoc/asciidoc_10.2.1.bb | 2 +- .../baremetal-helloworld_git.bb | 2 +- .../go-examples/go-helloworld_0.1.bb | 2 +- meta/recipes-extended/gzip/gzip.inc | 4 +- .../logrotate/logrotate_3.22.0.bb | 2 +- .../perl/libxml-namespacesupport-perl_1.12.bb | 2 +- meta/recipes-extended/shadow/shadow.inc | 2 +- meta/recipes-extended/timezone/timezone.inc | 2 +- .../libadwaita/libadwaita_1.5.3.bb | 2 +- meta/recipes-graphics/mesa/mesa.inc | 26 +- .../xorg-lib/xcb-util-errors_1.0.1.bb | 2 +- .../xorg-proto/xorgproto_2024.1.bb | 2 +- .../cryptodev/cryptodev-module_1.14.bb | 2 +- .../cryptodev/cryptodev-tests_1.14.bb | 2 +- ...20240909.bb => linux-firmware_20250311.bb} | 869 +++++++++++++----- meta/recipes-kernel/linux/kernel-devsrc.bb | 2 +- meta/recipes-kernel/linux/linux-yocto-dev.bb | 6 +- .../linux/linux-yocto-rt_6.10.bb | 6 +- .../linux/linux-yocto-rt_6.6.bb | 6 +- meta/recipes-kernel/linux/linux-yocto.inc | 4 +- meta/recipes-kernel/linux/linux-yocto_6.10.bb | 12 +- meta/recipes-kernel/linux/linux-yocto_6.6.bb | 12 +- .../lttng/lttng-modules_2.13.14.bb | 2 +- .../make-mod-scripts/make-mod-scripts_1.0.bb | 2 +- meta/recipes-kernel/perf/perf.bb | 2 +- .../gstreamer/gstreamer1.0-meta-base.bb | 4 +- meta/recipes-sato/l3afpad/l3afpad_git.bb | 2 +- meta/recipes-support/apr/apr_1.7.5.bb | 2 +- meta/recipes-support/gnutls/gnutls_3.8.6.bb | 2 +- meta/recipes-support/gpgme/gpgme_1.23.2.bb | 2 +- meta/recipes-support/vte/vte_0.76.3.bb | 4 +- 74 files changed, 783 insertions(+), 324 deletions(-) rename meta/recipes-kernel/linux-firmware/{linux-firmware_20240909.bb => linux-firmware_20250311.bb} (66%)