From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Cc: Larry.Finger@lwfinger.net, johannes@sipsolutions.net,
kvalo@kernel.org, arnd@arndb.de
Subject: [RFC] staging: wlan-ng: Driver broken since kernel 5.15
Date: Sat, 9 Mar 2024 23:09:24 +0100 [thread overview]
Message-ID: <6dc14151-e71e-4118-826d-3ca5c8ee907f@gmail.com> (raw)
Hi,
I would remove the driver from the mainline kernel. What are your thoughts?
I bought two WLAN devices (DUT: D-Link DWL-122 and T-Sinus 111 data)
that are supported by wlan-ng driver. Issue is that the driver is not
working anymore.
The error picture is that the device does not receive any packets.
The dmesg says:
[ 123.695917] prism2_usb 2-1.6:1.0 wlan0: Unknown mgmt request message
0x0e4f9800
[ 127.508211] prism2_usb 2-1.6:1.0 wlan0: Unknown mgmt request message
0x04f0d000
...
A working commit 8fc4fb1728855a22f9149079ba51877f5ee61fc9 (HEAD) Date:
Mon Jul 5 11:16:28 2021 -0700
A failing commit d980cc0620ae77ab2572235a1300bf22519f2e86 (HEAD) Date:
Fri Jul 16 19:08:09 2021 -0700
This means that the devices are unusable since kernel 5.15.
A look into the bitrates shows that only up to 11MBits are supported.
static const struct ieee80211_rate prism2_rates[] = {
...
{ .bitrate = 110 }
};
Would be interesting to see why this happened. But it is difficult for
me to find it.
Thanks for your support.
Bye Philipp
next reply other threads:[~2024-03-09 22:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-09 22:09 Philipp Hortmann [this message]
2024-03-11 7:04 ` [RFC] staging: wlan-ng: Driver broken since kernel 5.15 Dan Carpenter
2024-03-17 20:07 ` Philipp Hortmann
2024-03-17 20:20 ` Arnd Bergmann
2024-03-18 8:01 ` Dan Carpenter
2024-03-18 8:30 ` Arnd Bergmann
2024-03-18 17:07 ` Philipp Hortmann
2024-03-12 15:57 ` 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=6dc14151-e71e-4118-826d-3ca5c8ee907f@gmail.com \
--to=philipp.g.hortmann@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=johannes@sipsolutions.net \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.