From: Gabriel Tisan <gabriel.tisan@gmail.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Ping-Ke Shih <pkshih@realtek.com>,
Nick Morrow <morrownr@gmail.com>,
"linux-wireless@vger.kernel.org"
<linux-wireless@vger.kernel.org>
Subject: Re: rtw88: rtw8822cu (LM842) on Raspi4 -> driver get stucked while sending data
Date: Tue, 16 Apr 2024 18:25:45 +0200 [thread overview]
Message-ID: <CAD9ZU8CX-zC=mA-mE_B1ZGa2PCDwiW6qSWFhwvy7wMhu=MMNyA@mail.gmail.com> (raw)
In-Reply-To: <fe9d13fd-bf13-4c59-98a7-68fd20d97978@lwfinger.net>
> > To be sure, does anyone tested this driver in AP mode for 8822cu ?
>
> I have no idea if AP mode works for the rtw8822bu. The vendor driver for this
> device is available at https://github.com/RinCat/RTL88x2BU-Linux-Driver or
> https://github.com/morrownr/88x2bu-20210702.
>
> There is a problem with the wireless-next kernel and my rtw88 github repo in
> that device 0bda:c82c is listed as active for both rtw8822cu and rtw8821cu -
> certainly a mistake.
The problem is also in mainline, was introduced by Nick Morrow with this commit:
wifi: rtw88: Add missing VID/PIDs for 8811CU and 8821CU
Maybe he has a reason.
He told me to check https://github.com/morrownr/8821cu-20210916
even if I use a RTL8822CU chipset.
I checked https://github.com/lwfinger/rtw88 regarding AP mode for rtw8822cu
and I get the same problems like in the inline driver for kernel 6.6
prev parent reply other threads:[~2024-04-16 16:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 14:49 rtw88: rtw8822cu (LM842) on Raspi4 -> driver get stucked while sending data Gabriel Tisan
2024-04-12 17:19 ` Nick Morrow
2024-04-15 1:19 ` Ping-Ke Shih
2024-04-15 8:53 ` Gabriel Tisan
2024-04-15 21:42 ` Larry Finger
2024-04-16 16:25 ` Gabriel Tisan [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='CAD9ZU8CX-zC=mA-mE_B1ZGa2PCDwiW6qSWFhwvy7wMhu=MMNyA@mail.gmail.com' \
--to=gabriel.tisan@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=morrownr@gmail.com \
--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 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 read-only IMAP folder(s) and NNTP newsgroup(s).