From: Johannes Berg <johannes@sipsolutions.net>
To: "Nicco Kunzmann (mail.ru)" <niccokunzmann@mail.ru>,
Wireless RegDB <wireless-regdb@lists.infradead.org>
Subject: Re: [wireless-regdb] EU Regulation on CAC time
Date: Wed, 21 Mar 2018 09:26:01 +0100 [thread overview]
Message-ID: <1521620761.2645.16.camel@sipsolutions.net> (raw)
In-Reply-To: <052a981b-c150-61f3-318a-0546b33192a9@mail.ru>
On Tue, 2018-03-20 at 23:48 +0100, Nicco Kunzmann (mail.ru) wrote:
> Dear list subscribers,
>
> I was reading through the db.txt file.
> I did not see the CAC time for the country I live in, Germany.
> According to [1], DFS frequencies are described.
> However, I also read EN301893 [2] which is referenced by [1].
> EN301893, page 104, Table D.1 describes the CAC times and handles the
> range 5600MHz to 5650MHz specially with extended CAC times.
> Now, I read the db.txt file [3], section DE.
> There, I can not find the 5600MHz to 5650MHz range specified. Nor am I
> able to locate information about the DFS-ETSI region.
> I guess, the information can be inherited from somewhere.
>
> Could you help me understand where the information for EN301893/ the
> dfs_region "DFS-ETSI" is described?
>
> I checked "wireless-regdb"[4] and "crda"[5] and could not find it.
The CAC times are currently hard-coded in the kernel. The new
regulatory db framework (loading it as a firmware file) has the ability
to provision it through there, but the wireless-regdb db.txt, parser &
generator doesn't support it yet.
CRDA is more or less dead - still used, but will not get any future
work.
johannes
_______________________________________________
wireless-regdb mailing list
wireless-regdb@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/wireless-regdb
prev parent reply other threads:[~2018-03-21 8:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 22:48 [wireless-regdb] EU Regulation on CAC time Nicco Kunzmann (mail.ru)
2018-03-21 8:26 ` Johannes Berg [this message]
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=1521620761.2645.16.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=niccokunzmann@mail.ru \
--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.