From: Kalle Valo <kvalo@codeaurora.org>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: David Rubio <david.alejandro.rubio@gmail.com>,
Andy Huang <tehuang@realtek.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: Thu, 22 Oct 2020 08:53:29 +0300 [thread overview]
Message-ID: <87a6we7qna.fsf@codeaurora.org> (raw)
In-Reply-To: <87bc4553-7f17-0c23-50c8-2b413de9f7b8@lwfinger.net> (Larry Finger's message of "Mon, 19 Oct 2020 12:10:50 -0500")
Larry Finger <Larry.Finger@lwfinger.net> writes:
> On 10/18/20 4:11 AM, Kalle Valo wrote:
>> David Rubio <david.alejandro.rubio@gmail.com> writes:
>>
>>>>
>>> https://lore.kernel.org/linux-wireless/c0c336d806584361992d4b52665fbb82@realtek.com/
>>>
>>> I tested that patch. Works fine for me for wifi, but I can't test BT
>>> to be sure it works 100%. Most people will be fine with just wifi
>>> though, I guess, considering the objections were mostly about BT (I
>>> understood -from the objection- that connecting to a AP when having a
>>> BT device paired breaks?)
>>
>> If the patch helps people to get wifi working we should take it, BT coex
>> issues can be fixed in followup patches. IIRC there has been multiple
>> reports about this so I'm leaning towards taking the patch to v5.11.
>>
>> I changed the patch to New state and my plan is to take it to
>> wireless-drivers-next once the tree opens:
>>
>> https://patchwork.kernel.org/project/linux-wireless/patch/20200805084559.30092-1-kai.heng.feng@canonical.com/
>
> Kalle,
>
> I had generated and applied that trivial patch to my GitHub repo with
> the rtw88 drivers a couple of months ago. Yes, it does get the user
> past the initialization check; however, wifi performance is abysmal
> according the the users of the repo. It seems that the antenna
> selection of rfe 2 models affects wifi as well as BT. Applying this
> patch will get wifi running; however, the users will need to be within
> 1 m of the AP for it to work! I do not have an RTL8821CE chip, thus I
> have not tested myself.
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?
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2020-10-22 5:53 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 [this message]
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=87a6we7qna.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=Larry.Finger@lwfinger.net \
--cc=briannorris@chromium.org \
--cc=david.alejandro.rubio@gmail.com \
--cc=kai.heng.feng@canonical.com \
--cc=linux-wireless@vger.kernel.org \
--cc=tehuang@realtek.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.