On Sat, Oct 25, 2014 at 12:53 AM, Kamran Nishat wrote:
>
> But for this channel conditions should be changing at the scale of 100
> micro secs consistently.
>
> On Sat, Oct 25, 2014 at 12:13 AM, Adrian Chadd wrote:
> > It's not completely unsurprising - the initial channel estimate and
> > such i
On Mon, Jun 22, 2015 at 5:13 PM, Janusz Dziedzic
wrote:
> In case we will get ROC abort we should not call
> ieee80211_remain_on_channel_expired().
>
> In other case I hit such warning on MIPS and
> p2p negotiation failed (tested with use_chanctx=1).
>
> ath: phy0: Starting RoC period
> ath: phy0:
On Mon, Jun 22, 2015 at 6:32 PM, Michal Kazior wrote:
> On 22 June 2015 at 13:56, Krishna Chaitanya wrote:
>> On Mon, Jun 22, 2015 at 5:13 PM, Janusz Dziedzic
>> wrote:
>>> In case we will get ROC abort we should not call
>>> ieee80211_remain_on_channel_expir
Hi All,
I am working on AMPDU stats for ath9k PCIe cards for use as sniffer in
monitor mode.
As the driver doesnt support the AMPDU stats for radiotap we have
written the below snippet to add support for the same.
Can someone answer the below queries?
1) How to populate the below fields?
+ Linux Wireless for Information.
On Tue, Dec 4, 2012 at 5:51 PM, Krishna Chaitanya
wrote:
> Hi All,
>
> I am working on AMPDU stats for ath9k PCIe cards for use as sniffer in
> monitor mode.
> As the driver doesnt support the AMPDU stats for radiotap we have
> written the be
Hi All,
While testing the AMSDU patch and trying to send a AMSDU with each
MSDU 2000 bytes and 3 MSDU's in AMSDU
observed that the DMA engine times out and causes the below warning.
This might be due to a large frame being
trasnferred.
Tried to check the maximum supported frame by ath9k, but coul
