From: Kai-Heng Feng <kai.heng.feng@canonical.com>
To: Tony Chuang <yhchuang@realtek.com>
Cc: "kvalo@codeaurora.org" <kvalo@codeaurora.org>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
"open list:REALTEK WIRELESS DRIVER (rtw88)"
<linux-wireless@vger.kernel.org>,
"open list:NETWORKING DRIVERS" <netdev@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Andy Huang <tehuang@realtek.com>
Subject: Re: [PATCH] rtw88: 8821c: Add RFE 2 support
Date: Wed, 5 Aug 2020 19:24:32 +0800 [thread overview]
Message-ID: <9330BBA5-158B-49F1-8B7C-C2733F358AC1@canonical.com> (raw)
In-Reply-To: <c0c336d806584361992d4b52665fbb82@realtek.com>
Hi Tony,
> On Aug 5, 2020, at 19:18, Tony Chuang <yhchuang@realtek.com> wrote:
>
>> 8821CE with RFE 2 isn't supported:
>> [ 12.404834] rtw_8821ce 0000:02:00.0: rfe 2 isn't supported
>> [ 12.404937] rtw_8821ce 0000:02:00.0: failed to setup chip efuse info
>> [ 12.404939] rtw_8821ce 0000:02:00.0: failed to setup chip information
>>
>
> NACK
>
> The RFE type 2 should be working with some additional fixes.
> Did you tested connecting to AP with BT paired?
No, I only tested WiFi.
> The antenna configuration is different with RFE type 0.
> I will ask someone else to fix them.
> Then the RFE type 2 modules can be supported.
Good to know that, I'll be patient and wait for a real fix.
Kai-Heng
>
> Yen-Hsuan
next prev parent reply other threads:[~2020-08-05 19:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 8:45 Kai-Heng Feng
2020-08-05 11:18 ` Tony Chuang
2020-08-05 11:24 ` Kai-Heng Feng [this message]
2021-01-07 6:38 ` Kai-Heng Feng
2021-02-02 6:29 ` Kalle Valo
2021-02-02 7:02 ` Larry Finger
2021-02-02 7:36 ` Kai-Heng Feng
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=9330BBA5-158B-49F1-8B7C-C2733F358AC1@canonical.com \
--to=kai.heng.feng@canonical.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tehuang@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
all inboxes | Powered by JetHome®