From: "Arnd Bergmann" <arnd@arndb.de>
To: "Kalle Valo" <kvalo@kernel.org>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Arnd Bergmann" <arnd@kernel.org>,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev,
linux-wireless@vger.kernel.org,
"Claudiu Beznea" <claudiu.beznea@tuxon.dev>,
"Pavel Machek" <pavel@ucw.cz>, "Jakub Kicinski" <kuba@kernel.org>,
"David S . Miller" <davem@davemloft.net>,
linux-arm-kernel@lists.infradead.org,
"Larry Finger" <Larry.Finger@lwfinger.net>
Subject: Re: [PATCH] [RFC] wireless: move obsolete drivers to staging
Date: Wed, 11 Oct 2023 11:01:25 +0200 [thread overview]
Message-ID: <f5243ad9-0e7d-4a2f-b944-a45c41330aaf@app.fastmail.com> (raw)
In-Reply-To: <87r0m14khb.fsf@kernel.org>
On Wed, Oct 11, 2023, at 10:44, Kalle Valo wrote:
> "Arnd Bergmann" <arnd@arndb.de> writes:
>> On Wed, Oct 11, 2023, at 07:40, Kalle Valo wrote:
>>> Greg Kroah-Hartman <gregkh@linuxfoundation.org> writes:
>>>
>>> We (the wireless folks) have been talking about dropping legacy drivers
>>> on and off for several years now. The problem is that we don't know
>>> which of them work and which not, for example IIRC someone reported
>>> recently that wl3501 still works.
>>>
>>> Personally I would be extremly happy to remove all the ancient drivers
>>> as that reduces the amount of code for us to maintain but is that the
>>> right thing to do for the users? I don't have an answer to that,
>>> comments very welcome.
>>
>> I had a look at what openwrt enables, to see if any of the drivers
>> in my RFC patch are actually enabled, if anything supports legacy
>> embedded devices with these it would be openwrt. The good news here
>> is that openwrt intentionally leaves WEXT disabled, and none of them
>> are still in use.
>
> I don't think openwrt is a good metric in this case. These drivers are
> for 20+ years old hardware, most likely running on really old x86
> laptops. So the chances of them running openwrt on those laptops is low
> and I would expect them to run more traditional distros like debian or
> ubuntu. But of course this is just guessing.
OpenWRT is clearly not a good metric for laptops, but it's a good
indicator for embedded systems, in particular those with wireless
access points, and it does enable a lot of them
(atheros, broadcom, intel, marvell, ralink, realtek, mt76, wlcore,
rsi ...) depending on the platform.
I can also see that it used to enable airo, p54, hermes, adm8211,
zd1211, ipw2x00 and libertas but stopped this a year ago, see
https://github.com/openwrt/openwrt/commit/a06e023b4e12
Arnd
next prev parent reply other threads:[~2023-10-11 9:02 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 15:27 Arnd Bergmann
2023-10-10 16:08 ` Greg Kroah-Hartman
2023-10-11 5:40 ` Kalle Valo
2023-10-11 6:16 ` Greg Kroah-Hartman
2023-10-11 7:29 ` Kalle Valo
2023-10-11 15:09 ` Jakub Kicinski
2023-10-12 11:47 ` Kalle Valo
2023-10-12 14:36 ` Arnd Bergmann
2023-10-12 14:48 ` Kalle Valo
2023-10-12 15:11 ` Geert Uytterhoeven
2023-10-12 15:28 ` Johannes Berg
2023-10-12 15:39 ` Geert Uytterhoeven
2023-10-12 15:41 ` Johannes Berg
2023-10-12 16:36 ` Geoff Levand
2023-10-13 15:44 ` Arnd Bergmann
2023-10-13 18:02 ` Johannes Berg
2023-10-18 20:37 ` Jeff Johnson
2023-10-12 16:16 ` Philipp Hortmann
2023-10-12 16:18 ` Dan Williams
2023-10-11 7:24 ` Arnd Bergmann
2023-10-11 7:41 ` Greg Kroah-Hartman
2023-10-11 8:44 ` Kalle Valo
2023-10-11 9:01 ` Arnd Bergmann [this message]
2023-10-11 18:13 ` Philipp Hortmann
2023-10-11 20:22 ` Arnd Bergmann
2023-10-12 6:23 ` Dan Carpenter
2023-10-13 6:42 ` Philipp Hortmann
2023-10-13 15:36 ` Arnd Bergmann
2023-10-13 16:24 ` Larry Finger
2023-10-15 18:42 ` Philipp Hortmann
2023-10-18 16:05 ` Arnd Bergmann
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=f5243ad9-0e7d-4a2f-b944-a45c41330aaf@app.fastmail.com \
--to=arnd@arndb.de \
--cc=Larry.Finger@lwfinger.net \
--cc=alexandre.belloni@bootlin.com \
--cc=arnd@kernel.org \
--cc=claudiu.beznea@tuxon.dev \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux-wireless@vger.kernel.org \
--cc=pavel@ucw.cz \
/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®