From: Larry Finger <Larry.Finger@lwfinger.net>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-wireless@vger.kernel.org
Subject: Re: Support for RTL8188FU
Date: Tue, 1 Oct 2019 11:47:44 -0500 [thread overview]
Message-ID: <3af284c7-ee46-dd42-9549-de55feae2528@lwfinger.net> (raw)
In-Reply-To: <20191001160305.qrl4nt2jmdsogaaz@linutronix.de>
On 10/1/19 11:03 AM, Sebastian Andrzej Siewior wrote:
> Hi,
>
> I'm looking into support for RTL8188FU with the vendor driver next to
> me. There is a driver called rtl8188eu in staging. Is there a way to
> figure out the difference between E and F?
> Then there is rtl8xxxu outside of staging claiming to support
> RTL8188[CR]U. No idea what C & R is and how much difference there is
> towards F or E.
>
> Any suggestions what would be the best way towards support for the F
> chip?
A quick Internet search shows me that the RTL8188FU is a low-cost chip used on
Raspberry PI and other similar low-cost systems.
The USB group at Realtek is notorious for their lack of support for Linux
drivers. The ones they release have lots of dead code used for Windows and
FreeBSD drivers, and they have lots of code that applies to other chips. With
other drivers that I have placed at GitHub, some of the commits that remove dead
code will remove as many of 10K lines.
You should be able to find the code that differs between 8188EU and 8188FU to
see what is different.
The 8188RU is a special variant of the 8188EU. I have no idea what an 8188CU is.
Your only starting point is the driver that is next to you!
Larry
next prev parent reply other threads:[~2019-10-01 16:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 16:03 Support for RTL8188FU Sebastian Andrzej Siewior
2019-10-01 16:47 ` Larry Finger [this message]
2019-10-01 17:46 ` Sebastian Andrzej Siewior
2019-10-01 18:52 ` Larry Finger
2019-10-01 20:48 ` Sebastian Andrzej Siewior
2020-03-04 10:21 ` Sebastian Andrzej Siewior
2020-03-04 18:16 ` Larry Finger
2020-03-10 14:48 ` Sebastian Andrzej Siewior
2020-03-10 14:54 ` Greg Kroah-Hartman
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=3af284c7-ee46-dd42-9549-de55feae2528@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=bigeasy@linutronix.de \
--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).