This target produces a tarball following the most recent git tag.
The tarball contains firmware binaries that have been de-duped.
Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
This requires a personal access token with write repository permissions
to be created and a pipeline scheduled with the RELEASE_TOKEN masked
variable set.
When that combination is done, a tag is automatically created following
`YYYYMMDD` syntax when the pipeline runs.
Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
This will make it render more nicely if linux-firmware.git moves
to Gitlab or a fork of it is hosted in Gitlab.
Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
There were some releases of MTL DMC since the last update. We are
updating to v2.16 here, but see below release notes for each release.
Release notes for v2.16:
1. Bug fix for Debuggability DCN.
Release notes for v2.15:
1. Bug fix for HRR.
Release notes for v2.14:
1. Fix for HRR feature.
Signed-off-by: Gustavo Sousa <gustavo.sousa@intel.com>
Currently, 'Raw: <filename>' needs to be added to WHENCE for files that
must not be compressed. This means that such files need to be listed
twice ('File: <filename>' and 'Raw: <filename>') which is not pretty and
error prone. Also, the current implementation is broken for filenames
that contain quotes (") and it also requires grep'ing of WHENCE for every
processed line which slows things down.
Fix all of the above by introducing a new keyword 'RawFile' so that such
files are listed only once, quotes are handled correctly and grep is no
longer needed.
Signed-off-by: Juerg Haefliger <juerg.haefliger@canonical.com>
Signed-off-by: Josh Boyer <jwboyer@kernel.org>
Any options following the compressor option --zstd or --xz are passed on
to the compressor as additional options so that - for example - the
compression level can be specified:
$ ./copy-firmware.sh --zst -19 <destdir>
Signed-off-by: Juerg Haefliger <juerg.haefliger@canonical.com>
Signed-off-by: Josh Boyer <jwboyer@kernel.org>
This patch updates the firmware file for Intel Bluetooth AX203
Also it is known as Intel JohnsonPeak (JnP2).
FW Build: REL68350
Release Version: 22.250.0.2
Signed-off-by: Lokendra Singh <lokendra.singh@intel.com>
Signed-off-by: Josh Boyer <jwboyer@kernel.org>
This patch updates the firmware file for Intel Bluetooth AX203
Also it is known as Intel JohnsonPeak (JnP2).
FW Build: REL68350
Release Version: 22.250.0.2
Signed-off-by: Lokendra Singh <lokendra.singh@intel.com>
Signed-off-by: Josh Boyer <jwboyer@kernel.org>
This patch updates the firmware file for Intel Bluetooth AX211
Also it is known as Intel GarfieldPeak (GfP2).
FW Build: REL68350
Release Version: 22.250.0.2
Signed-off-by: Lokendra Singh <lokendra.singh@intel.com>
Signed-off-by: Josh Boyer <jwboyer@kernel.org>
This patch updates the firmware file for Intel Bluetooth AX211
Also it is known as Intel GarfieldPeak (GfP2).
FW Build: REL68350
Release Version: 22.250.0.2
Signed-off-by: Lokendra Singh <lokendra.singh@intel.com>
Signed-off-by: Josh Boyer <jwboyer@kernel.org>
This patch updates the firmware file for Intel Bluetooth AX210
Also it is known as Intel TyphoonPeak (TyP2).
FW Build: REL68350
Release Version: 22.250.0.2
Signed-off-by: Lokendra Singh <lokendra.singh@intel.com>
Signed-off-by: Josh Boyer <jwboyer@kernel.org>
This patch updates the firmware file for Intel Bluetooth AX200
Also it is known as Intel CyclonePeak (CcP2).
FW Build: REL53497
Release Version: 22.250.0.2
Signed-off-by: Lokendra Singh <lokendra.singh@intel.com>
Signed-off-by: Josh Boyer <jwboyer@kernel.org>
This patch updates the firmware file for Intel Bluetooth AX201
Also it is known as Intel HarrisonPeak (HrP2).
FW Build: REL53497
Release Version: 22.250.0.2
Signed-off-by: Lokendra Singh <lokendra.singh@intel.com>
Signed-off-by: Josh Boyer <jwboyer@kernel.org>
Update firmware for Intel qat_4xxx devices.
This firmware is taken from Intel QuickAssist Technology Hardware
Version 2.0 package QAT20.L.1.0.50-00003 [1].
Release notes for this firmware are reported at [2].
$ sha256sum qat_4xxx.bin
893caab5ce46e590c89e1dc434a28cd24a4b2405c2e63ddde6185223a3d53fba qat_4xxx.bin
Link: https://downloadmirror.intel.com/783270/QAT20.L.1.0.50-00003.tar.gz [1]
Link: https://intel.github.io/quickassist/RN/In-Tree/index.html [2]
Signed-off-by: Adam Guerin <adam.guerin@intel.com>
Signed-off-by: Gavin Troy <gavin.troy@intel.com>
Signed-off-by: Josh Boyer <jwboyer@kernel.org>
Update AMD SEV firmware version 1.55 build 8 for AMD family 19h processors
with models in the range 00h to 0fh.
Add AMD SEV firmware version 1.55 build 21 for AMD family 19h processors
with models in the range 10h to 1fh.
Signed-off-by: John Allen <john.allen@amd.com>
Signed-off-by: Josh Boyer <jwboyer@kernel.org>
DMCUB updates for Navi2x, DCN314 and DCN32.
From internal git commit 4ad2a00530b57c10b3abb9f8d055d78c3188c97c.
Tested with DC v3.2.249
Release notes:
- Add the ability to check if replay is supported
- Fix a black screen issue that causes a hard hang after hotplugging
- Fix an issue that caused the screen to flash on shutdown
- Fix link loss observed during DP2.1 PHY compliance testing
- Replay fixes
Signed-off-by: Hamza Mahfooz <hamza.mahfooz@amd.com>
Fix MBSSID number exceed array size and support firmware log format
Signed-off-by: Chin-Yen Lee <timlee@realtek.com>
Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>
First GSC FW release for MTL.
Release: 102.0.0.1655
Compatibility (API) Version: 1.0
SVN: 1
The firmware file is named after the compatibility version, as that is
what the kernel driver cares about.
Signed-off-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
DMCUB updates for Navi33
From internal git commit d132070e61f67284e84f106b8767ac05f342d9fe
Firmware release 0.0.180.0
Tested with DC 3.2.248.
- Adjust workflow for for subvp
Signed-off-by: Wayne Lin <Wayne.Lin@amd.com>
DMCUB updates for Navi32, Navi33
From internal git commit ace3cf43fbba4398c0cf8a66a6977c208278a0df
DC Firmware update 0.0.179.0, tested with DC 3.2.247.
Fix intermittent flickering for 4K display
Signed-off-by: Stylon Wang <stylon.wang@amd.com>
Signed-off-by: Josh Boyer <jwboyer@kernel.org>
We tried to do a partial revert of commit a5d7b4df ("amdgpu: update GC
11.0.2 firmware for amd.5.5 release") and commit ffe1a41e ("amdgpu:
update GC 11.0.0 firmware for amd.5.5 release") to help with a
compatibility issue with EOL kernels that didn't pick up stable patches,
but this caused more problems.
It causes some systems to fail to resume from S3 and some systems to
fail to boot. Our priority should be making things work with kernels
that we can actively support, not EOL kernels. Stable kernels,
the LTS kernel, and development kernels all work with the latest
firmware.
This reverts commit 789aa81504.
Cc: alexander.deucher@amd.com
Reported-by: shtetldik@gmail.com
Link: https://gitlab.freedesktop.org/drm/amd/-/issues/2782
Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
Signed-off-by: Josh Boyer <jwboyer@kernel.org>
When GC 11.0.0/11.0.2 firmware was updated it caused a regression where
kernels without the following commits wouldn't be able to boot properly:
ac2f5739fdca drm/amdgpu/mes11: enable reg active poll
a2fe4534bb38 drm/amd/amdgpu: update mes11 api def
The intention was that there was a fallback path and kernels with both
those commits and these commits:
da9a8dc33da2 drm/amdgpu: reserve the old gc_11_0_*_mes.bin
616843d5a11b drm/amd/amdgpu: introduce gc_*_mes_2.bin v2
09bf14907d86 drm/amdgpu: declare firmware for new MES 11.0.4
Would be able to work properly. The newer firmware that requires ac2f5739fdca
and a2fe4534bb38 would use `*mes_2.bin` and the older firmware that could
work without those commits would use `*_mes1.bin`.
This seems to have not panned out properly because users report that upgrading
to Ubuntu's 6.2 kernel that is missing the commits fails to boot. To fix the
issue, do a partial revert for those specific binaries.
Fixes: a5d7b4df ("amdgpu: update GC 11.0.2 firmware for amd.5.5 release")
Fixes: ffe1a41e ("amdgpu: update GC 11.0.0 firmware for amd.5.5 release")
Link: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2024427
Link: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2027959
Link: https://bugs.launchpad.net/linux-firmware/+bug/2029396
Link: https://gitlab.freedesktop.org/drm/amd/-/issues/2773
Link: https://gitlab.freedesktop.org/drm/amd/-/issues/2757
Link: https://gitlab.freedesktop.org/drm/amd/-/issues/2585
Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
Signed-off-by: Josh Boyer <jwboyer@kernel.org>
This firmware is submitted for RTL8852C BT USB I/F.
Release version is 0x040D_7225
Due to the follow-up RTL8852C firmware patch is format v2,
the RTL8852C BT USB firmware updates will be launched
with rtl8852cu_fw_v2.bin.
Suggested-by: Juerg Haefliger <juerg.haefliger@canonical.com>
Signed-off-by: Hilda Wu <hildawu@realtek.com>
Signed-off-by: Josh Boyer <jwboyer@kernel.org>
This reverts commit 55e7448533.
Commit 55e7448533 replaced rtl_bt firmware with a v2 binary which
is not compatible with older kernels and introduced a regression.
Undo that and add the v2 binary later using a different filename.
Let the rtl8852cu_fw.bin file keep the firmware format v1 and stay
at version 0xD7B8_FABF.
Subsequent RTL8852C BT USB firmware format v2 updates will be
launched with rtl8852cu_fw_v2.bin
Suggested-by: Juerg Haefliger <juerg.haefliger@canonical.com>
Signed-off-by: Hilda Wu <hildawu@realtek.com>
Reviewed-by: Juerg Haefliger <juerg.haefliger@canonical.com>
Signed-off-by: Josh Boyer <jwboyer@kernel.org>
Josh Boyer