From: Stefan Lippers-Hollmann <s.l-h@gmx.de>
To: Kalle Valo <kvalo@kernel.org>
Cc: "Igor Mitsyanko" <i.mitsyanko@gmail.com>,
"Jeff Johnson" <quic_jjohnson@quicinc.com>,
"Alexis Lothoré" <alexis.lothore@bootlin.com>,
"Johannes Berg" <johannes@sipsolutions.net>,
"Ajay Singh" <ajay.kathat@microchip.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
linux-wireless@vger.kernel.org,
"Sergey Matyukevich" <geomatsi@gmail.com>,
"kernel test robot" <lkp@intel.com>,
"Claudiu Beznea" <claudiu.beznea@tuxon.dev>,
srini.raju@purelifi.com, krystal.heaton@onsemi.com
Subject: Re: wireless: orphan qfnfmac and plfxlc drivers?
Date: Wed, 28 Feb 2024 04:02:55 +0100 [thread overview]
Message-ID: <20240228040255.0932ba6c@mir> (raw)
In-Reply-To: <87msrmj9c8.fsf@kernel.org>
Hi
On 2024-02-27, Kalle Valo wrote:
> Igor Mitsyanko <i.mitsyanko@gmail.com> writes:
> > On 2/16/24 01:37, Kalle Valo wrote:
> >> Jeff Johnson <quic_jjohnson@quicinc.com> writes:
> >>> On 2/15/2024 9:21 AM, Kalle Valo wrote:
[...]
> > that's right, Quantenna division was shutdown by ON. To my knowledge
> > no users of qtnfmac drivers are left after that. I would think
> > removing driver altogether is the right approach. I'm not associated
> > with ON anymore so it's just my personal opinion.
> >
> > CCing Krystal Heaton who I found on ON "contacts" web page (just in
> > case someone from ON wants to comment if removing qtnfmac driver from
> > Linux kernel is a concern).
>
> Sad news but thanks for letting us know. So unless anyone else objects
> the plan is to remove qtnfmac driver in the near future.
In theory, there would be quite a few /potential/ users for qtnfmac
and QT3840BC 'Topaz' (QSR1000) on a variety of early 802.11ac routers
and APs (particularly on ipq8064 SOCs[0]), but as the required qtnfmac
firmware for these chipsets has never been published, there is
no wireless support for (the typically 5 GHz-) "Topaz" wlan chipset
on those devices at all.
The devices are out there (albeit not the most common- or long-lived
combination), but they never had wireless support in the first place
(first because qtnfmac didn't support QSR1000, after that was
rectified[1], because the required firmware for qtnfmac/ QSR1000 has
never been published). It's a bit sad that these never got supported.
Regards
Stefan Lippers-Hollmann
--
[0] e.g. Linksys E8350, Linksys E8400, Netgear R7500,
ZyXEL NBG6816 (Armor Z1), ZyXEL WAP6806 (Armor X1) (on mt7621)
[Disclaimer: I don't own any of these myself, but I regularly
see requests for Topaz wireless support on the r7500 and e8350]
[1] Tue Oct 16 10:23:58 2018 +0000, qtnfmac: add support for Topaz
chipsets
e401fa25cfa23df8b17960a656ff11f49facae84
prev parent reply other threads:[~2024-02-28 3:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 14:13 [PATCH 0/2] wifi: nl80211/wilc1000: force WLAN_AKM_SUITE_SAE to big endian in NL80211_CMD_EXTERNAL_AUTH Alexis Lothoré
2024-02-15 14:13 ` [PATCH 1/2] wifi: nl80211: force WLAN_AKM_SUITE_SAE in " Alexis Lothoré
2024-02-15 16:58 ` Kalle Valo
2024-02-16 8:21 ` Alexis Lothoré
2024-02-16 9:34 ` Kalle Valo
2024-02-15 14:13 ` [PATCH 2/2] wifi: wilc1000: remove AKM suite be32 conversion for external auth request Alexis Lothoré
2024-02-21 18:54 ` Kalle Valo
2024-02-15 15:50 ` [PATCH 0/2] wifi: nl80211/wilc1000: force WLAN_AKM_SUITE_SAE to big endian in NL80211_CMD_EXTERNAL_AUTH Alexis Lothoré
2024-02-15 17:06 ` wireless: orphan qfnfmac and plfxlc drivers? Kalle Valo
2024-02-15 17:21 ` Kalle Valo
2024-02-15 18:51 ` Jeff Johnson
2024-02-16 9:37 ` Kalle Valo
2024-02-26 2:13 ` Igor Mitsyanko
2024-02-27 14:00 ` Kalle Valo
2024-02-28 3:02 ` Stefan Lippers-Hollmann [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=20240228040255.0932ba6c@mir \
--to=s.l-h@gmx.de \
--cc=ajay.kathat@microchip.com \
--cc=alexis.lothore@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=geomatsi@gmail.com \
--cc=i.mitsyanko@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=krystal.heaton@onsemi.com \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lkp@intel.com \
--cc=quic_jjohnson@quicinc.com \
--cc=srini.raju@purelifi.com \
--cc=thomas.petazzoni@bootlin.com \
/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;
as well as URLs for NNTP newsgroup(s).