From: Bitterblue Smith <rtl8821cerfe2@gmail.com>
To: linux-wireless@vger.kernel.org
Cc: Jes Sorensen <Jes.Sorensen@gmail.com>,
Larry Finger <Larry.Finger@lwfinger.net>
Subject: rtl8xxxu: Should it support RTL8188EU?
Date: Sun, 2 Oct 2022 00:42:49 +0300 [thread overview]
Message-ID: <2999b8e8-5706-8bfb-c3a5-5c547ab0a170@gmail.com> (raw)
Considering there is a driver for RTL8188EU already in staging,
which people have been whittling down, should I put any effort
into adding support to rtl8xxxu?
It's actually mostly working already [0], but rtl8xxxu doesn't
have AP mode, adhoc mode, power saving, etc so it wouldn't be
necessarily better than the driver in staging.
[0] https://git.kernel.org/pub/scm/linux/kernel/git/jes/linux.git/log/drivers/net/wireless/realtek/rtl8xxxu?h=rtl8xxxu-8188eu
next reply other threads:[~2022-10-01 21:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-01 21:42 Bitterblue Smith [this message]
2022-10-03 13:12 ` rtl8xxxu: Should it support RTL8188EU? Jes Sorensen
2022-10-20 11:40 ` Bitterblue Smith
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=2999b8e8-5706-8bfb-c3a5-5c547ab0a170@gmail.com \
--to=rtl8821cerfe2@gmail.com \
--cc=Jes.Sorensen@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
/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).