From: "David R. Bergstein" <david.r.bergstein@gmail.com>
To: Tony Chuang <yhchuang@realtek.com>
Cc: Pkshih <pkshih@realtek.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Realtek r8822be kernel module does not negotiate 802.11ac connection
Date: Thu, 28 Feb 2019 21:32:03 -0500 [thread overview]
Message-ID: <b0518665-d5ca-7c94-9808-7cc0cf565814@gmail.com> (raw)
In-Reply-To: <F7CD281DE3E379468C6D07993EA72F84D17AF74C@RTITMBSVM04.realtek.com.tw>
Tony,
Thanks for your response. Can you advise as to the availability of the
new rtw88 driver? As it appears to be under development, I could not
locate a copy of the code for local compilation.
Sincerely,
David R. Bergstein
On 2/27/19 5:23 AM, Tony Chuang wrote:
>> This message is in regard to a bug I have open on bugs.launchpad.net, 1813372,
>> linked below. This issue, originally identified in an Ubuntu kernel, has been
>> duplicated in the most current mainline kernel, 5.0-rc8, and is in regard to
>> problems attaining a wireless connection at 802.11ac speeds.
>>
>> https://bugs.launchpad.net/bugs/1813372
>>
>> At your earliest convenience, please see the bug report above, and advise if a fix
>> will be available for the r8822be kernel module.
>>
>> Sincerely,
>>
>> David R. Bergstein
>>
> Hi,
>
> If it's possible I will suggest that you can use the new driver "rtw88" being
> reviewed now. rtw88 is better supported by Realtek and has significant
> improvement in contrast to r8822be. And also it is aim to better support
> 802.11ac series ICs, so it may help resolve your problem about 802.11ac
> connection speeds.
> Thanks!
>
> Yan-Hsuan
>
next prev parent reply other threads:[~2019-03-01 2:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 4:09 David R. Bergstein
2019-02-27 10:23 ` Tony Chuang
2019-03-01 2:32 ` David R. Bergstein [this message]
2019-03-01 17:28 ` Larry Finger
2019-03-01 22:26 ` David R. Bergstein
2019-03-02 1:46 ` Larry Finger
2019-03-02 2:55 ` David R. Bergstein
2019-03-02 3:16 ` David R. Bergstein
2019-03-02 3:52 ` David R. Bergstein
2019-03-02 10:03 ` Arend Van Spriel
2019-03-04 2:34 ` Tony Chuang
2019-03-02 17:58 ` Larry Finger
2019-03-02 18:09 ` David R. Bergstein
2019-03-02 18:39 ` Larry Finger
2019-04-14 21:39 ` rtlwifi-new v0.6 and dkms failures David R. Bergstein
2019-04-16 21:19 ` David R. Bergstein
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=b0518665-d5ca-7c94-9808-7cc0cf565814@gmail.com \
--to=david.r.bergstein@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pkshih@realtek.com \
--cc=yhchuang@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
Powered by JetHome