From: Zefir Kurtisi <zefir.kurtisi@neratec.com>
To: Helmut Schaa <helmut.schaa@googlemail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: DFS CAC time
Date: Fri, 19 Dec 2014 16:56:36 +0100 [thread overview]
Message-ID: <54944AB4.7050208@neratec.com> (raw)
In-Reply-To: <CAGXE3d9ZubxEoeV+uD9GHJiAa7aB_NM87OfddNa4SC5CQkjNuA@mail.gmail.com>
On 12/19/2014 02:19 PM, Helmut Schaa wrote:
> Hi Zefir,
>
> On Fri, Dec 19, 2014 at 12:27 PM, Zefir Kurtisi
> <zefir.kurtisi@neratec.com> wrote:
>>
>> Hello Helmut,
>>
>> just forget about those aka 'weather channels' that require a pracitcally
>> impossible to achieve radar detection probability rate (99.99% during CAC, see
>> table D.5).
>
> Hmm, ok :)
>
> Would it make sense to mark these somehow in the wireless-regdb in a
> special way?
>
To reflect the fact that channels are available from regulatory's point of view
but not usable from driver's perspective, the correct way would be to
* set the correct CAC time in crda
* disable them in the driver internal regdb
In practice, that's an overhead to manage channels that we know will never be
available for WLAN master devices.
Cheers,
Zefir
prev parent reply other threads:[~2014-12-19 15:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-18 16:21 DFS CAC time Helmut Schaa
2014-12-19 11:27 ` Zefir Kurtisi
2014-12-19 12:28 ` Janusz Dziedzic
2014-12-19 13:18 ` Helmut Schaa
2014-12-20 10:27 ` YanBo
2014-12-19 13:19 ` Helmut Schaa
2014-12-19 15:56 ` Zefir Kurtisi [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=54944AB4.7050208@neratec.com \
--to=zefir.kurtisi@neratec.com \
--cc=helmut.schaa@googlemail.com \
--cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).