Hello Mr.Adrian,
Thanks for your response. I understand the following: Please correct if I
am wrong.
1. With WLAN_ACTIVE and BT_ACTIVE, the wireless medium is managed between BT
and WLAN without stomping the traffic.
2. With WLAN_ACTIVE, BT_ACTIVE and BT_PRIORITY, WiFI traffic stomping is
No, wifi stomping occurs with both 2-wire and 3-wire.
BT_PRIORITY just gives the MAC the ability to tell the difference
between high priority TX and any bt activity requiring the air, so the
MAC can then choose a weight based on differnet kinds of BT inputs.
If all you have is two wire, then you
Hi everyone,
We are using ath9k for our research project. The wlan interface that we
have is AR9285. Basically we want to adjust the data rate of beacon frame
to higher rate, i.e. from 1Mbps to 54Mbps, so that the beacon frame will
use less channel time.
I tried to achieve that by simply change
In routine ath_tx_fill_desc(), the txpower is only set to
MAX_RATE_POWER. Now it respects the txpower from bss_conf and set it if it
is (txpower * 2) MAX_RATE_POWER else set to MAX_RATE_POWER.
Signed-off-by: Tobias Steinicke tsteini...@net.t-labs.tu-berlin.de
---
On 10 April 2013 15:03, Tobias Steinicke
tobias.steini...@net.t-labs.tu-berlin.de wrote:
In routine ath_tx_fill_desc(), the txpower is only set to
MAX_RATE_POWER. Now it respects the txpower from bss_conf and set it if it
is (txpower * 2) MAX_RATE_POWER else set to MAX_RATE_POWER.
This
I fucked the format. Sorry for that.
I will resend it.
Tobias Steinicke
Am 11.04.2013 00:03, schrieb Tobias Steinicke:
In routine ath_tx_fill_desc(), the txpower is only set to
MAX_RATE_POWER. Now it respects the txpower from bss_conf and set it if it
is (txpower * 2) MAX_RATE_POWER else set
On 2013-04-11 1:20 AM, Adrian Chadd wrote:
On 10 April 2013 15:03, Tobias Steinicke
tobias.steini...@net.t-labs.tu-berlin.de wrote:
In routine ath_tx_fill_desc(), the txpower is only set to
MAX_RATE_POWER. Now it respects the txpower from bss_conf and set it if it
is (txpower * 2)
In routine ath_tx_fill_desc(), the txpower is only set to
MAX_RATE_POWER. Now it respects the txpower from bss_conf and set it if it
is (txpower * 2) MAX_RATE_POWER else set to MAX_RATE_POWER.
Signed-off-by: Tobias Steinicke tsteini...@net.t-labs.tu-berlin.de
---
On 10 April 2013 16:24, Felix Fietkau n...@openwrt.org wrote:
I think TPC power value mappings were only problematic in pre-802.11n
chipsets, all chipsets supported by ath9k should be fine. There may be
some minor changes missing to enable it on some older chipsets, but
other than that it
Am 11.04.2013 01:20, schrieb Adrian Chadd:
On 10 April 2013 15:03, Tobias Steinicke
tobias.steini...@net.t-labs.tu-berlin.de wrote:
In routine ath_tx_fill_desc(), the txpower is only set to
MAX_RATE_POWER. Now it respects the txpower from bss_conf and set it if it
is (txpower * 2)
If TPC isn't enabled, the cards transmit at the power configured in
the AR_PHY_TX_POWER_* registers.
Adrian
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Am 11.04.2013 01:38, schrieb Adrian Chadd:
If TPC isn't enabled, the cards transmit at the power configured in
the AR_PHY_TX_POWER_* registers.
I understand. Thanks for the clarification.
But since TPC is enabled, we have to set info.txpower to the
right value. Also ar900[23]_set_txdesc() have
hi,
I am trying to measure the time when the frame is inserted into queue
(ath_tx_process_buffer, ath_drain_txq_list[not req actually])
and when one receives ACK from hardware in ath_tx_process_buffer()
in the descriptor, ath_tx_status and eventually the
timestamp is calculated in
13 matches
Mail list logo
