public inbox for wireless-regdb@lists.infradead.org
 help / color / mirror / Atom feed
From: Seth Forshee <sforshee@kernel.org>
To: Mohammed Ismail <m.ismael@gmail.com>
Cc: wireless-regdb@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [wireless-regdb] wireless-regdb: Update regulatory rules for Egypt (EG) on 5GHz
Date: Tue, 11 Jul 2023 10:16:17 -0500	[thread overview]
Message-ID: <ZK1yQciEefUp1vUt@do-x1extreme> (raw)
In-Reply-To: <CAKOr0YRy=14-0QHBJNPWK3LHNMY01eVZnGL8nToP1271vJwz+g@mail.gmail.com>

Please be sure that you do not drop the mailing lists when you reply.

On Tue, Jul 04, 2023 at 08:07:35PM +0300, Mohammed Ismail wrote:
> Dear  Seth,
> Thank you for your swift reply, and I am sorry for that huge delay in my
> response.
> 
> You are right that there is no power information in the documents I
> provided.
> 
> But the power allowed for 5150-5350 is 200mw
> and your rules defined (5250 - 5350 @ 80), (*20*), DFS, AUTO-BW,
> wmmrule=ETSI

This is because 5250-5350 MHz requires TPC. Linux does not support TPC, so
we must reduce the max EIRP by half to 100 mW in this range.

I'll send a patch soon.

Thanks,
Seth

> 
> 
> thank you for your cooperation
> 
> best regards.
> Muhammad
> 
> On Thu, Jun 1, 2023 at 4:21 PM Seth Forshee <sforshee@kernel.org> wrote:
> 
> > On Thu, May 25, 2023 at 12:04:00PM +0300, Mohammed Ismail wrote:
> > > Hi
> > > Current rules are
> > >
> > > country EG: DFS-ETSI
> > >         (2402 - 2483 @ 40), (N/A, 20), (N/A)
> > >         (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
> > >         (5250 - 5330 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
> > >
> > > it is outdated , here are the updated information
> > >
> > >
> > https://www.tra.gov.eg/wp-content/uploads/2021/11/EGY-NTRA-June21-NFAT.pdf
> > >
> > >
> > https://www.tra.gov.eg/wp-content/uploads/2021/11/EGY-NTRA-June21-Chart.pdf
> >
> > Thanks for the links, however they don't seem to contain the information
> > about power limits, etc. that we need to update the database. I found
> > this document:
> >
> >
> > https://www.tra.gov.eg/wp-content/uploads/2022/03/EGY-NTRA-March-2022-SRD_English_Final.pdf
> >
> > From this I think the correct rules are:
> >
> > country EG: DFS-ETSI
> >         (2402 - 2483.5 @ 40), (20)
> >         (5150 - 5250 @ 80), (23), AUTO-BW, wmmrule=ETSI
> >         (5250 - 5350 @ 80), (20), DFS, AUTO-BW, wmmrule=ETSI
> >         (57000 - 66000 @ 2160), (40)
> >
> > If this looks correct to you, I'll send a patch.
> >
> > Thanks,
> > Seth
> >

_______________________________________________
wireless-regdb mailing list
wireless-regdb@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/wireless-regdb

  parent reply	other threads:[~2023-07-11 15:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAKOr0YRiWtywH_hggMn0jFivS7GOp9huw+ib5Lz43BxWo5M7CA@mail.gmail.com>
2023-06-01 13:21 ` [wireless-regdb] wireless-regdb: Update regulatory rules for Egypt (EG) on 5GHz Seth Forshee
     [not found]   ` <CAKOr0YRy=14-0QHBJNPWK3LHNMY01eVZnGL8nToP1271vJwz+g@mail.gmail.com>
2023-07-11 15:16     ` Seth Forshee [this message]
2020-10-18 17:39 Raif Atef

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=ZK1yQciEefUp1vUt@do-x1extreme \
    --to=sforshee@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=m.ismael@gmail.com \
    --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