Message-ID: <f9eff2cd-8afc-2124-4d02-ed998195c649@gmail.com>
Date:   Fri, 3 Mar 2023 12:15:20 -0600
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.7.2
Subject: Re: Issues with rtw88_8821cu
Content-Language: en-US
To:     Larry Finger <Larry.Finger@lwfinger.net>,
        Sascha Hauer <s.hauer@pengutronix.de>
Cc:     linux-wireless@vger.kernel.org, pkshih@realtek.com,
        neojou@gmail.com
References: <ee614c10-cfd7-de88-3f85-6448aaa17c5a@gmail.com>
 <20230303125147.GV32097@pengutronix.de>
 <71855f0a-c8f4-9011-2edd-08e1a3eec782@lwfinger.net>
From:   "Alex G." <mr.nuke.me@gmail.com>
In-Reply-To: <71855f0a-c8f4-9011-2edd-08e1a3eec782@lwfinger.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 3/3/23 09:53, Larry Finger wrote:
> On 3/3/23 06:51, Sascha Hauer wrote:
>> documentation for these chips and the downstream drivers are a complete
>> mess.
>>
>> Have you tried one of these drivers?
>>
>> https://github.com/lwfinger/rtw88
>> https://github.com/ulli-kroll/rtw88-usb
>>
>> The code is based on the kernel driver and the RTW88 USB support in the
>> kernel is derived from these drivers. There is a chance that I broke
>> something while porting it upstream and if yes it should be fairly easy
>> to sort out.
> 
> My repo is based on code from the wireless-next repo, thus any upstream 
> error will also be in it.
> 

I've had similar results with both repos. ulli-kroll's was a bit weird, 
as I had to use an older kernel -- but I saw the same issue with 2.4GHz 
channels, as well as the occasional USB issues.

Alex