[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <DM3PPF63A6024A92B862A68F1EA07192752A3E2A@DM3PPF63A6024A9.namprd11.prod.outlook.com>
Date: Sun, 5 Oct 2025 13:36:41 +0000
From: "Korenblit, Miriam Rachel" <miriam.rachel.korenblit@...el.com>
To: Bartosz Golaszewski <brgl@...ev.pl>
CC: "Berg, Johannes" <johannes.berg@...el.com>, "Anjaneyulu, Pagadala Yesu"
<pagadala.yesu.anjaneyulu@...el.com>, "Grumbach, Emmanuel"
<emmanuel.grumbach@...el.com>, Bhaskar Chowdhury <unixbhaskar@...il.com>,
Bartosz Golaszewski <bartosz.golaszewski@...aro.org>, "Peer, Ilan"
<ilan.peer@...el.com>, "Gabay, Daniel" <daniel.gabay@...el.com>,
"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] Revert "wifi: iwlwifi: mvm: remove support for
REDUCE_TX_POWER_CMD ver 6 and 7"
> So the 89 at the end of the filename is not the version of the firmware?
It is. But not for "frozen devices" - like yours.
In such devices, the API number (89 in your case) doesn't increase anymore,
but we still update the FW from time to time.
> No the full version anyway? I wasn't aware of this. Where is the version
> information encoded other than the linux-firmware git log?
You can see the SHA-1 of the FW in the dmesg. For example, in the log you sent:
Loaded firmware version: 89.e9cec78e.0 ty-a0-gf-a0-89.ucode
The SHA-1 is e9cec78e.
Miri
Powered by blists - more mailing lists