On Friday, November 04, 2011 04:05:49 Adrian Chadd wrote:
> I wonder if it thinks the air is busy and thus can't really TX
> anything, including beacons.
> What kind of interference is this?
Please keep in mind that all I need to do is to disable WPA on the first VAP
to make the driver send beaco
I wonder if it thinks the air is busy and thus can't really TX
anything, including beacons.
What kind of interference is this?
Adrian
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Zefir Kurtisi wrote:
> Just clarify whether you do not like the CONFIG_ prefix or the fact
> that it can't be enabled.
It's IMO always stupid to add dead code. No exceptions for
$random_authority_which_has_no_jurisdiction_for_billions_of_users.
//Peter
___
Hi,
> These pcap files were captured while VAP#1 was WPA encrypted and VPA#2 was
> unencrypted. An Apple notebook tried to connect to the router on VAP#1:
> apple-vap1.pcap -> captured packets on the notebook itself
> vap1_vpa2_nowpa.pcap -> captured packets from the router (wifi interface)
> mo
Hi Daniel,
On Fri, Nov 4, 2011 at 12:58 AM, Daniel Smith wrote:
> I recently upgraded to compat-wireless-3.1-rc8 from
> compat-wireless-2.6.39-1-sn and have discovered an interesting behavior.
> When in monitor mode I use the signal strength field reported in
> radiotap and with 3.1 I am now gett
I recently upgraded to compat-wireless-3.1-rc8 from
compat-wireless-2.6.39-1-sn and have discovered an interesting behavior.
When in monitor mode I use the signal strength field reported in
radiotap and with 3.1 I am now getting a range of values. The more
interesting ones are all the frames re
From: Ben Greear
Add interface address so it can be mapped to a local
interface. Add max-ampdu and mpdu-density.
Print out the tid->baw_size
Signed-off-by: Ben Greear
---
:100644 100644 1c269f5... 3d3b44f... M drivers/net/wireless/ath/ath9k/ath9k.h
:100644 100644 327aa28... 8e7e57c... M dri
On 2011-11-03 7:01 PM, Zefir Kurtisi wrote:
> Hi Felix,
>
> while I was waiting for your feedback on my related patch, I assumed
> you're okay with having those rx filter flags preserved in ath_calcrxfilter.
I did send some feedback on the rx filter preserve patch. I think it's
unnecessary and sho
On 11/03/2011 04:11 PM, Felix Fietkau wrote:
> On 2011-11-03 2:55 PM, Zefir Kurtisi wrote:
>> This patch integrates the DFS module into ath9k, including
>> * building the module into ath9k_hw
>> * setting up DFS debugfs
>> * defining HW capability flag for DFS support
>> * setting this flag
On 11/03/2011 06:30 PM, Felix Fietkau wrote:
> On 2011-11-03 6:25 PM, Zefir Kurtisi wrote:
>> On 11/03/2011 04:51 PM, Christian Lamparter wrote:
>>> On Thursday, November 03, 2011 02:55:53 PM Zefir Kurtisi wrote:
[...]
>>> where? There's no kconfig option, yet it has the CONFIG_ perifx.
>>>
On 2011-11-03 6:25 PM, Zefir Kurtisi wrote:
> On 11/03/2011 04:51 PM, Christian Lamparter wrote:
>> On Thursday, November 03, 2011 02:55:53 PM Zefir Kurtisi wrote:
>>> This patch integrates the DFS module into ath9k, including
>>> * building the module into ath9k_hw
>>> * setting up DFS debug
On 11/03/2011 04:51 PM, Christian Lamparter wrote:
> On Thursday, November 03, 2011 02:55:53 PM Zefir Kurtisi wrote:
>> This patch integrates the DFS module into ath9k, including
>> * building the module into ath9k_hw
>> * setting up DFS debugfs
>> * defining HW capability flag for DFS support
>
On Thu, Nov 3, 2011 at 10:15 PM, Zefir Kurtisi
wrote:
> On 11/03/2011 04:27 PM, Mohammed Shafi wrote:
>> Hi Zefir,
>>
> Hello Mohammed,
>
>> On Thu, Nov 3, 2011 at 7:25 PM, Zefir Kurtisi
>> wrote:
>>> [...]
>>>
>>> + if (ah->caps.hw_caps && ATH9K_HW_CAP_DFS) {
>>> + /**
>>> +
On 11/03/2011 04:27 PM, Mohammed Shafi wrote:
> Hi Zefir,
>
Hello Mohammed,
> On Thu, Nov 3, 2011 at 7:25 PM, Zefir Kurtisi
> wrote:
>> [...]
>>
>> + if (ah->caps.hw_caps && ATH9K_HW_CAP_DFS) {
>> + /**
>> +* enable radar pulse detection
>> +*
On 11/03/2011 04:56 PM, Mohammed Shafi wrote:
> On Thu, Nov 3, 2011 at 7:25 PM, Zefir Kurtisi
> wrote:
>> [...]
>> + switch (are->pulse_bw_info) {
>> + case 0:
>
> can we define some macro for this. thanks!
>
Ok.
___
ath9k-devel mailing l
On 11/03/2011 04:54 PM, Mohammed Shafi wrote:
> On Thu, Nov 3, 2011 at 7:25 PM, Zefir Kurtisi
> wrote:
>> [...]
>> +static bool postprocess_radar_event(struct ath_softc *sc,
>> + struct ath_radar_data *are, struct dfs_radar_pulse *drp)
>
> ath9k_postprocess_radar_event would be bet
On Thursday, November 03, 2011 02:55:53 PM Zefir Kurtisi wrote:
> This patch integrates the DFS module into ath9k, including
> * building the module into ath9k_hw
> * setting up DFS debugfs
> * defining HW capability flag for DFS support
> * setting this flag by DFS supporting devices
>(so
On Thu, Nov 3, 2011 at 7:25 PM, Zefir Kurtisi wrote:
> This initial DFS module provides basic functionality to deal with
> radar pulses reported by the DFS HW pattern detector.
>
> The reported data is evaluated and basic plausibility checks are
> performed to filter false pulses. Passing radar pu
On Thu, Nov 3, 2011 at 7:25 PM, Zefir Kurtisi wrote:
> This initial DFS module provides basic functionality to deal with
> radar pulses reported by the DFS HW pattern detector.
>
> The reported data is evaluated and basic plausibility checks are
> performed to filter false pulses. Passing radar pu
Hi Zefir,
On Thu, Nov 3, 2011 at 7:25 PM, Zefir Kurtisi wrote:
> This patch integrates the DFS module into ath9k, including
> * building the module into ath9k_hw
> * setting up DFS debugfs
> * defining HW capability flag for DFS support
> * setting this flag by DFS supporting devices
> (so
On 2011-11-03 2:55 PM, Zefir Kurtisi wrote:
> This patch integrates the DFS module into ath9k, including
> * building the module into ath9k_hw
> * setting up DFS debugfs
> * defining HW capability flag for DFS support
> * setting this flag by DFS supporting devices
> (so far: AR_SREV_92
This patch series proposes DFS radar pulse detection for ath9k.
Updates
* use DFS HW capability flag instead of #ifdefs
* disable feature by default
* moved DFS debugfs into own file
* reverted BIT() debug flags to hex
* limited DFS support to AR_SREV_9280_20_OR_LATER (TBC)
* minor changes c
This patch integrates the DFS module into ath9k, including
* building the module into ath9k_hw
* setting up DFS debugfs
* defining HW capability flag for DFS support
* setting this flag by DFS supporting devices
(so far: AR_SREV_9280_20_OR_LATER, TBC)
* setting PHYRADAR rx filter flag to en
This initial DFS module provides basic functionality to deal with
radar pulses reported by the DFS HW pattern detector.
The reported data is evaluated and basic plausibility checks are
performed to filter false pulses. Passing radar pulses are
forwarded to pattern detectors (not part of this patch
24 matches
Mail list logo
