Mon, 22 Oct 2012 21:03:01 +0200
Jérôme a écrit:
> Hi all.
>
> I've been using an AR7010 device for a few months now, and I face regular
> disconnections.
[...]
> Is this a known issue ?
>
> Is there something I can do to help solving this ?
Hi again.
I can't find anything relevant in the log
On 29 October 2012 03:20, Amin Gholoobi wrote:
> Normally a wireless reference clock is running at 1MHz and I would like to
> modify this one so it can run at 40MHz.
>
> I was wondering if there is any option in the driver which I can change and
> adjust the reference clock due to my needs.
The
On 2012-10-29 1:34 PM, Felix Fietkau wrote:
> On 2012-10-29 1:25 PM, Sven Eckelmann wrote:
>> The ath9k xmit functions for AMPDUs can send frames as non-aggregate in case
>> only one frame is currently available. The client will then answer using a
>> normal Ack instead of a BlockAck. This acknowle
On 2012-10-29 1:25 PM, Sven Eckelmann wrote:
> The ath9k xmit functions for AMPDUs can send frames as non-aggregate in case
> only one frame is currently available. The client will then answer using a
> normal Ack instead of a BlockAck. This acknowledgement has no TID stored and
> therefore the har
The ath9k xmit functions for AMPDUs can send frames as non-aggregate in case
only one frame is currently available. The client will then answer using a
normal Ack instead of a BlockAck. This acknowledgement has no TID stored and
therefore the hardware is not able to provide us the corresponding TID
Dear all,
I would like to see if anyone can help me with modifying
the reference clock by using ath9k driver.
Normally a wireless reference clock is running at 1MHz and I would like to
modify this one so it can run at 40MHz.
I was wondering if there is any option in the driver which I can change
