From: Zefir Kurtisi <zefir.kurtisi@neratec.com>
To: "Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>
Cc: Christian Lamparter <chunkeey@googlemail.com>,
kgiori@qca.qualcomm.com, ath9k-devel@lists.ath9k.org,
linux-wireless@vger.kernel.org
Subject: Re: [ath9k-devel] [RFC 5/6] ath9k: enable DFS pulse detection
Date: Thu, 06 Oct 2011 23:08:43 +0200 [thread overview]
Message-ID: <4E8E18DB.5070002@neratec.com> (raw)
In-Reply-To: <CAB=NE6XwNDc8v-qtQuQQZdh2ST-skpcZM7wqD32qHn3CgN-5Dw@mail.gmail.com>
On 06.10.2011 22:41, Luis R. Rodriguez wrote:
> On Thu, Oct 6, 2011 at 1:32 PM, Zefir Kurtisi<zefir.kurtisi@neratec.com> wrote:
>> As said above, disabling a driver's capability through a Kconfig option
>> should be enough (one ifdef per driver).
>
> OK cool.
>
>> Since regulatory compliance and open source by principle form a
>> gray-zone combination [2], testing for sure is essential to keep it more
>> white than black ;)
>>
>> [2] http://linuxwireless.org/en/developers/Regulatory/statement#Principles
>
> I actually do not think its grey now at all, we in fact IMHO have the
> best regulatory framework out there, while still ensuring freedoms.
>
> Luis
Sorry, of course it is, I was not specific enough.
I was just wondering if principle 3 generally would prevent us from
adding a Kconfig option to enable DFS for ath9k as long as it is not
certified (which is the only way to ensure to have a 'known compliant
usage') plus depending on mac80211 and hostapd.
Zefir
WARNING: multiple messages have this Message-ID (diff)
From: Zefir Kurtisi <zefir.kurtisi@neratec.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [RFC 5/6] ath9k: enable DFS pulse detection
Date: Thu, 06 Oct 2011 23:08:43 +0200 [thread overview]
Message-ID: <4E8E18DB.5070002@neratec.com> (raw)
In-Reply-To: <CAB=NE6XwNDc8v-qtQuQQZdh2ST-skpcZM7wqD32qHn3CgN-5Dw@mail.gmail.com>
On 06.10.2011 22:41, Luis R. Rodriguez wrote:
> On Thu, Oct 6, 2011 at 1:32 PM, Zefir Kurtisi<zefir.kurtisi@neratec.com> wrote:
>> As said above, disabling a driver's capability through a Kconfig option
>> should be enough (one ifdef per driver).
>
> OK cool.
>
>> Since regulatory compliance and open source by principle form a
>> gray-zone combination [2], testing for sure is essential to keep it more
>> white than black ;)
>>
>> [2] http://linuxwireless.org/en/developers/Regulatory/statement#Principles
>
> I actually do not think its grey now at all, we in fact IMHO have the
> best regulatory framework out there, while still ensuring freedoms.
>
> Luis
Sorry, of course it is, I was not specific enough.
I was just wondering if principle 3 generally would prevent us from
adding a Kconfig option to enable DFS for ath9k as long as it is not
certified (which is the only way to ensure to have a 'known compliant
usage') plus depending on mac80211 and hostapd.
Zefir
next prev parent reply other threads:[~2011-10-06 21:08 UTC|newest]
Thread overview: 110+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 10:29 [RFC 0/6] ath9k: DFS pattern detection Zefir Kurtisi
2011-10-03 10:29 ` [ath9k-devel] " Zefir Kurtisi
2011-10-03 10:29 ` [RFC 1/6] ath9k: add DFS statistics to debugfs Zefir Kurtisi
2011-10-03 10:29 ` [ath9k-devel] " Zefir Kurtisi
2011-10-03 18:14 ` Luis R. Rodriguez
2011-10-03 18:14 ` [ath9k-devel] " Luis R. Rodriguez
2011-10-04 8:27 ` Zefir Kurtisi
2011-10-04 8:27 ` [ath9k-devel] " Zefir Kurtisi
2011-10-03 10:29 ` [RFC 2/6] ath9k: add DFS debug flag Zefir Kurtisi
2011-10-03 10:29 ` [ath9k-devel] " Zefir Kurtisi
2011-10-03 18:15 ` Luis R. Rodriguez
2011-10-03 18:15 ` [ath9k-devel] " Luis R. Rodriguez
2011-10-04 8:31 ` Zefir Kurtisi
2011-10-04 8:31 ` [ath9k-devel] " Zefir Kurtisi
2011-10-04 9:40 ` Mohammed Shafi
2011-10-04 9:40 ` [ath9k-devel] " Mohammed Shafi
2011-10-03 10:29 ` [RFC 3/6] ath9k: initial radar pulse detection for DFS Zefir Kurtisi
2011-10-03 10:29 ` [ath9k-devel] " Zefir Kurtisi
2011-10-03 11:57 ` Adrian Chadd
2011-10-03 11:57 ` [ath9k-devel] " Adrian Chadd
2011-10-03 12:23 ` Zefir Kurtisi
2011-10-03 12:23 ` [ath9k-devel] " Zefir Kurtisi
2011-10-03 12:43 ` Adrian Chadd
2011-10-03 12:43 ` [ath9k-devel] " Adrian Chadd
2011-10-03 14:21 ` Zefir Kurtisi
2011-10-03 14:21 ` [ath9k-devel] " Zefir Kurtisi
2011-10-03 14:23 ` Adrian Chadd
2011-10-03 14:23 ` [ath9k-devel] " Adrian Chadd
2011-10-03 10:29 ` [RFC 4/6] ath9k: add DFS build parameter Zefir Kurtisi
2011-10-03 10:29 ` [ath9k-devel] " Zefir Kurtisi
2011-10-03 18:26 ` Luis R. Rodriguez
2011-10-03 18:26 ` [ath9k-devel] " Luis R. Rodriguez
2011-10-04 9:55 ` Zefir Kurtisi
2011-10-04 9:55 ` [ath9k-devel] " Zefir Kurtisi
2011-10-04 10:37 ` Felix Fietkau
2011-10-04 10:37 ` [ath9k-devel] " Felix Fietkau
2011-10-04 12:25 ` Adrian Chadd
2011-10-04 12:25 ` [ath9k-devel] " Adrian Chadd
2011-10-05 22:20 ` Luis R. Rodriguez
2011-10-05 22:20 ` [ath9k-devel] " Luis R. Rodriguez
2011-10-03 10:29 ` [RFC 5/6] ath9k: enable DFS pulse detection Zefir Kurtisi
2011-10-03 10:29 ` [ath9k-devel] " Zefir Kurtisi
2011-10-03 18:27 ` Luis R. Rodriguez
2011-10-03 18:27 ` [ath9k-devel] " Luis R. Rodriguez
2011-10-03 19:24 ` Christian Lamparter
2011-10-03 19:24 ` [ath9k-devel] " Christian Lamparter
2011-10-03 19:31 ` Luis R. Rodriguez
2011-10-03 19:31 ` [ath9k-devel] " Luis R. Rodriguez
2011-10-04 13:38 ` Christian Lamparter
2011-10-04 13:38 ` [ath9k-devel] " Christian Lamparter
2011-10-04 14:17 ` Zefir Kurtisi
2011-10-04 14:17 ` [ath9k-devel] " Zefir Kurtisi
2011-10-04 14:34 ` Adrian Chadd
2011-10-04 14:34 ` [ath9k-devel] " Adrian Chadd
2011-10-05 22:31 ` Luis R. Rodriguez
2011-10-05 22:31 ` [ath9k-devel] " Luis R. Rodriguez
2011-10-05 22:53 ` Peter Stuge
2011-10-05 23:02 ` Luis R. Rodriguez
2011-10-04 14:42 ` Christian Lamparter
2011-10-04 14:42 ` [ath9k-devel] " Christian Lamparter
2011-10-04 14:50 ` Adrian Chadd
2011-10-04 14:50 ` [ath9k-devel] " Adrian Chadd
2011-10-04 15:26 ` Christian Lamparter
2011-10-04 15:26 ` [ath9k-devel] " Christian Lamparter
2011-10-04 15:57 ` Adrian Chadd
2011-10-04 15:57 ` [ath9k-devel] " Adrian Chadd
2011-10-04 16:42 ` Christian Lamparter
2011-10-04 16:42 ` [ath9k-devel] " Christian Lamparter
2011-10-04 17:03 ` Adrian Chadd
2011-10-04 17:03 ` [ath9k-devel] " Adrian Chadd
2011-10-04 17:49 ` Christian Lamparter
2011-10-04 17:49 ` [ath9k-devel] " Christian Lamparter
2011-10-05 22:37 ` Luis R. Rodriguez
2011-10-05 22:37 ` [ath9k-devel] " Luis R. Rodriguez
2011-10-04 16:26 ` Zefir Kurtisi
2011-10-04 16:26 ` [ath9k-devel] " Zefir Kurtisi
2011-10-05 22:30 ` Luis R. Rodriguez
2011-10-05 22:30 ` [ath9k-devel] " Luis R. Rodriguez
2011-10-05 22:27 ` Luis R. Rodriguez
2011-10-05 22:27 ` Luis R. Rodriguez
2011-10-06 16:49 ` Christian Lamparter
2011-10-06 16:49 ` Christian Lamparter
2011-10-06 18:36 ` Luis R. Rodriguez
2011-10-06 18:36 ` Luis R. Rodriguez
2011-10-06 18:41 ` Luis R. Rodriguez
2011-10-06 18:41 ` Luis R. Rodriguez
2011-10-06 20:32 ` Zefir Kurtisi
2011-10-06 20:32 ` Zefir Kurtisi
2011-10-06 20:41 ` Luis R. Rodriguez
2011-10-06 20:41 ` Luis R. Rodriguez
2011-10-06 21:08 ` Zefir Kurtisi [this message]
2011-10-06 21:08 ` Zefir Kurtisi
2011-10-06 21:12 ` Luis R. Rodriguez
2011-10-06 21:12 ` Luis R. Rodriguez
2011-10-07 3:06 ` Adrian Chadd
2011-10-07 3:06 ` Adrian Chadd
2011-10-07 7:54 ` Luis R. Rodriguez
2011-10-07 7:54 ` Luis R. Rodriguez
2011-10-07 8:48 ` Zefir Kurtisi
2011-10-07 8:48 ` Zefir Kurtisi
2011-10-07 11:43 ` Adrian Chadd
2011-10-07 11:43 ` Adrian Chadd
2011-10-04 10:11 ` Zefir Kurtisi
2011-10-04 10:11 ` [ath9k-devel] " Zefir Kurtisi
2011-10-05 22:23 ` Luis R. Rodriguez
2011-10-05 22:23 ` [ath9k-devel] " Luis R. Rodriguez
2011-10-03 10:29 ` [RFC 6/6] ath9k: handle pulse data reported by DFS HW Zefir Kurtisi
2011-10-03 10:29 ` [ath9k-devel] " Zefir Kurtisi
2011-10-03 18:30 ` Luis R. Rodriguez
2011-10-03 18:30 ` [ath9k-devel] " Luis R. Rodriguez
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=4E8E18DB.5070002@neratec.com \
--to=zefir.kurtisi@neratec.com \
--cc=ath9k-devel@lists.ath9k.org \
--cc=chunkeey@googlemail.com \
--cc=kgiori@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rodrigue@qca.qualcomm.com \
/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.