Dear all,
I am experimenting a bit with Wi-Fi Direct on top of the ath9k driver and I
am wondering if it is possible to operate at the same moment, on the same
IEEE802.11n module, a software AP for an infrastructure Wi-Fi network (e.g.
by using hostapd) and a soft AP for a Wi-Fi Direct link.
As
--
>> De : linux-wireless-ow...@vger.kernel.org [mailto:linux-wireless-
>> ow...@vger.kernel.org] De la part de Adrien Decostre
>> Envoyé : lundi 27 octobre 2014 19:24
>> À : Zefir Kurtisi
>> Cc : linux-wirel...@vger.kernel.org; ath9k-devel@lists.ath9k.org
>> Objet : Re:
FS channel X - assuming that one did a CAC already,
> there should be no radar device around). The certification requirements leave
> enough room for interpreting those supplemental results in one way or another.
>
>
> Cheers,
> Zefir
>
> On 10/27/2014 07:23 PM, Adrien Decostre
EN 300 328 v1.8.1. I mean, is the same pulse detector
algorithm used for DFS and for the adaptivity tests on channels 36 to
48?
Many thanks in advance for your answer.
Best regards
Adrien
On Mon, Oct 27, 2014 at 3:50 PM, Zefir Kurtisi
wrote:
> On 10/27/2014 03:18 PM, Adrien Decostre wr
platform. Is this a right statement?
What about the CONFIG_ATH9K_DFS_CERTIFIED build options? Do we need it
to enable the detection of 0.5usec. pulses?
Thanks in advance for your answer.
Best regards
Adrien
On Mon, Oct 27, 2014 at 11:43 AM, Zefir Kurtisi
wrote:
> On 10/24/2014 05:23 PM, Adr
Dear all,
I am looking for information about the compliancy of the ath9k driver to
the EN 300 328 ETSI regulation.
Would someone know if ath9k has already been tested for this regulation?
Is it needed to enable any specific flag in ath9k to guarantee compliancy
to the adaptivity tests describe
regards
On Tue, Jun 3, 2014 at 4:49 PM, Sujith Manoharan wrote:
> Adrien Decostre wrote:
> > I have read that a new ETSI regulation (EN 300 328 v.1.8.1) will become
> > mandatory from 31-12-2014 onwards.
> >
> > I am wondering if the current ath9k driver is alread
Dear all,
I have read that a new ETSI regulation (EN 300 328 v.1.8.1) will become
mandatory from 31-12-2014 onwards.
I am wondering if the current ath9k driver is already compliant with this
new regulation?
Are the patches provided by Sujith Manoharan (“ath9k: Fix regulatory
compliance” http:/
Dear all,
We are currently doing some tests to retrieve the channel busy time,
Rx time and Tx time from the ath9k driver (these tests have been done
with the version 3.0.0). For this purpose, we started our
implementation from the initial ACS algorithm implementation provided
at https://github.com
Peter, Adrian,
Thanks a lot for these fast answers and important precisions about this
calibration issue.
Best regards
On Fri, Apr 15, 2011 at 4:53 PM, Peter Stuge wrote:
> Adrien Decostre wrote:
> > Would it be more acceptable by regulatory agencies to specify the
> > reg_dom
Adrian, Peter and Luis,
Thanks for your answers.
Just 1 more question for curiosity.
Would it be more acceptable by regulatory agencies to specify the reg_domain
to use when loading the driver?
For example, in "ath_reg_init", the reg_domain would be hard-coded (this was
just a quick test to see
Hello all,
I am quite new to the ath9k driver and I am currently trying to use this
driver for an access point on the 5GHz band.
The problem is that my card has a regulation domain set to WORA_WORLD 0x6A
which prevents the card to do active probing on any 5GHz channel. I tried
setting different
12 matches
Mail list logo
