public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alex G." <mr.nuke.me@gmail.com>
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
Subject: Re: Issues with rtw88_8821cu
Date: Fri, 3 Mar 2023 12:15:20 -0600	[thread overview]
Message-ID: <f9eff2cd-8afc-2124-4d02-ed998195c649@gmail.com> (raw)
In-Reply-To: <71855f0a-c8f4-9011-2edd-08e1a3eec782@lwfinger.net>

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

      reply	other threads:[~2023-03-03 18:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-01 21:57 Issues with rtw88_8821cu Alex G.
2023-03-03 12:51 ` Sascha Hauer
2023-03-03 15:53   ` Larry Finger
2023-03-03 18:15     ` Alex G. [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=f9eff2cd-8afc-2124-4d02-ed998195c649@gmail.com \
    --to=mr.nuke.me@gmail.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=neojou@gmail.com \
    --cc=pkshih@realtek.com \
    --cc=s.hauer@pengutronix.de \
    /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