Linux wireless drivers development
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: "wens@kernel.org" <wens@kernel.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"wireless-regdb@lists.infradead.org"
	<wireless-regdb@lists.infradead.org>
Subject: RE: [PATCH 1/4] wireless-regdb: Update regulatory info for Malaysia (MY) on 6GHz
Date: Wed, 5 Jun 2024 02:45:45 +0000	[thread overview]
Message-ID: <4e1b94e1ed9c47f09c3b6696961096b4@realtek.com> (raw)
In-Reply-To: <CAGb2v64YQ4nxHV0Dk8UGTYZt88pen__bf6Y-uRi5APZTE=sFVg@mail.gmail.com>

Chen-Yu Tsai <wens@kernel.org> wrote:
> 
> On Mon, Jun 3, 2024 at 2:06 PM Ping-Ke Shih <pkshih@realtek.com> wrote:
> 
> >         (5250 - 5330 @ 80), (24), DFS, AUTO-BW
> 
> Regulations say 5250 - 5350 at 1W with DFS and TPC required.
> Since Linux doesn't have TPC support [1], this rule should be removed.

Would you like to add an attribute 'TPC'? Before Linux or driver doesn't have
TPC support, we don't convert this entry into regulatory.bin. Afterward
Linux can support this, we only need to change conversion tool instead of
re-adding these entries.

> 
> >         (5490 - 5650 @ 160), (24), DFS
> 
> Regulations say 5470 - 5650 at 1W with DFS and TPC required.
> Since Linux doesn't have TPC support [1], this rule should be removed.
> 
> >         (5735 - 5835 @ 80), (24)
> 
> Regulations say 5735 - 5875 at 1W.
> 
> > +       (5925 - 6425 @ 320), (200 mW), NO-OUTDOOR
> 
> This part looks correct.
> 
> Could you update your patch to include these changes?
> Or send a separate patch following this one to update the existing rules?

I can. I plan to combine changes into this patch. 

Thanks
Ping-Ke 


  reply	other threads:[~2024-06-05  2:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-03  6:05 [PATCH 1/4] wireless-regdb: Update regulatory info for Malaysia (MY) on 6GHz Ping-Ke Shih
2024-06-03  6:09 ` [PATCH 2/4] wireless-regdb: Update regulatory info for Morocco (MA) " Ping-Ke Shih
2024-06-04  9:49   ` Chen-Yu Tsai
2024-06-03  6:09 ` [PATCH 3/4] wireless-regdb: Update regulatory info for Chile (CL) " Ping-Ke Shih
2024-06-04 10:09   ` Chen-Yu Tsai
2024-06-03  6:09 ` [PATCH 4/4] wireless-regdb: Update regulatory info for Mexico (MX) " Ping-Ke Shih
2024-06-04 10:34   ` Chen-Yu Tsai
2024-06-05  2:52     ` Ping-Ke Shih
2024-06-05  4:11       ` Chen-Yu Tsai
2024-06-04  9:45 ` [PATCH 1/4] wireless-regdb: Update regulatory info for Malaysia (MY) " Chen-Yu Tsai
2024-06-05  2:45   ` Ping-Ke Shih [this message]
2024-06-04  9:47 ` Chen-Yu Tsai
2024-06-06 14:49 ` Chen-Yu Tsai
2024-06-06 14:51   ` Chen-Yu Tsai

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=4e1b94e1ed9c47f09c3b6696961096b4@realtek.com \
    --to=pkshih@realtek.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=wens@kernel.org \
    --cc=wireless-regdb@lists.infradead.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