From: Larry Finger <Larry.Finger@lwfinger.net>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Support for RTL8188FU
Date: Tue, 1 Oct 2019 13:52:30 -0500 [thread overview]
Message-ID: <b958b669-a683-d7cd-6bbf-bfe3e674f62d@lwfinger.net> (raw)
In-Reply-To: <20191001174612.4kj3mt3h5epidyyk@linutronix.de>
On 10/1/19 12:46 PM, Sebastian Andrzej Siewior wrote:
> On 2019-10-01 11:47:44 [-0500], Larry Finger wrote:
>> 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.
>
> yeah, seen that.
>
>> You should be able to find the code that differs between 8188EU and 8188FU
>> to see what is different.
>
> So you would recommend to try to merge it to the staging driver.
If that is what you read, that is not what I meant.
The staging driver is really old and does not support nl80211 and friends. If
you are willing to undertake a 6 to 12-month rewrite of the driver you have, and
it supports RTL8188EU, then a replacement of the staging driver would be what
you should do. If you do not want to make that kind of time commitment, then a
GitHub repo would be your best bet; however, GitHub already has 5 such repos for
the rtl8188fu. As far as I can tell, none of them are yours.
The first thing I would do is clone the v5.2.2.4 branch of lwfinger/rtl8188eu at
GitHub, add the USB ID for your device, and see if that works. I expect it will.
If so, that would get you quite a ways toward the changes needed to get that
driver into staging.
Larry
next prev parent reply other threads:[~2019-10-01 18:52 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
2019-10-01 17:46 ` Sebastian Andrzej Siewior
2019-10-01 18:52 ` Larry Finger [this message]
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=b958b669-a683-d7cd-6bbf-bfe3e674f62d@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).