linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: Arnd Bergmann <arnd@kernel.org>, Kalle Valo <kvalo@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
	Nicolas Ferre <nicolas.ferre@microchip.com>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Claudiu Beznea <claudiu.beznea@tuxon.dev>,
	Jakub Kicinski <kuba@kernel.org>, Pavel Machek <pavel@ucw.cz>,
	"David S. Miller" <davem@davemloft.net>,
	Larry Finger <Larry.Finger@lwfinger.net>,
	linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-staging@lists.linux.dev
Subject: Re: [PATCH] [RFC] wireless: move obsolete drivers to staging
Date: Wed, 11 Oct 2023 20:13:24 +0200	[thread overview]
Message-ID: <da777a72-55d1-4ee3-91c8-30afe7659f54@gmail.com> (raw)
In-Reply-To: <20231010155444.858483-1-arnd@kernel.org>

On 10/10/23 17:27, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de> While looking at the old drivers 
> using the obsolete .ndo_do_ioctl() callback, I found a number of network 
> drivers that are especially obsolete, in particular for 802.11b 
> (11Mbit/s) or even older wireless networks, using non-busmaster 
> ISA/PCMCIA style bus interfaces, and using the legacy wireless extension 
> ioctls rather than the netlink interfaces that were meant to replace 
> them in 2007. All of these drivers are obsolete or orphaned. We had 
> previously discussed this topic, but nobody ever moved the files, so I 
> now went through the list to my best knowledge. These are the drivers 
> that I would classify as "probably unused" by now:

I found a USB WLAN Stick with a rtl8192u. I got it last Saturday and 
found out that the firmware is missing in my ubuntu 20.04. I found it on 
the web and fixed it. When I started the driver my computer crashed. The 
missing part was: priv->priv_wq = alloc_workqueue("priv_wq", 0, 0); 
Fixing this the next error was a network = kzalloc(sizeof(*network), 
GFP_KERNEL); in wrong context with leads to a crash of my computer. 
Fixing this leads to another issue which lets my computer crash.

For me the firmware of rtl8192u was intentionally missing because of the 
issues with the driver.

What this has to do with your question?
Can we check for missing firmware in main distributions to know which 
drivers are considered to be old and unused?

Bye Philipp

  parent reply	other threads:[~2023-10-11 18:13 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-10 15:27 [PATCH] [RFC] wireless: move obsolete drivers to staging 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
2023-10-11 18:13 ` Philipp Hortmann [this message]
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=da777a72-55d1-4ee3-91c8-30afe7659f54@gmail.com \
    --to=philipp.g.hortmann@gmail.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=alexandre.belloni@bootlin.com \
    --cc=arnd@arndb.de \
    --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=nicolas.ferre@microchip.com \
    --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;
as well as URLs for NNTP newsgroup(s).