Received-SPF: pass (google.com: domain of linux-wireless+bounces-6404-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
Precedence: bulk
MIME-Version: 1.0
References: <CAD9ZU8Coc0r3AiWz+rA4eoXuDQBBCAMY0J4w5x-Pa1JEpbmdWA@mail.gmail.com>
 <CAFktD2cp5eXJufdQibxDPGvN2iMfMZKDOunFzxv0TBNLqcMAQg@mail.gmail.com>
 <c68a406361524b6888d973a1e428118b@realtek.com> <CAD9ZU8A8f-aJuH54e+93cZGTckOSu+rYKcnQr0mkc8eq56zedg@mail.gmail.com>
 <fe9d13fd-bf13-4c59-98a7-68fd20d97978@lwfinger.net>
In-Reply-To: <fe9d13fd-bf13-4c59-98a7-68fd20d97978@lwfinger.net>
From: Gabriel Tisan <gabriel.tisan@gmail.com>
Date: Tue, 16 Apr 2024 18:25:45 +0200
Message-ID: <CAD9ZU8CX-zC=mA-mE_B1ZGa2PCDwiW6qSWFhwvy7wMhu=MMNyA@mail.gmail.com>
Subject: Re: rtw88: rtw8822cu (LM842) on Raspi4 -> driver get stucked while
 sending data
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>
Content-Type: text/plain; charset="UTF-8"

> > 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