From: Zefir Kurtisi <zefir.kurtisi@neratec.com>
To: Helmut Schaa <helmut.schaa@googlemail.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: DFS CAC time
Date: Fri, 19 Dec 2014 12:27:08 +0100 [thread overview]
Message-ID: <54940B8C.5070801@neratec.com> (raw)
In-Reply-To: <CAGXE3d8Uv01qjfvRQkMr1w_5wB6XKpC7d2VOR3UG0DMPHk6r9A@mail.gmail.com>
On 12/18/2014 05:21 PM, Helmut Schaa wrote:
> Hi,
>
> [...]
>
> So, every channel has a CAC time of 60 seconds.
>
> Checking version 1.7.2 of the ETSI regulation indicates that we might
> need some modifications to cfg80211:
>
> From [1] page 79:
>
> "NOTE 1: For channels whose nominal bandwidth falls completely or
> partly within the
> band 5 600 MHz to 5 650 MHz, the Channel Availability Check Time shall be
> 10 minutes.
> NOTE 2: For channels whose nominal bandwidth falls completely or
> partly within the
> band 5 600 MHz to 5 650 MHz, the Off-Channel CAC Time shall be within the
> range 1 hour to 24 hours."
>
> So, for these channels we should select a longer initial CAC time.
>
> Is anyone aware of this issue?
>
> Thanks,
> Helmut
>
>
> [1] http://www.etsi.org/deliver/etsi_en/301800_301899/301893/01.07.02_20/en_301893v010702a.pdf
> --
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).
They should simply be disabled, either at mac layer, or at least in ath/regd.c.
Cheers,
Zefir
next prev parent reply other threads:[~2014-12-19 11:37 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 [this message]
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
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=54940B8C.5070801@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 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.