From: Kalle Valo <kvalo@kernel.org>
To: Philipp Hortmann <philipp.g.hortmann@gmail.com>
Cc: linux-kernel@vger.kernel.org,
"David S . Miller" <davem@davemloft.net>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Claudiu Beznea <claudiu.beznea@tuxon.dev>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Geoff Levand <geoff@infradead.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jakub Kicinski <kuba@kernel.org>,
Jeff Johnson <quic_jjohnson@quicinc.com>,
Johannes Berg <johannes@sipsolutions.net>,
Larry Finger <Larry.Finger@lwfinger.net>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Pavel Machek <pavel@ucw.cz>, Stanislaw Gruszka <stf_xl@wp.pl>,
Gregory Greenman <gregory.greenman@intel.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
linux-arm-kernel@lists.infradead.org,
linux-staging@lists.linux.dev, linux-wireless@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>,
Stefan Lippers-Hollmann <s.l-h@gmx.de>
Subject: Re: [RFC] ipw2100 ipw2200 ps3_gelic rtl8712 --- Are we ready for wext cleanup?
Date: Mon, 14 Oct 2024 12:32:04 +0300 [thread overview]
Message-ID: <87iktv58tn.fsf@kernel.org> (raw)
In-Reply-To: <a7eb3db4-ad0d-451a-9106-90d481bd3231@gmail.com> (Philipp Hortmann's message of "Sun, 13 Oct 2024 22:28:48 +0200")
Philipp Hortmann <philipp.g.hortmann@gmail.com> writes:
> origin of this question was the following patch series from Arnd Bergmann
> [PATCH 00/10] Remove obsolete and orphaned wifi drivers
> https://lore.kernel.org/linux-staging/20231023131953.2876682-1-arnd@kernel.org/
>
> Here the remaining files that use iw_handler_def:
> drivers/net/ethernet/toshiba/ps3_gelic_wireless.c:static const struct
> iw_handler_def gelic_wl_wext_handler_def = {
> drivers/net/wireless/intel/ipw2x00/ipw2100.c:static const struct
> iw_handler_def ipw2100_wx_handler_def;
> drivers/net/wireless/intel/ipw2x00/ipw2100.c:static const struct
> iw_handler_def ipw2100_wx_handler_def = {
> drivers/net/wireless/intel/ipw2x00/ipw2200.c:static const struct
> iw_handler_def ipw_wx_handler_def = {
> drivers/staging/rtl8712/os_intfs.c: pnetdev->wireless_handlers =
> (struct iw_handler_def *)
> drivers/staging/rtl8712/rtl871x_ioctl.h:extern struct iw_handler_def
> r871x_handlers_def;
> drivers/staging/rtl8712/rtl871x_ioctl_linux.c:struct iw_handler_def
> r871x_handlers_def = {
>
>
> In this Email Greg writes over rtl8192e:
> https://lore.kernel.org/linux-staging/2024100810-payback-suds-8c15@gregkh/
> "...
> No staging driver should ever get in the way of api changes elsewhere in
> the kernel, that's one of the rules of this part of the tree. So from
> my opinion, it's fine to delete it now. It can always come back in a
> new way later on.
> ..."
>
> So it should not be an issue to remove rtl8712.
>
> Stefan Lippers-Hollmann was one year ago still using the ipw2200.
> https://lore.kernel.org/linux-staging/20231024014302.0a0b79b0@mir/
>
> Here my opinion why I think we should reconsider this:
>
> I really like to use old hardware. One of my computers is from trash
> and the other one is bought for 50€ three years ago. But non of my
> hardware is from before 2012. Do we as a community really need to
> support hardware from 2003 in kernel 6.13 for WLAN that evolved so
> rapidly? I do not think so.
>
> People around me are complaining that the 2,4GHz WLAN is difficult to
> use because so many devices are using it. Such slow devices consume a
> lot of time to send and receive the data and block therefore other
> devices.
>
> The longterm kernels will still support this hardware for years.
>
> Please explain to our very high value resources (Maintainers,
> Developers with wext and mac80211 expierience) that you cannot find
> any other solution that is within technical possibility and budget
> (USB WLAN Stick or exchange of WLAN module) and that they need to
> invest their time for maintenance.
> Here the example of invested time from Johannes Berg:
> https://lore.kernel.org/all/20241007213525.8b2d52b60531.I6a27aaf30bded9a0977f07f47fba2bd31a3b3330@changeid/
>
> I cannot ask the Linux kernel community to support my test hardware
> just because I bought it some time ago. Rather, I have to show that I
> use it for private or business purposes on a regular basis and that I
> cannot easily change.
>
> Using this hardware is security wise not state of the art as WPA3 is
> not supported. We put so much effort into security. Why not here?
I didn't quite get what you are saying here, are you proposing that we
should remove ancient drivers faster?
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-10-14 9:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-13 20:28 [RFC] ipw2100 ipw2200 ps3_gelic rtl8712 --- Are we ready for wext cleanup? Philipp Hortmann
2024-10-14 9:32 ` Kalle Valo [this message]
2024-10-14 18:39 ` Philipp Hortmann
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=87iktv58tn.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=Larry.Finger@lwfinger.net \
--cc=alexandre.belloni@bootlin.com \
--cc=arnd@arndb.de \
--cc=claudiu.beznea@tuxon.dev \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=geoff@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=gregory.greenman@intel.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@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=linuxppc-dev@lists.ozlabs.org \
--cc=nicolas.ferre@microchip.com \
--cc=pavel@ucw.cz \
--cc=philipp.g.hortmann@gmail.com \
--cc=quic_jjohnson@quicinc.com \
--cc=s.l-h@gmx.de \
--cc=stf_xl@wp.pl \
/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).