From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Viacheslav <adeep@lexina.in>
Cc: Giulio Benetti <giulio.benetti@benettiengineering.com>,
"buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH v1] package/rtl8822cs bump driver version to latest
Date: Thu, 11 Jul 2024 09:59:15 +0200 [thread overview]
Message-ID: <20240711095915.6e0c9473@windsurf> (raw)
In-Reply-To: <fcdc3e33-99c6-488c-9231-4169b9201ce1@lexina.in>
Hello,
On Thu, 11 Jul 2024 08:56:42 +0300
Viacheslav <adeep@lexina.in> wrote:
> > One question: https://github.com/jethome-ru/rtl88x2cs says "** USE
> > RTW88 NOT THIS DRIVER **", so why are we using it? It seems like you
> > are the person maintaining this driver.
>
> RTW88 in-kernel driver has some problems at this moment: no working AP
> mode, wifi connection fails after 2-3 days, speed issues.
>
> The comment appeared when JetHub devices switched to the rtw88 driver.
> After we switched back to rtl88x2cs, I decided to keep the comment as
> motivation for development and to identify issues in rtw88.
> However, in production, we and some other boards use the rtl88x2cs
> driver and we maintain it as necessary.
>
> Since this question has been asked more than once, I decided to modify
> the description a bit. Now that alarming message will no longer be there)
Thanks for the clarification!
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-07-11 7:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 7:55 [Buildroot] [PATCH v1] package/rtl8822cs bump driver version to latest Viacheslav Bocharov via buildroot
2024-07-10 22:16 ` Thomas Petazzoni via buildroot
2024-07-11 5:56 ` Viacheslav via buildroot
2024-07-11 7:59 ` Thomas Petazzoni via buildroot [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=20240711095915.6e0c9473@windsurf \
--to=buildroot@buildroot.org \
--cc=adeep@lexina.in \
--cc=giulio.benetti@benettiengineering.com \
--cc=thomas.petazzoni@bootlin.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