From: Rory Little <roryl@candelatech.com>
To: Jeff Johnson <jeff.johnson@oss.qualcomm.com>,
Johannes Berg <johannes@sipsolutions.net>
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH wireless-next] wifi: cfg80211: add fw_version device attribute for sysfs
Date: Thu, 30 Jul 2026 10:59:07 -0700 [thread overview]
Message-ID: <897f899c-f7b3-4920-bb87-1dfb2fcdfcbc@candelatech.com> (raw)
In-Reply-To: <fb6a4b6f-08a9-484c-b170-698673a711ad@candelatech.com>
On 7/28/26 10:32 PM, Rory Little wrote:
> On 7/28/26 18:34, Jeff Johnson wrote:
>> On 7/28/2026 4:47 PM, Rory Little wrote:
>>> The firmware version is already exposed via ethtool, but is not
>>> accessible without an attached interface to create a netdev. Expose this
>>> info in sysfs to allow users to query it without the use of ethtool.
>> Curious what is the value?
>
> Here are some that I have seen:
>
> 10.4-ct-9984-xtH-011-33ec52c8
> ____000000-20251118163234
> ____000000-20251015213023
> DEV_000000-20240823172837
> DEV_000000-20220929104205
> 89.7207fc64.0 ty-a0-gf-a0-89.uc
>
> Top one is ath10k with CT firmware, next four are an assortment of
> Mediatek radios, bottom is Intel.
I just realized that I misinterpreted what you were asking about here.
Sorry about that.
The value of an interface to query fw_version for us is to keep track of
system info and generate valuable bug reports (we do our own firmware
packaging, and certain issues that we encounter can be solved by
changing firmware version). This particular commit was motivated by the
desire to be able to query it in any system configuration, as we were
hitting a case where it needed to be queried while no interfaces were
attached to the phy (thereby preventing ethtool use).
- Rory
prev parent reply other threads:[~2026-07-30 17:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 23:47 Rory Little
2026-07-29 1:34 ` Jeff Johnson
2026-07-29 5:32 ` Rory Little
2026-07-30 17:59 ` Rory Little [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=897f899c-f7b3-4920-bb87-1dfb2fcdfcbc@candelatech.com \
--to=roryl@candelatech.com \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®