All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mihai Moldovan <ionic@ionic.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] AR9280 DFS -- high latency
Date: Mon, 19 Aug 2013 15:36:54 +0200	[thread overview]
Message-ID: <52121F76.3020503@ionic.de> (raw)
In-Reply-To: <93A5C693-BBC6-4B75-9118-7818C66C94FC@gmail.com>

Hi Bruno,

* On 16.08.2013 05:59 PM, Bruno Alexandre Taraio dos Santos Antunes wrote:
> Could you or anybody in the mailing list please tell me what are the steps to enable DFS.

DFS has to be enabled on the kernel side and it's dependent on an option called
CFG80211_CERTIFICATION_ONUS which is only to be enabled iff your whole system is
"regulatory compliant" even with the options enabled by that (currently DFS only
for ath9k, I guess) option. Those additional options may or may not be
regulatory compliant for the time being.

This said, once CFG80211_CERTIFICATION_ONUS has been enabled and if your kernel
is recent enough (>= 3.10), you'll be able to enable DFS in the ath9k options
tree, the symbol for that is ATH9K_DFS_CERTIFIED.

Minding all of the above, I don't think OpenWrt has support for it... yet. Those
are fragile options when it comes to compliance and OpenWrt must make sure to be
regulatory compliant on a cross-device level, so hacks like that are likely
disabled for good for now and can only be turned on by manually configuring the
kernel.

This said, hostapd probably needs DFS support as well, and to the best of my
knowledge, only the git branch of hostapd has initial (read: incomplete) DFS
support. Again, I figure OpenWrt is packaging an older stable release version,
so using DFS may prove difficult.

Why do you even want to jump through all those hoops? It's probably not worth
it, at this stage of development. Also note the performance problems I encountered.

Best regards,


Mihai

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4506 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20130819/af54d8b7/attachment.bin 

  reply	other threads:[~2013-08-19 13:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-15  3:29 [ath9k-devel] AR9280 DFS -- high latency Mihai Moldovan
2013-08-16 15:59 ` Bruno Alexandre Taraio dos Santos Antunes
2013-08-19 13:36   ` Mihai Moldovan [this message]
2013-08-19 15:25     ` Adrian Chadd
2013-08-19 21:34       ` Mihai Moldovan

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=52121F76.3020503@ionic.de \
    --to=ionic@ionic.de \
    --cc=ath9k-devel@lists.ath9k.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.