Linux-Wireless Archive mirror
 help / color / mirror / Atom feed
From: Bitterblue Smith <rtl8821cerfe2@gmail.com>
To: Ping-Ke Shih <pkshih@realtek.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
	Stefan Lippers-Hollmann <s.l-h@gmx.de>,
	Christian Hewitt <chewitt@libreelec.tv>
Subject: Re: [PATCH v6 4/6] wifi: rtlwifi: Move code from rtl8192de to rtl8192d-common
Date: Tue, 23 Apr 2024 14:06:12 +0300	[thread overview]
Message-ID: <937ed41e-6915-426b-8098-01e95c8554c0@gmail.com> (raw)
In-Reply-To: <054791df5141422fb0f8220eaeb66ff3@realtek.com>

On 23/04/2024 03:48, Ping-Ke Shih wrote:
> Bitterblue Smith <rtl8821cerfe2@gmail.com> wrote:
>> On 22/04/2024 05:55, Ping-Ke Shih wrote:
>>> Bitterblue Smith <rtl8821cerfe2@gmail.com> wrote:
>>>> +++ b/drivers/net/wireless/realtek/rtlwifi/rtl8192d/main.c
>>>> @@ -0,0 +1,9 @@
>>>> +// SPDX-License-Identifier: GPL-2.0
>>>> +/* Copyright(c) 2009-2012  Realtek Corporation.*/
>>>> +
>>>> +#include "../wifi.h"
>>>> +#include <linux/module.h>
>>>> +
>>>> +MODULE_AUTHOR("Realtek WlanFAE <wlanfae@realtek.com>");
>>>> +MODULE_LICENSE("GPL");
>>>> +MODULE_DESCRIPTION("Realtek 8192D 802.11an common routines");
>>>
>>> Not sure why you emphasize '802.11an' instead of just '802.11n'.
>>>
>>>
>>
>> I saw somewhere a dual-band chip described as 802.11an.
>> It seemed like a good idea. Should I change it?
> 
> 
> I'm not sure what '802.11an' defines, but this old chip should not support that.
> Then, maybe '802.11an' here means '802.11a/802.11n', but I still don't know the
> relation with dual-band chip.
> 
> FYI:
> 802.11a: 5GHz band, CCK/OFDM
> 802.11b: 2GHz band, CCK
> 802.11g: 2GHz band, CCK/OFDM
> 802.11n: 2/5GHz bands, HT
> 

Ohh, right, there is probably something officially called
"802.11an". I will change it back then.

  reply	other threads:[~2024-04-23 11:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-19 13:34 [PATCH v6 0/6] wifi: rtlwifi: Move common code from rtl8192de to rtl8192d-common Bitterblue Smith
2024-04-19 13:35 ` [PATCH v6 1/6] wifi: rtlwifi: rtl8192de: Fix 5 GHz TX power Bitterblue Smith
2024-04-19 13:36 ` [PATCH v6 2/6] wifi: rtlwifi: rtl8192de: Fix low speed with WPA3-SAE Bitterblue Smith
2024-04-19 13:37 ` [PATCH v6 3/6] wifi: rtlwifi: rtl8192de: Fix endianness issue in RX path Bitterblue Smith
2024-04-19 13:37 ` [PATCH v6 4/6] wifi: rtlwifi: Move code from rtl8192de to rtl8192d-common Bitterblue Smith
2024-04-22  2:55   ` Ping-Ke Shih
2024-04-22 17:25     ` Bitterblue Smith
2024-04-23  0:48       ` Ping-Ke Shih
2024-04-23 11:06         ` Bitterblue Smith [this message]
2024-04-19 13:38 ` [PATCH v6 5/6] wifi: rtlwifi: Clean up rtl8192d-common a bit Bitterblue Smith
2024-04-22  3:13   ` Ping-Ke Shih
2024-04-22 17:18     ` Bitterblue Smith
2024-04-19 13:39 ` [PATCH v6 6/6] wifi: rtlwifi: Adjust rtl8192d-common for USB Bitterblue Smith
2024-04-22  3:39   ` Ping-Ke Shih
2024-04-22 17:13     ` Bitterblue Smith

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=937ed41e-6915-426b-8098-01e95c8554c0@gmail.com \
    --to=rtl8821cerfe2@gmail.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=chewitt@libreelec.tv \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pkshih@realtek.com \
    --cc=s.l-h@gmx.de \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).