Linux wireless drivers development
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: James Hughes <james.hughes@raspberrypi.org>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Question on a RTL8812AU driver
Date: Mon, 20 Nov 2017 11:13:53 -0600	[thread overview]
Message-ID: <97422981-e0ea-850f-beed-87dc6033cc0a@lwfinger.net> (raw)
In-Reply-To: <CAE_XsML9q6=viKqG2TQCEb921reZBFuRC7=_vy87VDNqD5ONww@mail.gmail.com>

On 11/20/2017 10:39 AM, James Hughes wrote:
> Hello all,
> 
> I know there been a lot of work done on Realtek drivers in the last
> few months, and was wondering whether this will be of use for my
> particular issue.
> 
> We have a Raspberry Pi that needs to use a USB wireless adaptor
> (2001:3314) which uses the rtl8812AU chipset. We have to use this
> device as it's the only one that has been qualified for this
> particular use case.
> 
> We have been using an out of tree driver, I think originally from
> Realtek, that works, but after a few days locks up, and often requires
> a reboot on the Pi. We do have some mitigation strategies, but it'
> would be better to have a working driver. The Pi is, on the whole,
> inaccessible.
> 
> The OoT driver is from here
> https://github.com/diederikdehaas/rtl8812AU and appear quite ancient.
> 
> So, I've been looking at the 4.14 staging drivers that do seem to have
> support for some realtek devices. However, none of the drivers I have
> built recognise the module. The source of rtlwifi does refer to the
> 8812AU, but only to ignore it. There are other references throughout
> the source.,
> 
> My question, eventually, is down to figuring out whether any of the
> new staging code is destined to work on this device, or am I going to
> have to stick with the driver we are currently using which clearly has
> a lockup issue that I, in all likelihood, not going to be able to
> track down since its takes days for it to occur.
> 
> Or if anyone has any suggestions for getting this working, I'm all ears.

To my knowledge, there are no plans to convert the buggy, and badly written, 
code for the RTL8812AU into a form that would be suitable for wireless. Even 
getting it into a form that would be acceptable for staging would be a 
formidable task.

If you want this device supported by an in-kernel driver, the easiest method 
would be to extend rtl8xxxu. Jes Sorensen, the author of that driver, might be 
able to help you with that extension.

I know nothing of that "diederikdehaas" repo; however, I have a separate one at 
https://github.com/lwfinger/rtl8812au that I keep up to date. Note that I do not 
have such a device. The repo is just for convenience.

Larry

      reply	other threads:[~2017-11-20 17:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-20 16:39 Question on a RTL8812AU driver James Hughes
2017-11-20 17:13 ` Larry Finger [this message]

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=97422981-e0ea-850f-beed-87dc6033cc0a@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=james.hughes@raspberrypi.org \
    --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