From: Larry Finger <Larry.Finger@lwfinger.net>
To: James <bjlockie@lockie.ca>, Pkshih <pkshih@realtek.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: USB for rtw89 driver?
Date: Mon, 29 Nov 2021 15:42:55 -0600 [thread overview]
Message-ID: <917dde5b-36c7-a079-6dc1-7441a2f90745@lwfinger.net> (raw)
In-Reply-To: <3fef8020-a496-41e3-8974-4d16ff4551b6@lockie.ca>
On 11/29/21 08:24, James wrote:
>
>>> Does anyone know if the proprietary driver works on the Raspberry Pi4B
>>> (Arm)?
>>
>> Don't have a proprietary driver neither.
>
> Dlink seems to have added USB support.
> I assumed that is proprietary but I guess that is only x86.
>
> https://support.dlink.com/ProductInfo.aspx?m=DWA-181-US
>
> There is also an open source USB driver on github but I don't think it is getting fixes like the lfinger github one.
> https://github.com/neojou/rtw89-usb
The D-Link driver is for the rtl8822bu, not an rtl8852au. That would make it for
rtw88, not rtw89. BTW, it will not compile under kernel 5.16.0-rc3, but the
fixes would be minor.
That driver is the usual collection of junk code published by the Realtek USB
group for years. That code base is used to generate drivers for Windows, Linux,
and FreeBSD.
A group is currently modifying the rtl8188eu driver in staging to convert it
into reasonable Linux shape. This one would take the same effort to make it
suitable.
The basic USB driver in the neojou repo should work, but I do not have an
rtl8852au device.
Larry
next prev parent reply other threads:[~2021-11-29 22:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-27 22:22 USB for rtw89 driver? James
2021-11-29 8:52 ` Pkshih
2021-11-29 14:24 ` James
2021-11-29 21:42 ` Larry Finger [this message]
2021-11-29 22:22 ` James
2021-11-29 23:37 ` James
2021-11-30 1:44 ` Larry Finger
2021-11-30 3:10 ` James
2021-11-30 1:16 ` Larry Finger
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=917dde5b-36c7-a079-6dc1-7441a2f90745@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=bjlockie@lockie.ca \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.com \
/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.