From: Andy Huang <tehuang@realtek.com>
To: "'Larry Finger'" <Larry.Finger@lwfinger.net>,
Kalle Valo <kvalo@codeaurora.org>
Cc: David Rubio <david.alejandro.rubio@gmail.com>,
Brian Norris <briannorris@chromium.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
Yan-Hsuan Chuang <tony0620emma@gmail.com>,
Kai-Heng Feng <kai.heng.feng@canonical.com>
Subject: RE: rtw88 / rtl_8821ce: rfe 2 is not supported
Date: Fri, 23 Oct 2020 03:13:38 +0000 [thread overview]
Message-ID: <d6fecd1e5d7c4ba7a84494a61946c33a@realtek.com> (raw)
In-Reply-To: <fae0b720-bc94-b380-baa0-08a3286fb2cf@lwfinger.net>
From: Larry Finger <larry.finger@gmail.com> On Behalf Of Larry Finger
>
> On 10/22/20 12:53 AM, Kalle Valo wrote:
> > Ok, I will drop the patch then. But it would be really nice to enable
> > even some level of support for rfe 2, can't we find some solution? Like
> > disabling 2.4 GHz band for that rfe or something?
>
> The E-mail from Realtek
> (https://marc.info/?l=linux-wireless&m=160255510004938&w=2) says that the
> patches are ready; however, they need to do some "verification". To me
> (without
> proof), that implies a regulatory problem, and it is better that we not enable
> rfe 2 without the official patches.
>
> I hope those patches will be forthcoming very soon.
>
> Larry
>
The verification is not related to regulatory. It is that our QA team tests the some
functionalities (performance, BT coex etc.) of RFE type 2. If the test run successfully,
the patch will be sent in the next 2 weeks.
Tzu-En
prev parent reply other threads:[~2020-10-23 3:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-11 16:13 rtw88 / rtl_8821ce: rfe 2 is not supported David Rubio
2020-10-12 18:12 ` Brian Norris
2020-10-13 2:11 ` Andy Huang
2020-10-13 2:37 ` Larry Finger
2020-10-16 18:42 ` David Rubio
2020-10-18 9:11 ` Kalle Valo
2020-10-18 22:51 ` David Rubio
2020-10-19 7:37 ` Kalle Valo
2020-10-19 17:10 ` Larry Finger
2020-10-19 17:42 ` David Rubio
2020-10-21 3:41 ` Andy Huang
2020-10-21 14:12 ` David Rubio
2020-10-22 5:53 ` Kalle Valo
2020-10-22 15:53 ` Larry Finger
2020-10-23 3:13 ` Andy Huang [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=d6fecd1e5d7c4ba7a84494a61946c33a@realtek.com \
--to=tehuang@realtek.com \
--cc=Larry.Finger@lwfinger.net \
--cc=briannorris@chromium.org \
--cc=david.alejandro.rubio@gmail.com \
--cc=kai.heng.feng@canonical.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=tony0620emma@gmail.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