From: Ping-Ke Shih <pkshih@realtek.com>
To: ZeroBeat <ZeroBeat@gmx.de>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Jes.Sorensen@gmail.com" <Jes.Sorensen@gmail.com>
Subject: RE: [PATCH] wifiwifi: Realtek: rtl8xxxu Add new device ID
Date: Fri, 8 Dec 2023 07:01:34 +0000 [thread overview]
Message-ID: <05c047080464492b8701f4e6a45c7cc2@realtek.com> (raw)
In-Reply-To: <a6a23ccf-b571-49bf-855b-4fba3501f09b@gmx.de>
> -----Original Message-----
> From: ZeroBeat <ZeroBeat@gmx.de>
> Sent: Friday, December 8, 2023 2:42 PM
> To: Ping-Ke Shih <pkshih@realtek.com>
> Cc: linux-wireless@vger.kernel.org; Jes.Sorensen@gmail.com
> Subject: Re: [PATCH] wifiwifi: Realtek: rtl8xxxu Add new device ID
>
> Thanks for this very helpful information.
> It is much better to understand than this ones:
> https://www.kernel.org/doc/html/v4.11/process/submitting-patches.html
> https://wireless.wiki.kernel.org/en/developers/Documentation/SubmittingPatches
The links describe more detail things, and I think you will need them if you
keep submitting more and more patches.
>
> At the moment I still have no idea why the TP-Link TL-WN8200ND(UN) v3.0 sometimes work and
> sometimes not (after its device idea has been added).
> But I have seen this behavior (rtl8188eu), before:
> https://bugzilla.kernel.org/show_bug.cgi?id=217205
> Confirmed and fixed, now.
Sorry, I don't have much time to look into the thread, but as the title mentioned IQK,
I would say IQK can affect _performance_, so keep distance of your usb WiFi stick
about 50cm far from AP, and check it can work stable.
>
> Maybe the problem of the rtl8192eu is similar to this - but I'm not sure, because
> I haven't fully understood the entire driver code (relationship driver code and
> firmware) yet.
>
You can search for a vendor driver somewhere like github, and then try if the
out-of-tree driver works to you. If so, compare their initialization and
set channel function basically.
next prev parent reply other threads:[~2023-12-08 7:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 8:46 [PATCH] wifiwifi: Realtek: rtl8xxxu Add new device ID ZeroBeat
2023-12-07 8:52 ` Ping-Ke Shih
2023-12-07 9:02 ` ZeroBeat
2023-12-07 9:38 ` ZeroBeat
2023-12-08 0:43 ` Ping-Ke Shih
2023-12-08 6:41 ` ZeroBeat
2023-12-08 7:01 ` Ping-Ke Shih [this message]
2023-12-08 7:37 ` ZeroBeat
-- strict thread matches above, loose matches on Subject: below --
2023-12-06 11:48 ZeroBeat
2023-12-07 0:17 ` Ping-Ke Shih
2023-12-07 11:51 ` ZeroBeat
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=05c047080464492b8701f4e6a45c7cc2@realtek.com \
--to=pkshih@realtek.com \
--cc=Jes.Sorensen@gmail.com \
--cc=ZeroBeat@gmx.de \
--cc=linux-wireless@vger.kernel.org \
/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