From: Seth Forshee <seth.forshee@canonical.com>
To: Michael Green <green@qti.qualcomm.com>
Cc: Faisal Wiryasantika <faisal.wiryasantika@gmail.com>,
"wireless-regdb@lists.infradead.org"
<wireless-regdb@lists.infradead.org>
Subject: Re: [wireless-regdb] wireless-regdb: add Short Range Devices (SRD) for Qatar
Date: Tue, 1 May 2018 13:51:07 -0500 [thread overview]
Message-ID: <20180501185107.GL3502@ubuntu-xps13> (raw)
In-Reply-To: <5e5dddecb6a64a75adef06e6481bb2ed@NASANEXM01E.na.qualcomm.com>
On Wed, Apr 25, 2018 at 03:48:44PM +0000, Michael Green wrote:
> Faisal, Seth,
>
> a) DFS:
> Qatar specifies EN302 502 for their upper band and that spec states to apply radar detection in 5725-5850 (but not 5850-5875). Rather than create a more complicated definition, I propose we leave the patch as it currently is. Just means the last channel will also have radar detection enabled. If you want to review that spec, just google "EN 302 502". You will find latest V2.0.8 or V2.1.1 (both have same DFS rules).
>
> (5725 - 5875 @ 80), (50 mW), NO-OUTDOOR, DFS
>
>
> b) Power Limits:
> I encourage the use of the higher power limits per the previously shared CRA Confirmation doc. They did not yet get around to updating their website with these latest rules. But in my opinion, this document is an unequivocal confirmation of what the current rules are. The attached doc states the date, the authority, the specs and the limits. The web site has outdated information.
>
> I propose the patch be released per attached CRA confirmation doc:
>
> (2400 - 2483.5 @ 40), (100 mW), NO-OUTDOOR
> (5150 - 5250 @ 80), (200 mW), NO-OUTDOOR, AUTO-BW
> (5250 - 5350 @ 80), (200 mW), NO-OUTDOOR, DFS, AUTO-BW
> (5470 - 5725 @ 160), (100 mW), NO-OUTDOOR, DFS
> (5725 - 5875 @ 80), (100 mW), NO-OUTDOOR, DFS
> (57000 - 66000 @ 2160), (40), NO-OUTDOOR
Thanks for the information. I think this matches what I had except where
I had cut the power limits in half because I suspected TPC was required
(5250-5350, 5470-5725, and 5725-5875 MHz based on EN 301 893 and EN 302
502). Is TPC not required in these ranges?
Thanks,
Seth
>
> Please send comments if any, since customer is waiting for updated definition to propagate as soon as possible.
>
>
> Thanks,
>
> Michael Green
>
>
> -----Original Message-----
> From: wireless-regdb [mailto:wireless-regdb-bounces@lists.infradead.org] On Behalf Of Faisal Wiryasantika
> Sent: Sunday, April 08, 2018 4:29 AM
> To: Seth Forshee <mailto:seth.forshee@canonical.com>
> Cc: mailto:wireless-regdb@lists.infradead.org
> Subject: Re: [wireless-regdb] wireless-regdb: add Short Range Devices (SRD) for Qatar
>
> Hello Seth,
>
> Everything looks fine for me...except why you set U-NII-3 band 4 have DFS?
> As far as I know the U-NII-3 band 4 doesn't have DFS requirement under ETSI rules.
>
>
> Best regards,
> Faisal Wiryasantika
>
>
>
> On Fri, Mar 30, 2018 at 4:09 PM, Seth Forshee <mailto:seth.forshee@canonical.com> wrote:
> > On Thu, Mar 22, 2018 at 05:26:12PM +0300, Faisal Wiryasantika wrote:
> >> Hello Seth,
> >>
> >> It's mentioned here:
> >> http://www.motc.gov.qa/sites/default/files/qatar_national_frequency_a
> >> llocation_table_qnfat_0.pdf
> >> - page 64.
> >
> > Okay, so this is what I've come up with based on all the information I
> > have:
> >
> > country QA: DFS-ETSI
> > (2400 - 2483.5 @ 40), (100 mW), NO-OUTDOOR
> > (5150 - 5250 @ 80), (200 mW), NO-OUTDOOR, AUTO-BW
> > (5250 - 5350 @ 80), (100 mW), NO-OUTDOOR, DFS, AUTO-BW
> > (5470 - 5725 @ 160), (50 mW), NO-OUTDOOR, DFS
> > (5725 - 5875 @ 80), (50 mW), NO-OUTDOOR, DFS
> > (57000 - 66000 @ 2160), (40), NO-OUTDOOR
> >
> > Explanations for the differences from what you suggested:
> >
> > - In the letter you provided all ranges are listed as indoor only.
> >
> > - The power limits you had on some of the ranges were higher than what
> > ware in the letter, so I have reduced them accordingly.
> >
> > - The letter says "with & without TPC" for some of the power limits, and
> > I'm honestly not sure what is meant by that. So I've cut the limits in
> > half for any ranges which require TPC as per the relevant ETSI
> > standards, since we don't have support for TPC.
> >
> > Let me know if this looks correct to you, and if so I'll send a patch.
> >
> > Thanks,
> > Seth
> >
> >
> >>
> >>
> >> Best regards,
> >> Faisal Wiryasantika
> >>
> >>
> >>
> >>
> >> On Thu, Mar 22, 2018 at 3:48 PM, Seth Forshee
> >> <mailto:seth.forshee@canonical.com> wrote:
> >> > On Tue, Mar 20, 2018 at 07:21:22PM +0300, Faisal Wiryasantika wrote:
> >> >> Dear Seth,
> >> >>
> >> >>
> >> >> diff --git a/dbA.txt b/dbB.txt
> >> >> index 990abf9..b28e654 100644
> >> >> --- a/dbA.txt
> >> >> +++ b/dbB.txt
> >> >> -country QA: DFS-JP
> >> >> - (2402 - 2482 @ 40), (20)
> >> >> - (5735 - 5835 @ 80), (30)
> >> >> +country QA: DFS-ETSI
> >> >> + (2402 - 2482 @ 40), (20)
> >> >> + (5150 - 5250 @ 80), (200 mW), NO-OUTDOOR, AUTO-BW
> >> >> + (5250 - 5350 @ 80), (200 mW), NO-OUTDOOR, DFS, AUTO-BW
> >> >> + (5470 - 5725 @ 160), (200 mW), DFS
> >> >> + # Short Range Devices (SRD) (ETSI EN 300 440)
> >> >> + (5725 - 5875 @ 80), (100 mW), NO-OUTDOOR
> >> >> + # 60 GHz band channels 1-4, ref: Etsi En 302 567
> >> >> + (57000 - 66000 @ 2160), (40)
> >> >>
> >> >>
> >> >> Best regards,
> >> >> Faisal Wiryasantika
> >> >
> >> > Thanks for all the information. I'm still a bit hesitant because
> >> > documents I find on http://cra.gov.qa/ either do not show these
> >> > updates or else they are documents for proposed updates. The letter
> >> > you supplied seems to indicate that the changes may have just
> >> > recently gone into effect, however I can't find any public information which says the same.
> >> > Do you know why the public documents have not yet been updated?
> >> >
> >> > Thanks,
> >> > Seth
>
> _______________________________________________
> wireless-regdb mailing list
> mailto:wireless-regdb@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/wireless-regdb
_______________________________________________
wireless-regdb mailing list
wireless-regdb@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/wireless-regdb
next prev parent reply other threads:[~2018-05-01 18:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-29 9:10 [wireless-regdb] wireless-regdb: add Short Range Devices (SRD) for Qatar Faisal Abu Rayhan
2018-03-06 9:09 ` Seth Forshee
2018-03-13 8:12 ` Faisal Wiryasantika
2018-03-18 9:44 ` Faisal Wiryasantika
2018-03-20 16:21 ` Faisal Wiryasantika
2018-03-22 12:48 ` Seth Forshee
2018-03-22 14:26 ` Faisal Wiryasantika
2018-03-30 13:09 ` Seth Forshee
2018-04-08 8:29 ` Faisal Wiryasantika
[not found] ` <f472ada2fe9a4fbb931984f26d6f5603@NASANEXM01E.na.qualcomm.com>
2018-04-25 15:48 ` Michael Green
2018-05-01 18:51 ` Seth Forshee [this message]
2018-05-01 19:28 ` Michael Green
2018-05-01 20:16 ` [wireless-regdb] [PATCH] wireless-regdb: Update rules for QA and add 5 GHz and 60 GHz rules Seth Forshee
2018-05-07 4:30 ` Faisal Wiryasantika
2018-05-08 15:30 ` Seth Forshee
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=20180501185107.GL3502@ubuntu-xps13 \
--to=seth.forshee@canonical.com \
--cc=faisal.wiryasantika@gmail.com \
--cc=green@qti.qualcomm.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 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.