From: Andy Huang <tehuang@realtek.com>
To: "'Brian Norris'" <briannorris@chromium.org>,
David Rubio <david.alejandro.rubio@gmail.com>
Cc: 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: Tue, 13 Oct 2020 02:11:28 +0000 [thread overview]
Message-ID: <362f154dff1b4d6f88503af813eae406@realtek.com> (raw)
In-Reply-To: <CA+ASDXO75rYv29YvK=0zUkB494DsA_WA+n3UttRiko2awzUkOw@mail.gmail.com>
The support for RFE type 2 of 8821ce, the patches are ready, but we need to do some verifications. After the verification it will be upload.
Tzu-En
-----Original Message-----
From: Brian Norris <briannorris@chromium.org>
Sent: Tuesday, October 13, 2020 2:13 AM
To: David Rubio <david.alejandro.rubio@gmail.com>
Cc: 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
On Sun, Oct 11, 2020 at 9:13 AM David Rubio <david.alejandro.rubio@gmail.com> wrote:
> Oct 11 12:20:39 youmu kernel: rtw_8821ce 0000:02:00.0: rfe 2 isn't
> supported
I'm not sure anything changed since the last time this came up:
https://lore.kernel.org/linux-wireless/c0c336d806584361992d4b52665fbb82@realtek.com/
I think this needs somebody from Realtek to look, or else ignore the objections and merge the sub-optimal (trivial) patch. I'm not sure of the ramifications of doing the latter.
Brian
------Please consider the environment before printing this e-mail.
next prev parent reply other threads:[~2020-10-13 2:42 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 [this message]
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
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=362f154dff1b4d6f88503af813eae406@realtek.com \
--to=tehuang@realtek.com \
--cc=briannorris@chromium.org \
--cc=david.alejandro.rubio@gmail.com \
--cc=kai.heng.feng@canonical.com \
--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;
as well as URLs for NNTP newsgroup(s).