From: Simon Wunderlich <sw@simonwunderlich.de>
To: Janusz Dziedzic <janusz.dziedzic@tieto.com>
Cc: linux-wireless@vger.kernel.org, johannes@sipsolutions.net
Subject: Re: [PATCH v3 4/4] cfg80211: DFS use 10 minutes CAC when weather channels
Date: Tue, 26 Nov 2013 15:50:14 +0100 [thread overview]
Message-ID: <201311261550.14953.sw@simonwunderlich.de> (raw)
In-Reply-To: <1385409372-4229-4-git-send-email-janusz.dziedzic@tieto.com>
> When nominal bandwidth falls completely or partly
> within the band 5600MHz to 5650MHz the CAC time shall
> be 10 minutes.
> This is ETSI requirement. FCC forbids weather channels usage.
Although it is correct to handle that with longer times and all, I don't think
we should enable weather channels at all, not even for ETSI. Unlike "normal"
channels, it requires 99.99% detection rate in CAC, which is (I think)
practically impossible.
I guess we need ath9k (or other drivers, maybe ath10k too) to disallow CAC on
these channels, if we know that the drivers can do it? Although I don't think
it's technically possible ...
Cheers,
Simon
next prev parent reply other threads:[~2013-11-26 14:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 19:56 [PATCH v3 1/4] cfg80211: add reg_get_dfs_region() Janusz Dziedzic
2013-11-25 19:56 ` [PATCH v3 2/4] cfg80211: DFS check dfs_region before usage Janusz Dziedzic
2013-11-25 19:56 ` [PATCH v3 3/4] cfg80211/mac80211: DFS pass CAC time as a parameter Janusz Dziedzic
2013-11-25 19:56 ` [PATCH v3 4/4] cfg80211: DFS use 10 minutes CAC when weather channels Janusz Dziedzic
2013-11-26 14:50 ` Simon Wunderlich [this message]
2013-11-26 20:19 ` Janusz Dziedzic
2013-11-26 20:39 ` Johannes Berg
2013-11-27 6:16 ` Janusz Dziedzic
2013-12-02 14:43 ` Johannes Berg
2013-12-03 12:54 ` [PATCH v3 1/4] cfg80211: add reg_get_dfs_region() Johannes Berg
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=201311261550.14953.sw@simonwunderlich.de \
--to=sw@simonwunderlich.de \
--cc=janusz.dziedzic@tieto.com \
--cc=johannes@sipsolutions.net \
--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