[ath9k-devel] [RFC 05/18] ath9k_hw: Add MCI h/w code and state machine
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
Signed-off-by: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
---
drivers/net/wireless/ath/ath9k/Makefile |3 +-
drivers/net/wireless/ath/ath9k/ar9003_mci.c | 1464 +++
drivers/net/wireless/ath/ath9k/hw.h | 26 +
3 files changed, 1492 insertions(+), 1 deletions(-)
create mode 100644 drivers/net/wireless/ath/ath9k/ar9003_mci.c
diff --git a/drivers/net/wireless/ath/ath9k/Makefile
b/drivers/net/wireless/ath/ath9k/Makefile
index 49d3f25..390797d 100644
--- a/drivers/net/wireless/ath/ath9k/Makefile
+++ b/drivers/net/wireless/ath/ath9k/Makefile
@@ -34,7 +34,8 @@ ath9k_hw-y:= \
ar9002_mac.o \
ar9003_mac.o \
ar9003_eeprom.o \
- ar9003_paprd.o
+ ar9003_paprd.o \
+ ar9003_mci.o
obj-$(CONFIG_ATH9K_HW) += ath9k_hw.o
diff --git a/drivers/net/wireless/ath/ath9k/ar9003_mci.c
b/drivers/net/wireless/ath/ath9k/ar9003_mci.c
new file mode 100644
index 000..8599822
--- /dev/null
+++ b/drivers/net/wireless/ath/ath9k/ar9003_mci.c
@@ -0,0 +1,1464 @@
+/*
+ * Copyright (c) 2008-2011 Atheros Communications Inc.
+ *
+ * Permission to use, copy, modify, and/or distribute this software for any
+ * purpose with or without fee is hereby granted, provided that the above
+ * copyright notice and this permission notice appear in all copies.
+ *
+ * THE SOFTWARE IS PROVIDED AS IS AND THE AUTHOR DISCLAIMS ALL WARRANTIES
+ * WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
+ * MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
+ * ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
+ * WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
+ * ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
+ * OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
+ */
+
+#include linux/export.h
+#include hw.h
+#include ar9003_phy.h
+#include ar9003_mci.h
+
+static void ar9003_mci_reset_req_wakeup(struct ath_hw *ah)
+{
+ if (!AR_SREV_9462_20(ah))
+ return;
+
+ REG_RMW_FIELD(ah, AR_MCI_COMMAND2,
+ AR_MCI_COMMAND2_RESET_REQ_WAKEUP, 1);
+ udelay(1);
+ REG_RMW_FIELD(ah, AR_MCI_COMMAND2,
+ AR_MCI_COMMAND2_RESET_REQ_WAKEUP, 0);
+}
+
+static int ar9003_mci_wait_for_interrupt(struct ath_hw *ah, u32 address,
+ u32 bit_position, int time_out)
+{
+ struct ath_common *common = ath9k_hw_common(ah);
+
+ while (time_out) {
+
+ if (REG_READ(ah, address) bit_position) {
+
+ REG_WRITE(ah, address, bit_position);
+
+ if (address == AR_MCI_INTERRUPT_RX_MSG_RAW) {
+
+ if (bit_position
+ AR_MCI_INTERRUPT_RX_MSG_REQ_WAKE)
+ ar9003_mci_reset_req_wakeup(ah);
+
+ if (bit_position
+ (AR_MCI_INTERRUPT_RX_MSG_SYS_SLEEPING |
+AR_MCI_INTERRUPT_RX_MSG_SYS_WAKING))
+ REG_WRITE(ah, AR_MCI_INTERRUPT_RAW,
+ AR_MCI_INTERRUPT_REMOTE_SLEEP_UPDATE);
+
+ REG_WRITE(ah, AR_MCI_INTERRUPT_RAW,
+ AR_MCI_INTERRUPT_RX_MSG);
+ }
+ break;
+ }
+
+ udelay(10);
+ time_out -= 10;
+
+ if (time_out 0)
+ break;
+ }
+
+ if (time_out = 0) {
+ ath_dbg(common, ATH_DBG_MCI,
+ MCI Wait for Reg 0x%08x = 0x%08x timeout.\n,
+ address, bit_position);
+ ath_dbg(common, ATH_DBG_MCI,
+ MCI INT_RAW = 0x%08x, RX_MSG_RAW = 0x%08x,
+ REG_READ(ah, AR_MCI_INTERRUPT_RAW),
+ REG_READ(ah, AR_MCI_INTERRUPT_RX_MSG_RAW));
+ time_out = 0;
+ }
+
+ return time_out;
+}
+
+void ar9003_mci_remote_reset(struct ath_hw *ah, bool wait_done)
+{
+ u32 payload[4] = { 0x, 0x, 0x, 0xff00};
+
+ ar9003_mci_send_message(ah, MCI_REMOTE_RESET, 0, payload, 16,
+ wait_done, false);
+ udelay(5);
+}
+
+void ar9003_mci_send_lna_transfer(struct ath_hw *ah, bool wait_done)
+{
+ u32 payload = 0x;
+
+ ar9003_mci_send_message(ah, MCI_LNA_TRANS, 0, payload, 1,
+ wait_done, false);
+}
+
+static void ar9003_mci_send_req_wake(struct ath_hw *ah, bool wait_done)
+{
+ ar9003_mci_send_message(ah, MCI_REQ_WAKE, MCI_FLAG_DISABLE_TIMESTAMP,
+ NULL, 0, wait_done, false);
+ udelay(5
[ath9k-devel] [RFC 12/18] ath9k_hw: MCI related changes in chip management
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
send halt BT GPM if the chip is in network sleep and BT state
is awake
Signed-off-by: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
---
drivers/net/wireless/ath/ath9k/hw.c | 24
drivers/net/wireless/ath/ath9k/reg.h |2 ++
2 files changed, 26 insertions(+), 0 deletions(-)
diff --git a/drivers/net/wireless/ath/ath9k/hw.c
b/drivers/net/wireless/ath/ath9k/hw.c
index 662ab7e..ba5734a 100644
--- a/drivers/net/wireless/ath/ath9k/hw.c
+++ b/drivers/net/wireless/ath/ath9k/hw.c
@@ -1933,6 +1933,7 @@ static bool ath9k_hw_set_power_awake(struct ath_hw *ah,
int setChip)
bool ath9k_hw_setpower(struct ath_hw *ah, enum ath9k_power_mode mode)
{
struct ath_common *common = ath9k_hw_common(ah);
+ struct ath9k_hw_mci *mci = ah-btcoex_hw.mci;
int status = true, setChip = true;
static const char *modes[] = {
AWAKE,
@@ -1950,12 +1951,35 @@ bool ath9k_hw_setpower(struct ath_hw *ah, enum
ath9k_power_mode mode)
switch (mode) {
case ATH9K_PM_AWAKE:
status = ath9k_hw_set_power_awake(ah, setChip);
+
+ if (ah-caps.hw_caps ATH9K_HW_CAP_MCI)
+ REG_WRITE(ah, AR_RTC_KEEP_AWAKE, 0x2);
+
break;
case ATH9K_PM_FULL_SLEEP:
+
+ if (ah-caps.hw_caps ATH9K_HW_CAP_MCI) {
+ if (ar9003_mci_state(ah, MCI_STATE_ENABLE, NULL)
+ (mci-bt_state != MCI_BT_SLEEP)
+ !mci-halted_bt_gpm) {
+ ath_dbg(common, ATH_DBG_MCI, MCI halt BT GPM
+ (full_sleep));
+ ar9003_mci_send_coex_halt_bt_gpm(ah,
+true, true);
+ }
+
+ mci-ready = false;
+ REG_WRITE(ah, AR_RTC_KEEP_AWAKE, 0x2);
+ }
+
ath9k_set_power_sleep(ah, setChip);
ah-chip_fullsleep = true;
break;
case ATH9K_PM_NETWORK_SLEEP:
+
+ if (ah-caps.hw_caps ATH9K_HW_CAP_MCI)
+ REG_WRITE(ah, AR_RTC_KEEP_AWAKE, 0x2);
+
ath9k_set_power_network_sleep(ah, setChip);
break;
default:
diff --git a/drivers/net/wireless/ath/ath9k/reg.h
b/drivers/net/wireless/ath/ath9k/reg.h
index ba3672f..6e2f188 100644
--- a/drivers/net/wireless/ath/ath9k/reg.h
+++ b/drivers/net/wireless/ath/ath9k/reg.h
@@ -1279,6 +1279,8 @@ enum {
#define AR_RTC_INTR_MASK \
((AR_SREV_9100(ah)) ? (AR_RTC_BASE + 0x0058) : 0x7058)
+#define AR_RTC_KEEP_AWAKE 0x7034
+
/* RTC_DERIVED_* - only for AR9100 */
#define AR_RTC_DERIVED_CLK \
--
1.7.0.4
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
[ath9k-devel] [RFC 13/18] ath9k_hw: MCI related changes in set_reset_reg
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
Signed-off-by: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
---
drivers/net/wireless/ath/ath9k/hw.c | 14 +++---
1 files changed, 11 insertions(+), 3 deletions(-)
diff --git a/drivers/net/wireless/ath/ath9k/hw.c
b/drivers/net/wireless/ath/ath9k/hw.c
index ba5734a..1d71d1b 100644
--- a/drivers/net/wireless/ath/ath9k/hw.c
+++ b/drivers/net/wireless/ath/ath9k/hw.c
@@ -1350,6 +1350,7 @@ static bool ath9k_hw_set_reset_power_on(struct ath_hw *ah)
static bool ath9k_hw_set_reset_reg(struct ath_hw *ah, u32 type)
{
+ bool ret = false;
if (AR_SREV_9300_20_OR_LATER(ah)) {
REG_WRITE(ah, AR_WA, ah-WARegVal);
@@ -1361,13 +1362,20 @@ static bool ath9k_hw_set_reset_reg(struct ath_hw *ah,
u32 type)
switch (type) {
case ATH9K_RESET_POWER_ON:
- return ath9k_hw_set_reset_power_on(ah);
+ ret = ath9k_hw_set_reset_power_on(ah);
+ break;
case ATH9K_RESET_WARM:
case ATH9K_RESET_COLD:
- return ath9k_hw_set_reset(ah, type);
+ ret = ath9k_hw_set_reset(ah, type);
+ break;
default:
- return false;
+ break;
}
+
+ if (ah-caps.hw_caps ATH9K_HW_CAP_MCI)
+ REG_WRITE(ah, AR_RTC_KEEP_AWAKE, 0x2);
+
+ return ret;
}
static bool ath9k_hw_chip_reset(struct ath_hw *ah,
--
1.7.0.4
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
[ath9k-devel] [RFC 00/18] ath9k: Add support for MCI BT coex
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com Add support for MCI BT-Coex for AR9462. with AR9462 we have WLAN and BT coexists via MCI protocol(Message Coexistence Interface) WLAN and BT exchanges GPM, SCHED messages and few other messages for coexistence. this is not yet tested and need some more review, few misc cleanups. please add your review comments. thanks a lot to Rajkumar Manoharan rmano...@qca.qualcomm.com for his suggestions, review comments, code cleanups, and modifications in design. Mohammed Shafi Shajakhan (18): ath9k_hw: add definitions to support MCI h/w code ath9k_hw: add GPIO output MUX related macros ath9k_hw: Add MCI h/w specific structure ath9k_hw: initialize MCI parameters ath9k_hw: Add MCI h/w code and state machine ath9k: Add MCI interrupt to interrupt mask ath9k_hw: take care of enabling MCI interrupts ath9k_hw: check for asynchronous MCI interrupt pending ath9k_hw: check for MCI interrupt in get_isr ath9k: add MCI specific definitions and structures ath9k: Add functions to allocate/free buffers for MCI ath9k_hw: MCI related changes in chip management ath9k_hw: MCI related changes in set_reset_reg ath9k_hw: Add support for MCI WLAN calibration ath9k_hw: Add MCI related changes in chip reset ath9k: make ath_reset non-static ath9k: MCI state machine based on MCI interrupt ath9k: fix a typo drivers/net/wireless/ath/ath9k/Makefile |3 +- drivers/net/wireless/ath/ath9k/ar9003_calib.c | 43 + drivers/net/wireless/ath/ath9k/ar9003_mac.c | 36 +- drivers/net/wireless/ath/ath9k/ar9003_mci.c | 1464 + drivers/net/wireless/ath/ath9k/ar9003_mci.h | 102 ++ drivers/net/wireless/ath/ath9k/ar9003_phy.h |3 + drivers/net/wireless/ath/ath9k/ath9k.h|2 + drivers/net/wireless/ath/ath9k/btcoex.c |2 +- drivers/net/wireless/ath/ath9k/btcoex.h | 31 + drivers/net/wireless/ath/ath9k/hw.c | 174 +++- drivers/net/wireless/ath/ath9k/hw.h | 182 +++ drivers/net/wireless/ath/ath9k/init.c | 33 + drivers/net/wireless/ath/ath9k/mac.c | 17 +- drivers/net/wireless/ath/ath9k/main.c | 11 +- drivers/net/wireless/ath/ath9k/mci.c | 419 +++ drivers/net/wireless/ath/ath9k/mci.h | 20 + drivers/net/wireless/ath/ath9k/reg.h | 306 +- 17 files changed, 2807 insertions(+), 41 deletions(-) create mode 100644 drivers/net/wireless/ath/ath9k/ar9003_mci.c create mode 100644 drivers/net/wireless/ath/ath9k/ar9003_mci.h ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
[ath9k-devel] [RFC 04/18] ath9k_hw: initialize MCI parameters
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
these parameter will be utilized and modified in the MCI hardware codes
state machine
Signed-off-by: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
---
drivers/net/wireless/ath/ath9k/init.c | 22 ++
1 files changed, 22 insertions(+), 0 deletions(-)
diff --git a/drivers/net/wireless/ath/ath9k/init.c
b/drivers/net/wireless/ath/ath9k/init.c
index e046de9..34b922b 100644
--- a/drivers/net/wireless/ath/ath9k/init.c
+++ b/drivers/net/wireless/ath/ath9k/init.c
@@ -408,6 +408,7 @@ fail:
static int ath9k_init_btcoex(struct ath_softc *sc)
{
struct ath_txq *txq;
+ struct ath_hw *ah = sc-sc_ah;
int r;
switch (sc-sc_ah-btcoex_hw.scheme) {
@@ -426,6 +427,27 @@ static int ath9k_init_btcoex(struct ath_softc *sc)
sc-btcoex.bt_stomp_type = ATH_BTCOEX_STOMP_LOW;
sc-btcoex.duty_cycle = ATH_BTCOEX_DEF_DUTY_CYCLE;
INIT_LIST_HEAD(sc-btcoex.mci.info);
+ if (sc-sc_ah-caps.hw_caps ATH9K_HW_CAP_MCI) {
+ ah-btcoex_hw.mci.ready = false;
+ ah-btcoex_hw.mci.bt_state = 0;
+ ah-btcoex_hw.mci.bt_ver_major = 3;
+ ah-btcoex_hw.mci.bt_ver_minor = 0;
+ ah-btcoex_hw.mci.bt_version_known = false;
+ ah-btcoex_hw.mci.update_2g5g = true;
+ ah-btcoex_hw.mci.is_2g = true;
+ ah-btcoex_hw.mci.wlan_channels_update = false;
+ ah-btcoex_hw.mci.wlan_channels[0] = 0x;
+ ah-btcoex_hw.mci.wlan_channels[1] = 0x;
+ ah-btcoex_hw.mci.wlan_channels[2] = 0x;
+ ah-btcoex_hw.mci.wlan_channels[3] = 0x7fff;
+ ah-btcoex_hw.mci.query_bt = true;
+ ah-btcoex_hw.mci.unhalt_bt_gpm = true;
+ ah-btcoex_hw.mci.halted_bt_gpm = false;
+ ah-btcoex_hw.mci.need_flush_btinfo = false;
+ ah-btcoex_hw.mci.wlan_cal_seq = 0;
+ ah-btcoex_hw.mci.wlan_cal_done = 0;
+ ah-btcoex_hw.mci.config = 0x2201;
+ }
break;
default:
WARN_ON(1);
--
1.7.0.4
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
[ath9k-devel] [RFC 02/18] ath9k_hw: add GPIO output MUX related macros
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com Signed-off-by: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com --- drivers/net/wireless/ath/ath9k/hw.h | 10 ++ 1 files changed, 10 insertions(+), 0 deletions(-) diff --git a/drivers/net/wireless/ath/ath9k/hw.h b/drivers/net/wireless/ath/ath9k/hw.h index 4f786cb..cd43d59 100644 --- a/drivers/net/wireless/ath/ath9k/hw.h +++ b/drivers/net/wireless/ath/ath9k/hw.h @@ -126,6 +126,16 @@ #define AR_GPIO_OUTPUT_MUX_AS_RX_CLEAR_EXTERNAL 4 #define AR_GPIO_OUTPUT_MUX_AS_MAC_NETWORK_LED5 #define AR_GPIO_OUTPUT_MUX_AS_MAC_POWER_LED 6 +#define AR_GPIO_OUTPUT_MUX_AS_MCI_WLAN_DATA 0x16 +#define AR_GPIO_OUTPUT_MUX_AS_MCI_WLAN_CLK 0x17 +#define AR_GPIO_OUTPUT_MUX_AS_MCI_BT_DATA0x18 +#define AR_GPIO_OUTPUT_MUX_AS_MCI_BT_CLK 0x19 +#define AR_GPIO_OUTPUT_MUX_AS_WL_IN_TX 0x14 +#define AR_GPIO_OUTPUT_MUX_AS_WL_IN_RX 0x13 +#define AR_GPIO_OUTPUT_MUX_AS_BT_IN_TX 9 +#define AR_GPIO_OUTPUT_MUX_AS_BT_IN_RX 8 +#define AR_GPIO_OUTPUT_MUX_AS_RUCKUS_STROBE 0x1d +#define AR_GPIO_OUTPUT_MUX_AS_RUCKUS_DATA0x1e #define AR_GPIOD_MASK 0x1FFF #define AR_GPIO_BIT(_gpio) (1 (_gpio)) -- 1.7.0.4 ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] turning monitor mode on in ath9k code
On Sat, Nov 5, 2011 at 5:14 AM, abhinav narain abhinavnarai...@gmail.com wrote: hi, Hi Abhinav, I want to sniff all the packets from the network. I am setting sc-sc_ah-is_monitoring = true; in ath9k_start() but this gets set to false in in ath9k_config(..). using the flag : IEEE80211_CONF_CHANGE_MONITOR, by doing changed | = IEEE80211_CONF_CHANGE_MONITOR ; those were mac80211 (protocol stack for 802.11) flags that has to be taken care by the driver. mac80211 sets those flags when the interface gets down Does not set it on, and I hope this does not break the things in kernel elsewhere Both the functions are defined in main.c in compat../drivers/net/wireless/ath/ath9k I have the following doubts : 1. this flag is not used anywhere and I don't get how should i set changed so that this flag is set. 2. If I force ah-is_monitoring to true, before this, I am not sure how the driver will behave as other things might go wrong elsewhere Please suggest how to set the monitoring mode. please install iw sudo apt-get install you can uncheck the Enable wireless in gui sudo service network-manager stop sudo iw dev wlan0 set type monitor sudo iw dev wlan0 set channel 6 sudo ifconfig wlan0 up - Also, I have doubt in setting the monitor mode using iwconfig. The usual mode of the device is Master( using iwconfig ) When, I use the following commands : $ifconfig wlan0 down $iwconfig wlan0 mode monitor $ifconfig wlan0 up The router reboots on the last command, and the wlan0 still shows monitor mode(iwconfig output) The browser interface also shows Master mode. monitor mode ? A user space ioctl call : ioctl(sd, SIOCSIWMODE, wrq) gives me an error : Device or resource ready. the radio interface is not configure. There is a mon.wlan0, mon.wlan1 (in Monitor mode) interfaces in iwconfig output. Shall i use them to create a raw socket and sniff on it ? are you trying to use some AP sort of device as monitor mode? When I use iw with the following command : $ iw phy phy0 interface add mon0 type monitor It gives error, that device not found ... what should I do to set wlan0 on after having my wlan74 interface as an AP mode using hostpad, i did this and it seem to work for me sudo iw dev wlan74 interface add mon74 type monitor sudo ifconfig mon74 up ? Please suggest Abhinav Narain ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] Unrealistic RSSI values being reported
On Fri, Nov 4, 2011 at 4:57 PM, Daniel Smith viscous.liq...@gmail.com wrote: On 11/3/2011 7:10 PM, Mohammed Shafi wrote: Hi Daniel, On Fri, Nov 4, 2011 at 12:58 AM, Daniel Smithviscous.liq...@gmail.com 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 getting a range of values. The more interesting ones are all the frames reporting a signal of 110+ dBm. To see what is being pulled from the descriptors I dumped rs-rs_rssi to klog when the value was larger than 95. Below is a snippet showing the ranging values, i tried with the AR9382 card in 3.1.0-wl with the attached debug patch, can you please give a sample log with the patch applied and putting the interface in monitor mode. did you print/check rs_rssi somewhere else? did you also try with the latest package http://linuxwireless.org/download/compat-wireless-2.6/ First I apologize as I forgot to mention I am putting the channel into HT40 mode and the frames coming in are non-HT as that is the stated that the issue was reported to me. I have not ran test yet to see if it occurs with the channel in HT20 and non-ht mode. Also I have one more test to run on compat-wireless-3.0-2 but it looks like I am not seeing any issue with it. For reference here is the patch from my change, very similar to yours except that I didn't dump signal or noise. @@ -1015,6 +1015,8 @@ static int ath9k_rx_skb_preprocess(struct ath_common *common, rx_status-snr = rx_stats-rs_rssi; rx_status-antenna = rx_stats-rs_antenna; rx_status-flag |= RX_FLAG_MACTIME_MPDU; + if (rx_stats-rs_rssi 95 || rx_stats-rs_rssi 0) + printk([ath9k]: RSSI %hhd\n, rx_stats-rs_rssi); hi Daniel, some values i got signal = noise + rs_rssi noise = -95 , rs_rssi = 55, signal = -40 rs_rssi has values like 65, 57, 52, 29, 53, 55, 21 , 35 , 50. sure values 95 does not seems to occur for me. sure i can try with HT40 mode and put these prints will be out of station for 3 days, will try to debug once , hope some other developers might provide more inputs return 0; } I will rerun it with your additions so you can see those values as well. Yes I can also test it with a nightly package to see if it has been resolved. Thanks for the Help! dps ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] [RFC v2 2/2] ath9k: integrate initial DFS module
Hi Zefir,
On Thu, Nov 3, 2011 at 7:25 PM, Zefir Kurtisi zefir.kurt...@neratec.com 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_9280_20_OR_LATER, TBC)
* setting PHYRADAR rx filter flag to enable radar
pulse reporting
* forward radar PHY errors to dfs module
This is WIP and at its current stage is limited to test ath9k
pulse detection capabilities. The DFS pattern matching is
TBD in the higher layers and is not part of this patch.
CONFIG_ATH9K_DFS must be set to enable pulse detection.
Signed-off-by: Zefir Kurtisi zefir.kurt...@neratec.com
---
drivers/net/wireless/ath/ath9k/Makefile | 2 ++
drivers/net/wireless/ath/ath9k/debug.c | 3 +++
drivers/net/wireless/ath/ath9k/debug.h | 2 ++
drivers/net/wireless/ath/ath9k/hw.c | 12
drivers/net/wireless/ath/ath9k/hw.h | 1 +
drivers/net/wireless/ath/ath9k/main.c | 17 +
drivers/net/wireless/ath/ath9k/recv.c | 18 +-
7 files changed, 50 insertions(+), 5 deletions(-)
diff --git a/drivers/net/wireless/ath/ath9k/Makefile
b/drivers/net/wireless/ath/ath9k/Makefile
index 36ed3c4..1f260a5 100644
--- a/drivers/net/wireless/ath/ath9k/Makefile
+++ b/drivers/net/wireless/ath/ath9k/Makefile
@@ -29,6 +29,8 @@ ath9k_hw-y:= \
eeprom_9287.o \
ani.o \
btcoex.o \
+ dfs.o \
+ dfs_debug.o \
mac.o \
ar9002_mac.o \
ar9003_mac.o \
diff --git a/drivers/net/wireless/ath/ath9k/debug.c
b/drivers/net/wireless/ath/ath9k/debug.c
index 138ae09..6642108 100644
--- a/drivers/net/wireless/ath/ath9k/debug.c
+++ b/drivers/net/wireless/ath/ath9k/debug.c
@@ -1633,6 +1633,9 @@ int ath9k_init_debug(struct ath_hw *ah)
debugfs_create_file(debug, S_IRUSR | S_IWUSR, sc-debug.debugfs_phy,
sc, fops_debug);
#endif
+
+ ath9k_dfs_init_debug(sc);
+
debugfs_create_file(dma, S_IRUSR, sc-debug.debugfs_phy, sc,
fops_dma);
debugfs_create_file(interrupt, S_IRUSR, sc-debug.debugfs_phy, sc,
diff --git a/drivers/net/wireless/ath/ath9k/debug.h
b/drivers/net/wireless/ath/ath9k/debug.h
index 4f6c939..f70735a 100644
--- a/drivers/net/wireless/ath/ath9k/debug.h
+++ b/drivers/net/wireless/ath/ath9k/debug.h
@@ -19,6 +19,7 @@
#include hw.h
#include rc.h
+#include dfs_debug.h
struct ath_txq;
struct ath_buf;
@@ -180,6 +181,7 @@ struct ath_stats {
struct ath_interrupt_stats istats;
struct ath_tx_stats txstats[ATH9K_NUM_TX_QUEUES];
struct ath_rx_stats rxstats;
+ struct ath_dfs_stats dfs_stats;
u32 reset[__RESET_TYPE_MAX];
};
diff --git a/drivers/net/wireless/ath/ath9k/hw.c
b/drivers/net/wireless/ath/ath9k/hw.c
index 76dbc85..0f2fb42 100644
--- a/drivers/net/wireless/ath/ath9k/hw.c
+++ b/drivers/net/wireless/ath/ath9k/hw.c
@@ -2333,6 +2333,18 @@ int ath9k_hw_fill_cap_info(struct ath_hw *ah)
pCap-pcie_lcr_offset = 0x80;
}
+#ifdef CONFIG_ATH9K_DFS
+ /*
+ * enable radar detection on DFS supporting devices
+ */
+ if (AR_SREV_9280_20_OR_LATER(ah)) {
+ /*
+ * TODO: check for which chip-sets we want to support DFS
+ */
+ pCap-hw_caps |= ATH9K_HW_CAP_DFS;
+ }
+#endif
+
tx_chainmask = pCap-tx_chainmask;
rx_chainmask = pCap-rx_chainmask;
while (tx_chainmask || rx_chainmask) {
diff --git a/drivers/net/wireless/ath/ath9k/hw.h
b/drivers/net/wireless/ath/ath9k/hw.h
index 9dbc3cd..4f02f83 100644
--- a/drivers/net/wireless/ath/ath9k/hw.h
+++ b/drivers/net/wireless/ath/ath9k/hw.h
@@ -204,6 +204,7 @@ enum ath9k_hw_caps {
ATH9K_HW_CAP_5GHZ = BIT(14),
ATH9K_HW_CAP_APM = BIT(15),
ATH9K_HW_CAP_RTT = BIT(16),
+ ATH9K_HW_CAP_DFS = BIT(17),
};
struct ath9k_hw_capabilities {
diff --git a/drivers/net/wireless/ath/ath9k/main.c
b/drivers/net/wireless/ath/ath9k/main.c
index d3b92ce..4d70aab 100644
--- a/drivers/net/wireless/ath/ath9k/main.c
+++ b/drivers/net/wireless/ath/ath9k/main.c
@@ -305,6 +305,23 @@ static bool ath_complete_reset(struct ath_softc *sc,
bool start)
ath9k_hw_antdiv_comb_conf_set(ah, div_ant_conf);
}
+ if (ah-caps.hw_caps ATH9K_HW_CAP_DFS) {
+ /**
+ * enable radar pulse detection
+ *
+ * TODO: do this only for DFS channels
+ */
+ ah-private_ops.set_radar_params(ah, ah-radar_conf);
can we do this something like ath9k_hw_set_radar_params?
Re: [ath9k-devel] [RFC v2 1/2] ath9k: add DFS radar pulse processing
On Thu, Nov 3, 2011 at 7:25 PM, Zefir Kurtisi zefir.kurt...@neratec.com 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 pulses are
forwarded to pattern detectors (not part of this patch).
The patch also includes
* new debug level ATH_DBG_DFS
* debugfs DFS radar statistics
Signed-off-by: Zefir Kurtisi zefir.kurt...@neratec.com
---
drivers/net/wireless/ath/ath.h | 2 +
drivers/net/wireless/ath/ath9k/dfs.c | 192
drivers/net/wireless/ath/ath9k/dfs.h | 24
drivers/net/wireless/ath/ath9k/dfs_debug.c | 89 +
drivers/net/wireless/ath/ath9k/dfs_debug.h | 59 +
5 files changed, 366 insertions(+), 0 deletions(-)
create mode 100644 drivers/net/wireless/ath/ath9k/dfs.c
create mode 100644 drivers/net/wireless/ath/ath9k/dfs.h
create mode 100644 drivers/net/wireless/ath/ath9k/dfs_debug.c
create mode 100644 drivers/net/wireless/ath/ath9k/dfs_debug.h
diff --git a/drivers/net/wireless/ath/ath.h b/drivers/net/wireless/ath/ath.h
index 46d6926..e38fcad 100644
--- a/drivers/net/wireless/ath/ath.h
+++ b/drivers/net/wireless/ath/ath.h
@@ -215,6 +215,7 @@ do {
\
* @ATH_DBG_HWTIMER: hardware timer handling
* @ATH_DBG_BTCOEX: bluetooth coexistance
* @ATH_DBG_BSTUCK: stuck beacons
+ * @ATH_DBG_DFS: radar datection
* @ATH_DBG_ANY: enable all debugging
*
* The debug level is used to control the amount and type of debugging output
@@ -240,6 +241,7 @@ enum ATH_DEBUG {
ATH_DBG_BTCOEX = 0x2000,
ATH_DBG_WMI = 0x4000,
ATH_DBG_BSTUCK = 0x8000,
+ ATH_DBG_DFS = 0x0001,
ATH_DBG_ANY = 0x
};
diff --git a/drivers/net/wireless/ath/ath9k/dfs.c
b/drivers/net/wireless/ath/ath9k/dfs.c
new file mode 100644
index 000..9d3c8b9
--- /dev/null
+++ b/drivers/net/wireless/ath/ath9k/dfs.c
@@ -0,0 +1,192 @@
+/*
+ * Copyright (c) 2008-2011 Atheros Communications Inc.
+ * Copyright (c) 2011 Neratec Solutions AG
+ *
+ * Permission to use, copy, modify, and/or distribute this software for any
+ * purpose with or without fee is hereby granted, provided that the above
+ * copyright notice and this permission notice appear in all copies.
+ *
+ * THE SOFTWARE IS PROVIDED AS IS AND THE AUTHOR DISCLAIMS ALL WARRANTIES
+ * WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
+ * MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
+ * ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
+ * WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
+ * ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
+ * OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
+ */
+
+#include hw.h
+#include hw-ops.h
+#include ath9k.h
+#include dfs.h
+#include dfs_debug.h
+
+/* pulse duration reported is scaled with 1000/800 us */
+#define AR93X_NSECS_PER_DUR 800
+static u32 dur_to_usecs(u32 dur)
+{
+ return (dur * AR93X_NSECS_PER_DUR + 500) / 1000;
+}
+
+/* internal struct to pass radar data */
+struct ath_radar_data {
+ u8 pulse_bw_info;
+ u8 rssi;
+ u8 ext_rssi;
+ u8 pulse_length_ext;
+ u8 pulse_length_pri;
+};
+
+/* TODO: move into or synchronize this with generic header
+ * as soon as IF is defined */
+struct dfs_radar_pulse {
+ u16 freq;
+ u64 ts;
+ u32 width;
+ u8 rssi;
+};
+
+#define PRI_CH_RADAR_FOUND 0x01
+#define EXT_CH_RADAR_FOUND 0x02
+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 better?
+{
+ u8 rssi;
+ u16 dur;
+
+ ath_dbg(ath9k_hw_common(sc-sc_ah), ATH_DBG_DFS,
+ pulse_bw_info=0x%x, pri,ext len/rssi=(%u/%u, %u/%u)\n,
+ are-pulse_bw_info,
+ are-pulse_length_pri, are-rssi,
+ are-pulse_length_ext, are-ext_rssi);
+
+ /* Only the last 2 bits of the BW info are relevant, they indicate
+ which channel the radar was detected in.*/
+ are-pulse_bw_info = 0x03;
+
+ switch (are-pulse_bw_info) {
+ case 0:
+ /* Bogus bandwidth info received in descriptor,
+ so ignore this PHY error */
+ DFS_STAT_INC(sc, bwinfo_discards);
+ return false;
+ case PRI_CH_RADAR_FOUND:
+ /* radar in ctrl channel */
+ dur = are-pulse_length_pri;
+ DFS_STAT_INC(sc, pri_phy_errors);
+ /* cannot use ctrl channel RSSI
+
Re: [ath9k-devel] [RFC v2 1/2] ath9k: add DFS radar pulse processing
On Thu, Nov 3, 2011 at 7:25 PM, Zefir Kurtisi zefir.kurt...@neratec.com 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 pulses are
forwarded to pattern detectors (not part of this patch).
The patch also includes
* new debug level ATH_DBG_DFS
* debugfs DFS radar statistics
Signed-off-by: Zefir Kurtisi zefir.kurt...@neratec.com
---
drivers/net/wireless/ath/ath.h | 2 +
drivers/net/wireless/ath/ath9k/dfs.c | 192
drivers/net/wireless/ath/ath9k/dfs.h | 24
drivers/net/wireless/ath/ath9k/dfs_debug.c | 89 +
drivers/net/wireless/ath/ath9k/dfs_debug.h | 59 +
5 files changed, 366 insertions(+), 0 deletions(-)
create mode 100644 drivers/net/wireless/ath/ath9k/dfs.c
create mode 100644 drivers/net/wireless/ath/ath9k/dfs.h
create mode 100644 drivers/net/wireless/ath/ath9k/dfs_debug.c
create mode 100644 drivers/net/wireless/ath/ath9k/dfs_debug.h
diff --git a/drivers/net/wireless/ath/ath.h b/drivers/net/wireless/ath/ath.h
index 46d6926..e38fcad 100644
--- a/drivers/net/wireless/ath/ath.h
+++ b/drivers/net/wireless/ath/ath.h
@@ -215,6 +215,7 @@ do {
\
* @ATH_DBG_HWTIMER: hardware timer handling
* @ATH_DBG_BTCOEX: bluetooth coexistance
* @ATH_DBG_BSTUCK: stuck beacons
+ * @ATH_DBG_DFS: radar datection
* @ATH_DBG_ANY: enable all debugging
*
* The debug level is used to control the amount and type of debugging output
@@ -240,6 +241,7 @@ enum ATH_DEBUG {
ATH_DBG_BTCOEX = 0x2000,
ATH_DBG_WMI = 0x4000,
ATH_DBG_BSTUCK = 0x8000,
+ ATH_DBG_DFS = 0x0001,
ATH_DBG_ANY = 0x
};
diff --git a/drivers/net/wireless/ath/ath9k/dfs.c
b/drivers/net/wireless/ath/ath9k/dfs.c
new file mode 100644
index 000..9d3c8b9
--- /dev/null
+++ b/drivers/net/wireless/ath/ath9k/dfs.c
@@ -0,0 +1,192 @@
+/*
+ * Copyright (c) 2008-2011 Atheros Communications Inc.
+ * Copyright (c) 2011 Neratec Solutions AG
+ *
+ * Permission to use, copy, modify, and/or distribute this software for any
+ * purpose with or without fee is hereby granted, provided that the above
+ * copyright notice and this permission notice appear in all copies.
+ *
+ * THE SOFTWARE IS PROVIDED AS IS AND THE AUTHOR DISCLAIMS ALL WARRANTIES
+ * WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
+ * MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
+ * ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
+ * WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
+ * ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
+ * OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
+ */
+
+#include hw.h
+#include hw-ops.h
+#include ath9k.h
+#include dfs.h
+#include dfs_debug.h
+
+/* pulse duration reported is scaled with 1000/800 us */
+#define AR93X_NSECS_PER_DUR 800
+static u32 dur_to_usecs(u32 dur)
+{
+ return (dur * AR93X_NSECS_PER_DUR + 500) / 1000;
+}
+
+/* internal struct to pass radar data */
+struct ath_radar_data {
+ u8 pulse_bw_info;
+ u8 rssi;
+ u8 ext_rssi;
+ u8 pulse_length_ext;
+ u8 pulse_length_pri;
+};
+
+/* TODO: move into or synchronize this with generic header
+ * as soon as IF is defined */
+struct dfs_radar_pulse {
+ u16 freq;
+ u64 ts;
+ u32 width;
+ u8 rssi;
+};
+
+#define PRI_CH_RADAR_FOUND 0x01
+#define EXT_CH_RADAR_FOUND 0x02
+static bool postprocess_radar_event(struct ath_softc *sc,
+ struct ath_radar_data *are, struct dfs_radar_pulse *drp)
+{
+ u8 rssi;
+ u16 dur;
+
+ ath_dbg(ath9k_hw_common(sc-sc_ah), ATH_DBG_DFS,
+ pulse_bw_info=0x%x, pri,ext len/rssi=(%u/%u, %u/%u)\n,
+ are-pulse_bw_info,
+ are-pulse_length_pri, are-rssi,
+ are-pulse_length_ext, are-ext_rssi);
+
+ /* Only the last 2 bits of the BW info are relevant, they indicate
+ which channel the radar was detected in.*/
+ are-pulse_bw_info = 0x03;
+
+ switch (are-pulse_bw_info) {
+ case 0:
can we define some macro for this. thanks!
+ /* Bogus bandwidth info received in descriptor,
+ so ignore this PHY error */
+ DFS_STAT_INC(sc, bwinfo_discards);
+ return false;
+ case PRI_CH_RADAR_FOUND:
+ /* radar in ctrl channel */
+ dur = are-pulse_length_pri;
+ DFS_STAT_INC(sc, pri_phy_errors);
+ /* cannot use ctrl channel RSSI
+
Re: [ath9k-devel] [RFC v2 2/2] ath9k: integrate initial DFS module
On Thu, Nov 3, 2011 at 10:15 PM, Zefir Kurtisi
zefir.kurt...@neratec.com 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 zefir.kurt...@neratec.com
wrote:
[...]
+ if (ah-caps.hw_caps ATH9K_HW_CAP_DFS) {
+ /**
+ * enable radar pulse detection
+ *
+ * TODO: do this only for DFS channels
+ */
+ ah-private_ops.set_radar_params(ah, ah-radar_conf);
can we do this something like ath9k_hw_set_radar_params?
why we need a seperate debug file for dfs, had i missed something?
My first proposal included the DFS statistics in debug.c, but Luis asked me
to keep it separated (see
http://www.mail-archive.com/ath9k-devel@lists.ath9k.org/msg06821.html). I'm
fine with both approaches, just let me know.
oh ok. please follow up with Luis's approach. thanks.
I'll add a ath9k_hw_set_radar_params() in v3.
Thanks,
Zefir
--
shafi
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] Unrealistic RSSI values being reported
Hi Daniel, On Fri, Nov 4, 2011 at 12:58 AM, Daniel Smith viscous.liq...@gmail.com 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 getting a range of values. The more interesting ones are all the frames reporting a signal of 110+ dBm. To see what is being pulled from the descriptors I dumped rs-rs_rssi to klog when the value was larger than 95. Below is a snippet showing the ranging values, i tried with the AR9382 card in 3.1.0-wl with the attached debug patch, can you please give a sample log with the patch applied and putting the interface in monitor mode. did you print/check rs_rssi somewhere else? did you also try with the latest package http://linuxwireless.org/download/compat-wireless-2.6/ Nov 3 15:00:03 dpsmith-dev-system kernel: [ 5319.907908] [ath9k]: RSSI 107 Nov 3 15:00:03 dpsmith-dev-system kernel: [ 5319.911697] [ath9k]: RSSI -61 Nov 3 15:00:03 dpsmith-dev-system kernel: [ 5319.913553] [ath9k]: RSSI -119 Nov 3 15:00:03 dpsmith-dev-system kernel: [ 5319.913562] [ath9k]: RSSI -59 Nov 3 15:00:03 dpsmith-dev-system kernel: [ 5319.913570] [ath9k]: RSSI -94 Nov 3 15:00:03 dpsmith-dev-system kernel: [ 5319.915880] [ath9k]: RSSI 119 Nov 3 15:00:03 dpsmith-dev-system kernel: [ 5319.915890] [ath9k]: RSSI -109 Nov 3 15:00:03 dpsmith-dev-system kernel: [ 5319.915898] [ath9k]: RSSI 123 Nov 3 15:00:03 dpsmith-dev-system kernel: [ 5319.917743] [ath9k]: RSSI 101 A couple of data points, 1. I have tested two different cards, one having AR9106+AR9160 and one with an AR9382. 2. It appears that it is always the same devices that this occurs for, e.g. pretty confident there are some devices that I collected that I did not see anything out of the 3-10dBm range I know 2.6.39 - 3.1 is a bit of a jump, but I wanted to push this to the community to see if there are some thoughts or opinions while I dig deeper. My next step is to see if it occurs in 3.0 which should help give me a narrow set of patches to review/bisect to see at what point this was introduced. I would suspect it to be an initval issue, but the two chips I have should have different initval sets. Any thoughts or suggestions would be greatly appreciated. dps ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi diff --git a/drivers/net/wireless/ath/ath9k/recv.c b/drivers/net/wireless/ath/ath9k/recv.c index 67b862c..378f202 100644 --- a/drivers/net/wireless/ath/ath9k/recv.c +++ b/drivers/net/wireless/ath/ath9k/recv.c @@ -1003,6 +1003,7 @@ static int ath9k_rx_skb_preprocess(struct ath_common *common, rx_status-band = hw-conf.channel-band; rx_status-freq = hw-conf.channel-center_freq; rx_status-signal = ah-noise + rx_stats-rs_rssi; + printk(\nnoise = %d, rs_rssi = %d, signal =%d, ah-noise, rx_stats-rs_rssi, rx_status-signal); rx_status-antenna = rx_stats-rs_antenna; rx_status-flag |= RX_FLAG_MACTIME_MPDU; ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] connection problem with AR928X
On Sat, Oct 29, 2011 at 11:54 AM, Changyu Li ironyma...@gmail.com wrote: Hi, I started having this problem just recently. In short, everything is fine, then no data is received, then after a while, a bunch of data is received at once, most tcp connections are not broken, some timed out though. please let us know the following things: 1.lspci -vvvxxx 2.which kernel you are using, to get the latest driver and see if its fixed try compat-wireless. did this problem after you had done some kernel upgrade? http://linuxwireless.org/en/users/Download#Where_to_download_bleeding_edge if there are any installations issues please let us know. 3. pls report back if the issue is seen in latest compat wireless Wireshark showed that I was still receiving arp broadcasts from the router, but nothing else, ie, no replies from router for pings, or tcp connections, existing connections stopped receiving packets. This problem is only present when I connect to my 2wire router, it does does not occur when I use my phone as an access point. I've been using this router for a while and this has never happened before. The router has not been updated recently. When other computers connect to the 2wire router, this problem does not occur. What information shoul I provide about my system, and how should I proceed to fix this problem? Thanks, Batman. ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] AR9285 and Thompson TG585 v8 connection problems
On Sat, Oct 29, 2011 at 9:02 PM, David Summers
at...@summers5913.freeserve.co.uk wrote:
No switches on my card. Card came already attached to the MTB when I
bought it, looks like its just the raw AR9285 chip you can see here:
http://www.qca.qualcomm.com/media/product/product_79_file1.pdf
I'll try just using each antenna alone and see if one works. So which
channel transmits can be configured in software, rather than being hard
wired?
i assume if we remove the antenna in chain0, the performance will be
bad. as per my assumption tx will always happen in chain0.(does we
have some tx diversity?)
Anyway I'll dig some more - if there is anything else I can do to help,
give a shout.
please try the attached patch in your compat wireless which disables
antenna diversity.
you can apply by patch -p1 disable-antenna-diversity.patch in your
compat wireless directory
please see in the kernel.log if the diversity is first of all enabled.
lets find out if really that because of this the problem had occurred.
usually enabling this feature indeed improves the throughput a lot.
may be its a regression, if its previously working properly.
pls make sure that both of your antenna are good and no mismatches.
some time one broken antenna can also cause a problem.
Thanks,
David.
On 27/10/11 12:23, Adrian Chadd wrote:
Wait a sec! That's still a bug. Still very a bug! (And a bug with FreeBSD
too!)
The AR9285 has two RX and one TX radio. It _can_ have:
* no antenna switch, so the RX mixing is done on the chip itself (the
A+B, A-B, A, B RX antenna diversity code) - where TX only occurs on
one antenna;
* an antenna switch, so the RX/TX can be flipped around;
* both combined.
So if you've got an AR9285 with one antenna connected, we should see
what is going on. Ie:
* does your AR9285 have an antenna switch or not;
* does your AR9285 have an issue with TX or RX.
So let's try something - can you please attach an antenna on the
_other_ antenna, just one. Let's see how it behaves?
The AR9285 antenna selection and diversity code is still a bit magic
and I think it could do with a lot better debugging and logging. So
you've found yet another case which we should handle. :)
Thanks!
Adrian
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
--
shafi
diff --git a/drivers/net/wireless/ath/ath9k/hw.c b/drivers/net/wireless/ath/ath9k/hw.c
index f16d203..eb80882 100644
--- a/drivers/net/wireless/ath/ath9k/hw.c
+++ b/drivers/net/wireless/ath/ath9k/hw.c
@@ -2282,8 +2282,12 @@ int ath9k_hw_fill_cap_info(struct ath_hw *ah)
if (ah-eep_ops-get_eeprom(ah, EEP_MODAL_VER) = 3) {
ant_div_ctl1 =
ah-eep_ops-get_eeprom(ah, EEP_ANT_DIV_CTL1);
- if ((ant_div_ctl1 0x1) ((ant_div_ctl1 3) 0x1))
+ if ((ant_div_ctl1 0x1) ((ant_div_ctl1 3) 0x1)) {
+printk(\nHELLO Antenna diversity is enabled\n);
pCap-hw_caps |= ATH9K_HW_CAP_ANT_DIV_COMB;
+printk(\nHELLO i am going to disable Antenna diversity\n);
+pCap-hw_caps = ~ATH9K_HW_CAP_ANT_DIV_COMB;
+ }
}
if (AR_SREV_9300_20_OR_LATER(ah)) {
if (ah-eep_ops-get_eeprom(ah, EEP_CHAIN_MASK_REDUCE))
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] connection problem with AR928X
On Mon, Oct 31, 2011 at 11:50 PM, changyu li ironyma...@gmail.com wrote: The problem is fixed and was not ath9k's problem. The problem was caused by arpon daemon's response to bogus packets. It was fixed by making a static entry for the default route. thanks for reporting it. adding ath9k list. Thank you. -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] Maybe a bug somewhere in the WIFI driver
On Mon, Oct 24, 2011 at 5:20 PM, BARRAL Adrien adrien.bar...@robopec.com wrote: Hi Shafi, I think the bug was corrected. I installed compat-wireless 2011-10-10 and since, no freeze happens. thank you very much for trying it out. (added ath9k list) Thank you very much. Regards, Adrien BARRAL -Message d'origine- De : Mohammed Shafi [mailto:shafi.wirel...@gmail.com] Envoyé : mercredi 12 octobre 2011 06:20 À : BARRAL Adrien Cc : ath9k-devel@lists.ath9k.org Objet : Re: [ath9k-devel] Maybe a bug somewhere in the WIFI driver On Tue, Oct 11, 2011 at 9:29 PM, BARRAL Adrien adrien.bar...@robopec.com wrote: Hello, Here is a description of my system : Linux : 2.6.35-22-generic (on a ubuntu 10.04 LTS) My wifi card is : 02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01) dmesg outputs about the wifi controller are : Oct 10 17:28:49 kernel: [ 12.546288] ath9k :02:00.0: PCI INT A - GSI 17 (level, low) - IRQ 17 Oct 10 17:28:49 kernel: [ 12.606040] HDA Intel :00:1b.0: PCI INT A - GSI 16 (level, low) - IRQ 16 Oct 10 17:28:49 kernel: [ 12.653486] phy0: Atheros AR9285 Rev:2 mem=0xf8e6, irq=17 I am using an atheros Wifi Card in ad-hoc mode, I create my ad-hoc network with two differents ways : 1. Thanks to the following commands : ifconfig wlan2 down iwconfig wlan2 mode Ad-Hoc iwconfig wlan2 essid Toto ifconfig wlan2 up 2. Thanks to the ubuntu network manager Create a New Network function's. The way I use to create the network doesn't matter. A few minutes after the AdHoc network is created, my system freeze. I have got the following message in /var/log/kernel : - START OF MESSAGE -- Oct 11 09:44:52 kernel: [ 840.290670] BUG: unable to handle kernel NULL pointer dereference at 0080 Oct 11 09:44:52 kernel: [ 840.290682] IP: [c020cb7c] __kmalloc_track_caller+0x6c/0x170 Oct 11 09:44:52 kernel: [ 840.290697] *pde = 7e630067 Oct 11 09:44:52 kernel: [ 840.290703] Oops: [#1] SMP Oct 11 09:44:52 kernel: [ 840.290709] last sysfs file: /sys/devices/pci:00/:00:1e.0/:04:0b.0/local_cpus Oct 11 09:44:52 kernel: [ 840.290716] Modules linked in: ipt_MASQUERADE xt_state ipt_REJECT xt_tcpudp iptable_filter nf_nat_h323 nf_conntrack_h323 nf_nat_pptp nf_conntrack_pptp nf_conntrack_proto_gre nf_nat_proto_gre nf_nat_tftp nf_conntrack_tftp nf_nat_sip nf_conntrack_sip nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables x_tables nls_iso8859_1 nls_cp437 vfat fat parport_pc ppdev snd_hda_codec_nvhdmi binfmt_misc snd_hda_codec_realtek snd_hda_intel snd_hda_codec nvidia(P) arc4 snd_usb_audio ath9k snd_hwdep snd_usbmidi_lib snd_pcm ath9k_common snd_seq_midi ath9k_hw joydev snd_rawmidi ath mac80211 snd_seq_midi_event snd_seq snd_timer usbhid snd_seq_device cfg80211 uvcvideo intel_agp usb_storage hid snd cdc_acm psmouse videodev v4l1_compat led_class serio_raw coretemp xhci_hcd agpgart soundcore snd_page_alloc lp parport r8169 mii Oct 11 09:44:52 kernel: [ 840.290822] Oct 11 09:44:52 kernel: [ 840.290829] Pid: 757, comm: phy0 Tainted: P 2.6.35-22-generic #33-Ubuntu To be filled by O.E.M./To Be Filled By O.E.M. Oct 11 09:44:52 kernel: [ 840.290837] EIP: 0060:[c020cb7c] EFLAGS: 00010002 CPU: 3 Oct 11 09:44:52 kernel: [ 840.290844] EIP is at __kmalloc_track_caller+0x6c/0x170 Oct 11 09:44:52 kernel: [ 840.290849] EAX: c2705aec EBX: c07c6888 ECX: c07c6888 EDX: Oct 11 09:44:52 kernel: [ 840.290854] ESI: 00d0 EDI: 0080 EBP: f3f6bebc ESP: f3f6be94 Oct 11 09:44:52 kernel: [ 840.290860] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 Oct 11 09:44:52 kernel: [ 840.290866] Process phy0 (pid: 757, ti=f3f6a000 task=f3ec3f70 task.ti=f3f6a000) Oct 11 09:44:52 kernel: [ 840.290870] Stack: Oct 11 09:44:52 kernel: [ 840.290874] c2705a98 c04ece6e c04eddf8 0246 00d0 01c4 f35b5300 Oct 11 09:44:52 kernel: [ 840.290886] 0 00d0 00ff f3f6bedc c04ece98 c07c64d0 00c0 f35b9000 Oct 11 09:44:52 kernel: [ 840.290900] 0 f080d000 f3f6bef8 c04eddf8 f080d000 f3dc8480 Oct 11 09:44:52 kernel: [ 840.290914] Call Trace: Oct 11 09:44:52 kernel: [ 840.290924] [c04ece6e] ? __alloc_skb+0x2e/0x100 Oct 11 09:44:52 kernel: [ 840.290931] [c04eddf8] ? skb_copy+0x38/0x90 Oct 11 09:44:52 kernel: [ 840.290938] [c04ece98] ? __alloc_skb+0x58/0x100 Oct 11 09:44:52 kernel: [ 840.290944] [c04eddf8] ? skb_copy+0x38/0x90 Oct 11 09:44:52 kernel: [ 840.290976] [f8e3714d] ? ieee80211_rx_mgmt_probe_req+0xed/0x130 [mac80211] Oct 11 09:44:52 kernel: [ 840.291004] [f8e3810d] ? ieee80211_ibss_rx_queued_mgmt+0x3d/0xf0
Re: [ath9k-devel] Fwd: Kernel warning in ath9k related to wpa_supplicant scanning
On Fri, Oct 21, 2011 at 1:57 AM, Bryan Phillippe b...@terran.org wrote:
Thoughts on who's to blame and how to resolve?
its the driver, the rate is is taken as a HT rate,
if (rx_stats-rs_rate 0x80) {
/* HT rate */
rxs-flag |= RX_FLAG_HT;
if (rx_stats-rs_flags ATH9K_RX_2040)
rxs-flag |= RX_FLAG_40MHZ;
if (rx_stats-rs_flags ATH9K_RX_GI)
rxs-flag |= RX_FLAG_SHORT_GI;
rxs-rate_idx = rx_stats-rs_rate 0x7f;
return 0;
}
please provide lspci so that we can get the descriptor dump for rx-status.
also please whether your consistently getting elaborating how to
recreate the issue.
thanks.
Thanks,
--
-bp
Begin forwarded message:
From: B. J.
Date: October 20, 2011 1:26:21 PM PDT
To: hos...@lists.shmoo.com
Subject: Kernel warning in ath9k related to wpa_supplicant scanning
This is with wpa_supplicant-0.7.3 and compat-wireless-2011-10-10:
...
nl80211: Event message available
nl80211: New scan results available
Received scan results (0 BSSes)
BSS: Start scan result update 6
New scan results available
Selecting BSS from priority group 0
Try to find WPA-enabled AP
Try to find non-WPA AP
No suitable network found
Setting scan request: 5 sec 0 usec
RTM_NEWLINK: operstate=0 ifi_flags=0x3 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
Starting AP scan for wildcard SSID
nl80211: Scan SSID - hexdump_ascii(len=0): [NULL]
Scan requested (ret=0) - scan timeout 30 seconds
nl80211: Event message available
nl80211: Scan trigger
[ cut here ]
WARNING: at
/home/bp/P4/UTM-mainline/components/kernel/build/richland/ath9k/net/mac80211/rx.c:3002
ieee80211_rx+0xf4/0x9dc [mac80211]()
Rate marked as an HT rate but passed status-rate_idx is not an MCS index
[0-76]: 93 (0x5d)
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
--
shafi
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] Performance problems with the AR9287
On Thu, Oct 20, 2011 at 3:56 AM, Mitch Davis mjd+ath9k@afork.com wrote: Hello, I am writing to you all on behalf of the many Fedora users with AR9287 chips. In Fedora 15, wireless performance with the AR9287 is terrible. Here's a bug about it: https://bugzilla.redhat.com/show_bug.cgi?id=702722 It's now on Fedora's common bugs list: http://fedoraproject.org/wiki/Common_F15_bugs#Poor_transfer_speeds_with_Atheros-based_wireless_chipsets I have tried compat-wireless and compat-wireless-next (see comment 15) and neither gives any improvement. This chip works well with the driver that was shipped in Fedora 14 (kernel 2.6.35). Can someone help me find the problem please? I am happy to do debugging and information collection, but I'll need some hand-holding. as Ben, kindly verify this issue can be recreate in the latest compat wireless or wireless-testing(it would take time to compile the kernel). http://linuxwireless.org/en/developers/Documentation/git-guide i will try my level tbest o badly get some time to recreate the issue in a clean environment. Thank you, Mitch. ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] error:Segmentation fault after compiling and move ath9k
On Wed, Oct 19, 2011 at 8:56 PM, Pavel Roskin pro...@gnu.org wrote: On Wed, 19 Oct 2011 09:53:04 +0530 Mohammed Shafi shafi.wirel...@gmail.com wrote: Hi Wendy, sorry i have not tried on working with OpenWrt. please ask in the OpenWrt list. i had also Cced Felix and Adrian, Pavel Roskin who might know about this. may be you can just try with another OpenWrt package which has some latest compat-wireless. Actually, I'm not involved with OpenWRT, I just use it on some of my routers. thanks, shafi On Wed, Oct 19, 2011 at 7:00 AM, wendy_life wendy_l...@yeah.net wrote: ** Hi shafi ！ Recently,I got a stupid mistake that kept puzzling me for long time.Help！ Things are like those as follow: OS：Openwrt backfire Compile target:ath9k(compat-wireless-2011-06-22) That's several months old! Platform target:UBNT RouterStation I chose ath9k at the time of make menuconfig,and then I got the ko files as follow Kmo-ath: ath.ko** Kmod-ath9k: ath9k.ko Kmod-ath9k_common: ath9k_hw.ko ath9k_common.ko Kmod-cfg80211: cfg80211.ko compat_firmware_class.ko compat.ko Kmod-mac80211: mac80211.ko When I replace thess .ko files to target platform ,reboot and wifi(wireless start command ), I got this error prompt: Segmentation fault Unless there is a kernel log with indications that it comes from ath9k, there is no point in posting that to the ath9k-devel list, let alone copying individual developers. And even then, I would prefer somebody in the OpenWRT list to triage the problem first. thanks a lot for your inputs! -- Regards, Pavel Roskin -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] error:Segmentation fault after compiling and move ath9k
Hi Wendy, sorry i have not tried on working with OpenWrt. please ask in the OpenWrt list. i had also Cced Felix and Adrian, Pavel Roskin who might know about this. may be you can just try with another OpenWrt package which has some latest compat-wireless. thanks, shafi On Wed, Oct 19, 2011 at 7:00 AM, wendy_life wendy_l...@yeah.net wrote: ** Hi shafi ！ Recently,I got a stupid mistake that kept puzzling me for long time.Help！ Things are like those as follow: OS：Openwrt backfire Compile target:ath9k(compat-wireless-2011-06-22) Platform target:UBNT RouterStation I chose ath9k at the time of make menuconfig,and then I got the ko files as follow Kmo-ath:ath.ko** Kmod-ath9k: ath9k.ko Kmod-ath9k_common: ath9k_hw.ko ath9k_common.ko Kmod-cfg80211: cfg80211.ko compat_firmware_class.ko compat.ko Kmod-mac80211: mac80211.ko When I replace thess .ko files to target platform ,reboot and wifi(wireless start command ), I got this error prompt: Segmentation fault At the same time , I also got .ipk files after compiling as follow kmod-ath9k-common_2.6.32.27+2011-06-22-2_ar71xx.ipk kmod-ath9k_2.6.32.27+2011-06-22-2_ar71xx.ipk kmod-ath_2.6.32.27+2011-06-22-2_ar71xx.ipk kmod-cfg80211_2.6.32.27+2011-06-22-2_ar71xx.ipk kmod-mac80211_2.6.32.27+2011-06-22-2_ar71xx.ipk I try to remove original modules and setup these new .ipk files,reboot and wifi. I got the same me error prompt:Segmentation fault At both processes,I have not changed any code since downloading source code of OpenWrt Backfire(including compat-wireless 2011-06-22),just compiled one time. What is the problem? what is the right process of modifying ath9k driver code and taking compiled modules effect on target platform? 2011-10-19 -- Best Wishes~~ ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] Can't associate with a particular AP
On Sat, Oct 15, 2011 at 10:21 AM, Julien Valroff jul...@kirya.net wrote: Hi Mohammed, Le mercredi 05 oct. 2011 à 06:24:06 (+0200 CEST), Julien Valroff a écrit : Le mardi 04 oct. 2011 à 20:35:14 (+0200 CEST), Julien Valroff a écrit : Le mardi 04 oct. 2011 à 07:46:58 (+0200 CEST), Mohammed Shafi a écrit : [...] enabling mac80211 debugs will also be useful. you said that the issue happens without security, and also only when the AP router is already connected by another station. in the other thread it was mentioned that the problem occurs only when its a wireless router. I am compiling a kernel with mac80211 debug features enabled, will make further tests within the next week-end and report. Please find attached the kernel log with mac80211 debug enabled. Have you been able to reproduce the issue on your side? sorry no :(, i used compat-wireless-2011-10-10 and i made sure that my ar9285 is to be connected to an AP which is already connected by another station. i did not get the issue. the environment is a less a nosier one and the channel is 7 same as yours. just doubt, why your tx-power is only 14dbm while mine has 27 dbm in iwconfig. i assume its just a random sample. if its consistently 14dbm when you connect your AR9285 station first, we need to look at that. Cheers, Julien -- .''`. Julien Valroff ~ jul...@kirya.net ~ jul...@debian.org : :' : Debian Developer Free software contributor `. `'` http://www.kirya.net/ `- 4096R/ E1D8 5796 8214 4687 E416 948C 859F EF67 258E 26B1 -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] Can't associate with a particular AP
On Sun, Oct 16, 2011 at 9:01 PM, Adrian Chadd adr...@freebsd.org wrote: Can you please grab a third device and grab a dump of the actual probe/association frames? looks like the tx-power is constrained due to regulatory (or) power constraint element from AP? I think it'd be helpful to see what's changed. Adrian -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] HowTo put 40MHz and short GI into effect?
On Wed, Oct 12, 2011 at 6:31 AM, songzhang songzh...@tju.edu.cn wrote: Thanks a lot Mohammed! I change 40MHz preferences,HT40+ in wireless file,and then it starting running!wow! That is to say my card can run at MCS 15 in 40MHz and short GI,300Mbps.But there is another problem,the throughput is not more than 150Mbps and MCS can not keep at 15 for long time. I doubt if STBC or antenna cause that problems and how configure TX-STBC and antenna(space streams)? both Tx/Rx STBC are not supported. i have not tested ar9160, please try to add more pairs in case you are running iperf. 2011-10-12 songzhang On Tue, Oct 11, 2011 at 7:25 PM, songzhang songzh...@tju.edu.cn wrote: Hello all, Using SR71-A with atheros 9160 chip and ath9k (2011-6-25 conpat),I still can not put 40MHz and short GI into effect.Right now ,I only get MCS15 in 20MHz,130Mbps. My question what should I configure to put?40MHz?and?short?GI?into?effect? short GI HT20 is not supported for AR9160(support only for AR9287 1.1 or later chipsets). HT40 should work fine, if we configure the AP in HT40 mode -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] need help debugging/pinning down obscure freezes/hangs using AR9287
On Wed, Oct 12, 2011 at 12:08 AM, Philipp Raich philipp.ra...@gmail.com wrote: Hi. When using the ath9k module my system freezes in less than a few minutes, and I'm not able to find out why. Could someone help me by telling me where to find useful information on where or why this happens? (Or should i begin to insert my own debugging-output in the code???) please provide us more information under what scenario the freeze happens(your kernel version in which you are running compat-wireless). i just connected to a secure AP and pinged it.(AR987 rev 01) also provide lspci -xxx The crashes almost disappear if i crank the TX-Power up and thus improve the signal quality (i think this could be a hint), and almost only appear when the connection is under heavy load (firing up a youtube-video works reliably most of the time), but may also appear at any given time. [To me it sounds like something the module expects to be there gets lost... (null-pointer anyone?)] Even worse, I do not have a working SysRq-Key on this machine (remapping other key did not work, PS/2-keyboard won't work), but I think it would be useless anyway, the tty running Xorg usually shows a beautiful color-pattern as soon as the crashes occur, when running a serial console as it happens, the screen just freezes. I used the almost recent version of ath9k (via compat-wireless tarball '2011-10-10') and enabled debugging as far as I could get it to work (I see the nodes under /sys/kernel/debug/ieee80211/phy0/ath9k but could not find anything really helpful there... Mostly because I have no idea where to look and what the numbers mean I was not able to find any insightful documentation). capturing the crash with net console will help. those debug info may not be very useful for crash. http://www.mjmwired.net/kernel/Documentation/networking/netconsole.txt What would be most interesting to me is, what happens before the crashes occur? What is ath9k doing? The usual kernel-debugging stuff... I thought I saw debug-printks in the code, and hoped to enable it via 'modprobe ath9k debug=0x', but with no luck. Was it disabled in the recent past? Did I miss a step in enabling it? please read http://linuxwireless.org/en/users/Drivers/ath9k/debug. Can somebody give me a little guidance on what to do next? I would really like to improve the situation for me and everyone else, or at least help as much as I can, and I think I need a hint. Thanks, Philipp Raich ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] need help debugging/pinning down obscure freezes/hangs using AR9287
On Wed, Oct 12, 2011 at 7:23 PM, Peter Stuge pe...@stuge.se wrote: Philipp Raich wrote: I would really like to improve the situation for me and everyone else, or at least help as much as I can, and I think I need a hint. From experience I know that Atheros does not like to work with end users on debugging issues like this, even if end users happen to be competent. The prefered modus operandi is to attempt to reproduce issues internally, and if that is successful then some time later there usually comes a patch into wireless-testing.git. This is of course useless for corner case problems. people do take efforts to recreate remote issues. there are several issues that were properly fixed. i accept that there may be few issues which may not be fixed. This mailing list is a lot like first-line support. You usually don't get quality engineer time from Atheros here. I can understand that, because remote debugging is a tremendous pain. But it's also the only way to resolve odd problems. any developer would be very happy if they can find a bug and fix it. obviously we need to parallely work on other commitments. would you please stop complaining and provide some help ? all you try to do is focus only on the *negative things*. there are several issues we find by ourselves and send patches. i do take a point we have to improve on this. i will surely work on it. thanks! I would recommend that you try to reproduce using FreeBSD. I'm unsure if the driver there supports AR9287, but if it does I think you will be able to get good help thanks to Adrian, the main fbsd driver developer, who is also active on this list, but he's obviously not working on the Linux driver. :) //Peter ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] need help debugging/pinning down obscure freezes/hangs using AR9287
On Wed, Oct 12, 2011 at 8:26 PM, Peter Stuge pe...@stuge.se wrote: Mohammed Shafi wrote: From experience I know that Atheros does not like to work with end users on debugging issues like this, even if end users happen to be competent. The prefered modus operandi is to attempt to reproduce issues internally, and if that is successful then some time later there usually comes a patch into wireless-testing.git. This is of course useless for corner case problems. people do take efforts to recreate remote issues. there are several issues that were properly fixed. I absolutely agree! I tried to also acknowledge that, but I'm happy to be more clear: Atheros takes efforts to reproduce issues and in many cases already it has resulted in fixes. The problem is that remote issues can be impossible or too difficult to reproduce. i accept that there may be few issues which may not be fixed. I know. I don't. I was actually shocked to meet this attitude when coming into the ath9k community. I didn't think anyone would work on open source without the desire to make it perfect. I was too naive. I completely understand the attitude, I just disagree with it. its not that i meant we cannot fix those issues, i meant that there may be certain issues which might not yet be discovered. This mailing list is a lot like first-line support. You usually don't get quality engineer time from Atheros here. I can understand that, because remote debugging is a tremendous pain. But it's also the only way to resolve odd problems. any developer would be very happy if they can find a bug and fix it. Yes of course. The problem is that developers alone can not reasonably quickly find and fix bugs that depend on a particular remote RF environment. obviously we need to parallely work on other commitments. Remote debugging is a pain, it takes a lot of time, and I understand that there is no time for it. Adding to this, it might also require sharing whatever proprietary or FCC-forbidden information with consumers, and that of course rules it out completely. would you please stop complaining and provide some help ? It took me many months time to get an idea of the ath9k community, and I would have appreciated tremendously if someone had explained to me how things worked and what I could expect, so that I could take independent action accordingly. I believe I help people when I talk about how this community works. sorry, this community works much better than what you speak about it. all you try to do is focus only on the *negative things*. I try to focus on facts. Facts are negative sometimes. Some facts may be unintentional, but they are facts nevertheless. When I read an email with a request for help with what seems to be a corner case problem (otherwise it would have been fixed already, because ath9k works really well for many users) then I think it is important to talk about what the facts are regarding debugging and the information flow that supports debugging, to allow efficient resolution of the problem situation. A fact is that there is little to no public information exchange on developer level with Atheros (e.g. on this mailing list) and another fact is that this is quite the opposite of what I expected when subscribing to the list. I do find these facts tremendously negative, but there's not much I can do. Even if I were to become involved as a developer I couldn't do anything about it. I could work on the code, but I couldn't change the flow of information. I don't have time to work on the code, I do so in enough other places already, and besides I have very little interest to work on the code when information can not flow to support maximum development and debugging efficiency. there are several issues we find by ourselves and send patches. Certainly! I never said anything about this. There are continuously updates and improvements at the very least for the newest hardware but probably also for older hardware, although e.g. Luis has mentioned that he is interested only in the newest hardware. i do take a point we have to improve on this. i will surely work on it. thanks! It's impossible for third party such as myself to say if and how much Atheros needs to improve on finding issues internally. I expect that you already do reviews internally before proposing patches for wireless-testing.git and so on, and of course you have test labs which provide developers with problem reports, but none of this matters for issues that have not yet been encountered, such as when a user reports an unseen corner case problem. The kicker is of course that what may first seem to be just a corner case problem can end up being or revealing a much more important problem. I would recommend that you try to reproduce using FreeBSD. I'm unsure if the driver there supports AR9287, but if it does I think you will be able to get good help
Re: [ath9k-devel] AR9380 appears as product id 0xABCD instead of 0x0030
true its an already reported platform specific issue, usually they use this id for emulation testing. as a workaround this PID has to be added to support this card in that specific platform On Mon, Oct 10, 2011 at 8:06 PM, Adrian Chadd adr...@freebsd.org wrote: .. sounds like another PCI bus setup/reset problem. Sigh. :) Adrian ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] AR9380 appears as product id 0xABCD instead of 0x0030
On Tue, Oct 11, 2011 at 6:06 PM, Daniel Golle dgo...@allnet.de wrote:
Sure, that's what I did already to make it work at least a bit, but run into
DMA
problems once there was any serious traffic (using Kernel 2.6.39 and
compat-wireless 2011-06-20)
Kernel 3.0.4 with compat-wireless 2011-10-05 seems to work quite nice, at
least
for now... I'll continue testing that in the next days.
please try to see the DMA problems are fixed in latest compat
http://linuxwireless.org/en/users/Download#Where_to_download_bleeding_edge
On 10/11/2011 09:58 AM, Wojciech Dubowik wrote:
Hi!
I want to use an AR9380 mini pci-e module on kirkwood. under x86 the
module
works fine and appears as product-id 0x0030, on kirkwood the same
module shows
up as product-id 0xabcd.
Anyone knows possible reasons for this to happen?
(First I suspected there could be an PCI expansion ROM executed by
the x86 BIOS,
that doesn't seem to be that case.)
Any hints welcome :)
You could use sth like that in your setup.
---
Index: compat-wireless-2011-05-27/drivers/net/wireless/ath/ath9k/pci.c
===
--- compat-wireless-2011-05-27.orig/drivers/net/wireless/ath/ath9k/pci.c
2011-05-31 21:02:34.0 +0200
+++ compat-wireless-2011-05-27/drivers/net/wireless/ath/ath9k/pci.c
2011-06-06 12:58:57.578412992 +0200
@@ -30,6 +30,7 @@
{ PCI_VDEVICE(ATHEROS, 0x002D) }, /* PCI */
{ PCI_VDEVICE(ATHEROS, 0x002E) }, /* PCI-E */
{ PCI_VDEVICE(ATHEROS, 0x0030) }, /* PCI-E AR9300 */
+ { PCI_VDEVICE(ATHEROS, 0xABCD) }, /* PCI-E AR9380 */
{ PCI_VDEVICE(ATHEROS, 0x0032) }, /* PCI-E AR9485 */
{ 0 }
};
Index: compat-wireless-2011-05-27/drivers/net/wireless/ath/ath9k/hw.c
===
--- compat-wireless-2011-05-27.orig/drivers/net/wireless/ath/ath9k/hw.c
2011-06-06 12:58:50.0 +0200
+++ compat-wireless-2011-05-27/drivers/net/wireless/ath/ath9k/hw.c
2011-06-06 13:00:12.568412970 +0200
@@ -653,6 +653,7 @@
case AR2427_DEVID_PCIE:
case AR9300_DEVID_PCIE:
case AR9300_DEVID_AR9485_PCIE:
+ case AR9300_DEVID_AR9380_PCIE:
case AR9300_DEVID_AR9330:
case AR9300_DEVID_AR9340:
break;
Index: compat-wireless-2011-05-27/drivers/net/wireless/ath/ath9k/hw.h
===
--- compat-wireless-2011-05-27.orig/drivers/net/wireless/ath/ath9k/hw.h
2011-06-06 12:58:50.0 +0200
+++ compat-wireless-2011-05-27/drivers/net/wireless/ath/ath9k/hw.h
2011-06-06 12:58:57.578412992 +0200
@@ -44,6 +44,7 @@
#define AR9287_DEVID_PCIE 0x002e
#define AR9300_DEVID_PCIE 0x0030
#define AR9300_DEVID_AR9340 0x0031
+#define AR9300_DEVID_AR9380_PCIE 0xabcd
#define AR9300_DEVID_AR9485_PCIE 0x0032
#define AR9300_DEVID_AR9330 0x0035
---
It has worked for me on kirkwood platform.
Wojtek
Cheers
Daniel
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
--
shafi
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] HowTo put 40MHz and short GI into effect?
On Tue, Oct 11, 2011 at 7:25 PM, songzhang songzh...@tju.edu.cn wrote: Hello all, Using SR71-A with atheros 9160 chip and ath9k (2011-6-25 conpat),I still can not put 40MHz and short GI into effect.Right now ,I only get MCS15 in 20MHz,130Mbps. My question what should I configure to put 40MHz and short GI into effect? short GI HT20 is not supported for AR9160(support only for AR9287 1.1 or later chipsets). HT40 should work fine, if we configure the AP in HT40 mode Thanks for giving back! 2011-10-11 songzhang ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] Maybe a bug somewhere in the WIFI driver
On Tue, Oct 11, 2011 at 9:29 PM, BARRAL Adrien adrien.bar...@robopec.com wrote: Hello, Here is a description of my system : Linux : 2.6.35-22-generic (on a ubuntu 10.04 LTS) My wifi card is : 02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01) dmesg outputs about the wifi controller are : Oct 10 17:28:49 kernel: [ 12.546288] ath9k :02:00.0: PCI INT A - GSI 17 (level, low) - IRQ 17 Oct 10 17:28:49 kernel: [ 12.606040] HDA Intel :00:1b.0: PCI INT A - GSI 16 (level, low) - IRQ 16 Oct 10 17:28:49 kernel: [ 12.653486] phy0: Atheros AR9285 Rev:2 mem=0xf8e6, irq=17 I am using an atheros Wifi Card in ad-hoc mode, I create my ad-hoc network with two differents ways : 1. Thanks to the following commands : ifconfig wlan2 down iwconfig wlan2 mode Ad-Hoc iwconfig wlan2 essid Toto ifconfig wlan2 up 2. Thanks to the ubuntu network manager Create a New Network function's. The way I use to create the network doesn't matter. A few minutes after the AdHoc network is created, my system freeze. I have got the following message in /var/log/kernel : - START OF MESSAGE -- Oct 11 09:44:52 kernel: [ 840.290670] BUG: unable to handle kernel NULL pointer dereference at 0080 Oct 11 09:44:52 kernel: [ 840.290682] IP: [c020cb7c] __kmalloc_track_caller+0x6c/0x170 Oct 11 09:44:52 kernel: [ 840.290697] *pde = 7e630067 Oct 11 09:44:52 kernel: [ 840.290703] Oops: [#1] SMP Oct 11 09:44:52 kernel: [ 840.290709] last sysfs file: /sys/devices/pci:00/:00:1e.0/:04:0b.0/local_cpus Oct 11 09:44:52 kernel: [ 840.290716] Modules linked in: ipt_MASQUERADE xt_state ipt_REJECT xt_tcpudp iptable_filter nf_nat_h323 nf_conntrack_h323 nf_nat_pptp nf_conntrack_pptp nf_conntrack_proto_gre nf_nat_proto_gre nf_nat_tftp nf_conntrack_tftp nf_nat_sip nf_conntrack_sip nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables x_tables nls_iso8859_1 nls_cp437 vfat fat parport_pc ppdev snd_hda_codec_nvhdmi binfmt_misc snd_hda_codec_realtek snd_hda_intel snd_hda_codec nvidia(P) arc4 snd_usb_audio ath9k snd_hwdep snd_usbmidi_lib snd_pcm ath9k_common snd_seq_midi ath9k_hw joydev snd_rawmidi ath mac80211 snd_seq_midi_event snd_seq snd_timer usbhid snd_seq_device cfg80211 uvcvideo intel_agp usb_storage hid snd cdc_acm psmouse videodev v4l1_compat led_class serio_raw coretemp xhci_hcd agpgart soundcore snd_page_alloc lp parport r8169 mii Oct 11 09:44:52 kernel: [ 840.290822] Oct 11 09:44:52 kernel: [ 840.290829] Pid: 757, comm: phy0 Tainted: P 2.6.35-22-generic #33-Ubuntu To be filled by O.E.M./To Be Filled By O.E.M. Oct 11 09:44:52 kernel: [ 840.290837] EIP: 0060:[c020cb7c] EFLAGS: 00010002 CPU: 3 Oct 11 09:44:52 kernel: [ 840.290844] EIP is at __kmalloc_track_caller+0x6c/0x170 Oct 11 09:44:52 kernel: [ 840.290849] EAX: c2705aec EBX: c07c6888 ECX: c07c6888 EDX: Oct 11 09:44:52 kernel: [ 840.290854] ESI: 00d0 EDI: 0080 EBP: f3f6bebc ESP: f3f6be94 Oct 11 09:44:52 kernel: [ 840.290860] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 Oct 11 09:44:52 kernel: [ 840.290866] Process phy0 (pid: 757, ti=f3f6a000 task=f3ec3f70 task.ti=f3f6a000) Oct 11 09:44:52 kernel: [ 840.290870] Stack: Oct 11 09:44:52 kernel: [ 840.290874] c2705a98 c04ece6e c04eddf8 0246 00d0 01c4 f35b5300 Oct 11 09:44:52 kernel: [ 840.290886] 0 00d0 00ff f3f6bedc c04ece98 c07c64d0 00c0 f35b9000 Oct 11 09:44:52 kernel: [ 840.290900] 0 f080d000 f3f6bef8 c04eddf8 f080d000 f3dc8480 Oct 11 09:44:52 kernel: [ 840.290914] Call Trace: Oct 11 09:44:52 kernel: [ 840.290924] [c04ece6e] ? __alloc_skb+0x2e/0x100 Oct 11 09:44:52 kernel: [ 840.290931] [c04eddf8] ? skb_copy+0x38/0x90 Oct 11 09:44:52 kernel: [ 840.290938] [c04ece98] ? __alloc_skb+0x58/0x100 Oct 11 09:44:52 kernel: [ 840.290944] [c04eddf8] ? skb_copy+0x38/0x90 Oct 11 09:44:52 kernel: [ 840.290976] [f8e3714d] ? ieee80211_rx_mgmt_probe_req+0xed/0x130 [mac80211] Oct 11 09:44:52 kernel: [ 840.291004] [f8e3810d] ? ieee80211_ibss_rx_queued_mgmt+0x3d/0xf0 [mac80211] Oct 11 09:44:52 kernel: [ 840.291012] [c04ec5c0] ? skb_dequeue+0x50/0x70 Oct 11 09:44:52 kernel: [ 840.291039] [f8e38211] ? ieee80211_ibss_work+0x51/0xd0 [mac80211] Oct 11 09:44:52 kernel: [ 840.291049] [c0161a4e] ? run_workqueue+0x8e/0x150 Oct 11 09:44:52 kernel: [ 840.291075] [f8e381c0] ? ieee80211_ibss_work+0x0/0xd0 [mac80211] Oct 11 09:44:52 kernel: [ 840.291084] [c0161b94] ? worker_thread+0x84/0xe0 Oct 11 09:44:52 kernel: [ 840.291092] [c0165e10] ? autoremove_wake_function+0x0/0x50 Oct 11 09:44:52
Re: [ath9k-devel] [RFC 2/6] ath9k: add DFS debug flag
On Tue, Oct 4, 2011 at 2:01 PM, Zefir Kurtisi zefir.kurt...@neratec.com wrote:
On 10/03/2011 08:15 PM, Luis R. Rodriguez wrote:
On Mon, Oct 3, 2011 at 3:29 AM, Zefir Kurtisi zefir.kurt...@neratec.com
wrote:
Signed-off-by: Zefir Kurtisi zefir.kurt...@neratec.com
---
drivers/net/wireless/ath/ath.h | 34 ++
1 files changed, 18 insertions(+), 16 deletions(-)
diff --git a/drivers/net/wireless/ath/ath.h b/drivers/net/wireless/ath/ath.h
index 6d56532..34d4da1 100644
--- a/drivers/net/wireless/ath/ath.h
+++ b/drivers/net/wireless/ath/ath.h
@@ -211,6 +211,7 @@ ath_printk(const char *level, struct ath_common
*common, const char *fmt, ...);
* @ATH_DBG_HWTIMER: hardware timer handling
* @ATH_DBG_BTCOEX: bluetooth coexistance
* @ATH_DBG_BSTUCK: stuck beacons
+ * @ATH_DBG_DFS: radar datection
* @ATH_DBG_ANY: enable all debugging
*
* The debug level is used to control the amount and type of debugging
output
@@ -220,22 +221,23 @@ ath_printk(const char *level, struct ath_common
*common, const char *fmt, ...);
* entry.
*/
enum ATH_DEBUG {
- ATH_DBG_RESET = 0x0001,
- ATH_DBG_QUEUE = 0x0002,
- ATH_DBG_EEPROM = 0x0004,
- ATH_DBG_CALIBRATE = 0x0008,
- ATH_DBG_INTERRUPT = 0x0010,
- ATH_DBG_REGULATORY = 0x0020,
- ATH_DBG_ANI = 0x0040,
- ATH_DBG_XMIT = 0x0080,
- ATH_DBG_BEACON = 0x0100,
- ATH_DBG_CONFIG = 0x0200,
- ATH_DBG_FATAL = 0x0400,
- ATH_DBG_PS = 0x0800,
- ATH_DBG_HWTIMER = 0x1000,
- ATH_DBG_BTCOEX = 0x2000,
- ATH_DBG_WMI = 0x4000,
- ATH_DBG_BSTUCK = 0x8000,
+ ATH_DBG_RESET = BIT(0),
+ ATH_DBG_QUEUE = BIT(1),
+ ATH_DBG_EEPROM = BIT(2),
+ ATH_DBG_CALIBRATE = BIT(3),
+ ATH_DBG_INTERRUPT = BIT(4),
+ ATH_DBG_REGULATORY = BIT(5),
+ ATH_DBG_ANI = BIT(6),
+ ATH_DBG_XMIT = BIT(7),
+ ATH_DBG_BEACON = BIT(8),
+ ATH_DBG_CONFIG = BIT(9),
+ ATH_DBG_FATAL = BIT(10),
+ ATH_DBG_PS = BIT(11),
+ ATH_DBG_HWTIMER = BIT(12),
+ ATH_DBG_BTCOEX = BIT(13),
+ ATH_DBG_WMI = BIT(14),
+ ATH_DBG_BSTUCK = BIT(15),
+ ATH_DBG_DFS = BIT(16),
ATH_DBG_ANY = 0x
Split this into two patches, one to convert stuff to BIT(foo) and the
other one to add ATH_DBG_DFS
In fact, the BIT values will be reverted, since it is easier to have the hex
values when setting debug mask than the bit position (for me at least).
yes, i agree having hex values is much better. especially when we
have a combination of 2 or 3 debug masks for debugging issues.
thanks!
Luis
Thanks,
Zefir
--
To unsubscribe from this list: send the line unsubscribe linux-wireless in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
shafi
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] Can't associate with a particular AP
On Mon, Oct 3, 2011 at 10:06 PM, Julien Valroff jul...@kirya.net wrote: [ please CC me when replying, I am not subscribed to the list ] Hi, I have recently purchased a new laptop (Asus X93S) with an Atheros AR9285 wireless chip which obviously uses the ath9k module. When connecting to the AP of my router, everything works as expected provided no other PC has already been connected to the AP. If that is not the case, I have to reboot the router and make sure my new laptop is the first to connect. Here is the log of such a failing connection: Oct 1 08:55:41 ares kernel: [ 8774.854934] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Oct 1 08:55:41 ares NetworkManager[1830]: info (wlan0): supplicant interface state: associating - associated Oct 1 08:55:48 ares kernel: [ 8781.880987] wlan0: deauthenticated from ce:67:c3:86:34:80 (Reason: 15) Oct 1 08:55:49 ares wpa_supplicant[1859]: CTRL-EVENT-DISCONNECTED bssid=ce:67:c3:86:34:80 reason=15 Oct 1 08:55:49 ares kernel: [ 8781.931122] cfg80211: Calling CRDA to update world regulatory domain Oct 1 08:55:49 ares NetworkManager[1830]: info (wlan0): supplicant interface state: associated - disconnected Oct 1 08:55:49 ares NetworkManager[1830]: info (wlan0): supplicant interface state: disconnected - scanning Oct 1 08:55:50 ares wpa_supplicant[1859]: Trying to authenticate with ce:67:c3:86:34:80 (SSID='Kirya' freq=2422 MHz) Oct 1 08:55:50 ares NetworkManager[1830]: info (wlan0): supplicant interface state: scanning - authenticating Oct 1 08:55:50 ares kernel: [ 8783.091580] wlan0: authenticate with ce:67:c3:86:34:80 (try 1) Oct 1 08:55:50 ares wpa_supplicant[1859]: Trying to associate with ce:67:c3:86:34:80 (SSID='Kirya' freq=2422 MHz) Oct 1 08:55:50 ares kernel: [ 8783.093674] wlan0: authenticated Oct 1 08:55:50 ares NetworkManager[1830]: info (wlan0): supplicant interface state: authenticating - associating Oct 1 08:55:50 ares kernel: [ 8783.114042] wlan0: associate with ce:67:c3:86:34:80 (try 1) Oct 1 08:55:50 ares kernel: [ 8783.123261] wlan0: RX ReassocResp from ce:67:c3:86:34:80 (capab=0x411 status=0 aid=2) Oct 1 08:55:50 ares kernel: [ 8783.123265] wlan0: associated Oct 1 08:55:50 ares wpa_supplicant[1859]: Associated with ce:67:c3:86:34:80 Oct 1 08:55:50 ares NetworkManager[1830]: info (wlan0): supplicant interface state: associating - associated Oct 1 08:55:52 ares kernel: [ 8785.016027] wlan0: no IPv6 routers present Oct 1 08:55:56 ares kernel: [ 8789.887920] wlan0: deauthenticated from ce:67:c3:86:34:80 (Reason: 15) Oct 1 08:55:56 ares wpa_supplicant[1859]: CTRL-EVENT-DISCONNECTED bssid=ce:67:c3:86:34:80 reason=15 Oct 1 08:55:56 ares kernel: [ 8789.903098] cfg80211: Calling CRDA to update world regulatory domain Oct 1 08:55:56 ares NetworkManager[1830]: info (wlan0): supplicant interface state: associated - disconnected Oct 1 08:55:57 ares NetworkManager[1830]: info (wlan0): supplicant interface state: disconnected - scanning Oct 1 08:55:58 ares wpa_supplicant[1859]: Trying to authenticate with ce:67:c3:86:34:80 (SSID='Kirya' freq=2422 MHz) Oct 1 08:55:58 ares NetworkManager[1830]: info (wlan0): supplicant interface state: scanning - authenticating Oct 1 08:55:58 ares kernel: [ 8791.063535] wlan0: authenticate with ce:67:c3:86:34:80 (try 1) Oct 1 08:55:58 ares wpa_supplicant[1859]: Trying to associate with ce:67:c3:86:34:80 (SSID='Kirya' freq=2422 MHz) Oct 1 08:55:58 ares kernel: [ 8791.070815] wlan0: authenticated Oct 1 08:55:58 ares NetworkManager[1830]: info (wlan0): supplicant interface state: authenticating - associating Oct 1 08:55:58 ares kernel: [ 8791.091384] wlan0: associate with ce:67:c3:86:34:80 (try 1) Oct 1 08:55:58 ares kernel: [ 8791.100579] wlan0: RX ReassocResp from ce:67:c3:86:34:80 (capab=0x411 status=0 aid=2) Oct 1 08:55:58 ares kernel: [ 8791.100583] wlan0: associated Oct 1 08:55:58 ares wpa_supplicant[1859]: Associated with ce:67:c3:86:34:80 Oct 1 08:55:58 ares NetworkManager[1830]: info (wlan0): supplicant interface state: associating - associated Oct 1 08:56:04 ares kernel: [ 8797.894857] wlan0: deauthenticated from ce:67:c3:86:34:80 (Reason: 15) Oct 1 08:56:05 ares wpa_supplicant[1859]: CTRL-EVENT-DISCONNECTED bssid=ce:67:c3:86:34:80 reason=15 Oct 1 08:56:05 ares kernel: [ 8797.933108] cfg80211: Calling CRDA to update world regulatory domain Oct 1 08:56:05 ares NetworkManager[1830]: info (wlan0): supplicant interface state: associated - disconnected Oct 1 08:56:05 ares NetworkManager[1830]: info (wlan0): supplicant interface state: disconnected - scanning Oct 1 08:56:06 ares NetworkManager[1830]: warn Activation (wlan0/wireless): association took too long. Oct 1 08:56:06 ares NetworkManager[1830]: info (wlan0): device state change:
[ath9k-devel] [PATCH v2] ath9k_hw: extend GPIO pin select mask for rfkill
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
this extends the bits for rf kill GPIO selection to [7:2] from [4:2] as
we use GPIO pin 11 as rfkill for AR9480 and also remove few unused
macros
Cc: Wilson Tsao wt...@qca.qualcomm.com
Cc: Hu, Russell r...@qca.qualcomm.com
Signed-off-by: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
---
drivers/net/wireless/ath/ath9k/eeprom.h |8 +++-
drivers/net/wireless/ath/ath9k/hw.c | 10 --
2 files changed, 11 insertions(+), 7 deletions(-)
diff --git a/drivers/net/wireless/ath/ath9k/eeprom.h
b/drivers/net/wireless/ath/ath9k/eeprom.h
index a3c7d0c..70fe75c 100644
--- a/drivers/net/wireless/ath/ath9k/eeprom.h
+++ b/drivers/net/wireless/ath/ath9k/eeprom.h
@@ -104,11 +104,6 @@
#define OLC_FOR_AR9287_10_LATER (AR_SREV_9287_11_OR_LATER(ah) \
ah-eep_ops-get_eeprom(ah, EEP_OL_PWRCTRL))
-#define AR_EEPROM_RFSILENT_GPIO_SEL 0x001c
-#define AR_EEPROM_RFSILENT_GPIO_SEL_S 2
-#define AR_EEPROM_RFSILENT_POLARITY 0x0002
-#define AR_EEPROM_RFSILENT_POLARITY_S 1
-
#define EEP_RFSILENT_ENABLED0x0001
#define EEP_RFSILENT_ENABLED_S 0
#define EEP_RFSILENT_POLARITY 0x0002
@@ -116,6 +111,9 @@
#define EEP_RFSILENT_GPIO_SEL 0x001c
#define EEP_RFSILENT_GPIO_SEL_S 2
+#define AR9480_EEP_RFSILENT_GPIO_SEL 0x00fc
+#define AR9480_EEP_RFSILENT_GPIO_SEL_S 2
+
#define AR5416_OPFLAGS_11A 0x01
#define AR5416_OPFLAGS_11G 0x02
#define AR5416_OPFLAGS_N_5G_HT40 0x04
diff --git a/drivers/net/wireless/ath/ath9k/hw.c
b/drivers/net/wireless/ath/ath9k/hw.c
index f2de7ee..521bb79 100644
--- a/drivers/net/wireless/ath/ath9k/hw.c
+++ b/drivers/net/wireless/ath/ath9k/hw.c
@@ -2170,8 +2170,14 @@ int ath9k_hw_fill_cap_info(struct ath_hw *ah)
#if defined(CONFIG_RFKILL) || defined(CONFIG_RFKILL_MODULE)
ah-rfsilent = ah-eep_ops-get_eeprom(ah, EEP_RF_SILENT);
if (ah-rfsilent EEP_RFSILENT_ENABLED) {
- ah-rfkill_gpio =
- MS(ah-rfsilent, EEP_RFSILENT_GPIO_SEL);
+
+ if (AR_SREV_9480(ah))
+ ah-rfkill_gpio =
+ MS(ah-rfsilent, AR9480_EEP_RFSILENT_GPIO_SEL);
+ else
+ ah-rfkill_gpio =
+ MS(ah-rfsilent, EEP_RFSILENT_GPIO_SEL);
+
ah-rfkill_polarity =
MS(ah-rfsilent, EEP_RFSILENT_POLARITY);
--
1.7.0.4
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
[ath9k-devel] [PATCH] ath9k_hw: Fix number of GPIO pins for AR9287/9300
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com this patch fixes the assumption of maximum number of GPIO pins present in AR9287/AR9300. this fix is essential as we might encounter some functionality issues involved in accessing the status of GPIO pins which are all incorrectly assumed to be not within the range of max_num_gpio of AR9300/AR9287 chipsets Cc: sta...@kernel.org Signed-off-by: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com --- drivers/net/wireless/ath/ath9k/hw.c |4 1 files changed, 4 insertions(+), 0 deletions(-) diff --git a/drivers/net/wireless/ath/ath9k/hw.c b/drivers/net/wireless/ath/ath9k/hw.c index f2de7ee..e2c62ea 100644 --- a/drivers/net/wireless/ath/ath9k/hw.c +++ b/drivers/net/wireless/ath/ath9k/hw.c @@ -2153,6 +2153,10 @@ int ath9k_hw_fill_cap_info(struct ath_hw *ah) pCap-num_gpio_pins = AR9271_NUM_GPIO; else if (AR_DEVID_7010(ah)) pCap-num_gpio_pins = AR7010_NUM_GPIO; + else if (AR_SREV_9300_20_OR_LATER(ah)) + pCap-num_gpio_pins = AR9300_NUM_GPIO; + else if (AR_SREV_9287_11_OR_LATER(ah)) + pCap-num_gpio_pins = AR9287_NUM_GPIO; else if (AR_SREV_9285_12_OR_LATER(ah)) pCap-num_gpio_pins = AR9285_NUM_GPIO; else if (AR_SREV_9280_20_OR_LATER(ah)) -- 1.7.0.4 ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
[ath9k-devel] [PATCH] ath9k_hw: set pci_express capability true for AR9480
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
the AR_SREV register does not seems to indicate whether AR9480 is
pci_express capable or not though the other information like macVersion
etc can be obtained properly. this fix is essential as ASPM won't be intialized
and its related driver functionality ath9k_hw_configpcipowersave won't be
called
Signed-off-by: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
---
drivers/net/wireless/ath/ath9k/hw.c |7 ++-
1 files changed, 6 insertions(+), 1 deletions(-)
diff --git a/drivers/net/wireless/ath/ath9k/hw.c
b/drivers/net/wireless/ath/ath9k/hw.c
index f2de7ee..56ba6a8 100644
--- a/drivers/net/wireless/ath/ath9k/hw.c
+++ b/drivers/net/wireless/ath/ath9k/hw.c
@@ -284,7 +284,12 @@ static void ath9k_hw_read_revisions(struct ath_hw *ah)
ah-hw_version.macVersion =
(val AR_SREV_VERSION2) AR_SREV_TYPE2_S;
ah-hw_version.macRev = MS(val, AR_SREV_REVISION2);
- ah-is_pciexpress = (val AR_SREV_TYPE2_HOST_MODE) ? 0 : 1;
+
+ if (AR_SREV_9480(ah))
+ ah-is_pciexpress = true;
+ else
+ ah-is_pciexpress = (val
+AR_SREV_TYPE2_HOST_MODE) ? 0 : 1;
} else {
if (!AR_SREV_9100(ah))
ah-hw_version.macVersion = MS(val, AR_SREV_VERSION);
--
1.7.0.4
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] HowTo Set to get HT throughput(SR-71a and ath9k)
On Wed, Sep 28, 2011 at 1:41 PM, wendy_life wendy_l...@yeah.net wrote: Hi,all! with much effort , I only get MAX througthput 20Mbps at adhoc mode and 54Mbps at ap-client mode. 11n adhoc is not yet supported in mac80211, patches for 11n support for adhoc are under review comments. [Target Board: UBNT Routerstation System Version:Backfire (10.03.1-rc4, r24045) Wifi card: SR71-A] I doubt if I make error configuration about the config files,as following: /etc/config/wireless config wifi-device radio0 option type mac80211 option channel 161 option macaddr *** option hwmode 11na option htmode HT40+ list ht_capab SHORT-GI-40 list ht_capab DSSS_CCK-40 # REMOVE THIS LINE TO ENABLE WIFI: #option disabled 1 option txpower 10 My question is how to configure the file to get 300Mbps throughput??? More,I am not sure if the antenna play its function(3 antennas) Best wishes! 2011-09-28 Best Wishes~~ ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
[ath9k-devel] [RFC] ath9k_hw: Fix number of GPIO pins for AR9287/9300
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com Signed-off-by: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com --- drivers/net/wireless/ath/ath9k/hw.c |4 1 files changed, 4 insertions(+), 0 deletions(-) diff --git a/drivers/net/wireless/ath/ath9k/hw.c b/drivers/net/wireless/ath/ath9k/hw.c index f2de7ee..e2c62ea 100644 --- a/drivers/net/wireless/ath/ath9k/hw.c +++ b/drivers/net/wireless/ath/ath9k/hw.c @@ -2153,6 +2153,10 @@ int ath9k_hw_fill_cap_info(struct ath_hw *ah) pCap-num_gpio_pins = AR9271_NUM_GPIO; else if (AR_DEVID_7010(ah)) pCap-num_gpio_pins = AR7010_NUM_GPIO; + else if (AR_SREV_9300_20_OR_LATER(ah)) + pCap-num_gpio_pins = AR9300_NUM_GPIO; + else if (AR_SREV_9287_11_OR_LATER(ah)) + pCap-num_gpio_pins = AR9287_NUM_GPIO; else if (AR_SREV_9285_12_OR_LATER(ah)) pCap-num_gpio_pins = AR9285_NUM_GPIO; else if (AR_SREV_9280_20_OR_LATER(ah)) -- 1.7.0.4 ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
[ath9k-devel] [RFC] ath9k_hw: set is_pciexpress true for AR9480
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
the AR_SREV register does not seems to indicate it properly though the
other information like macVersion etc can be obtained properly
Signed-off-by: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
---
drivers/net/wireless/ath/ath9k/hw.c |7 ++-
1 files changed, 6 insertions(+), 1 deletions(-)
diff --git a/drivers/net/wireless/ath/ath9k/hw.c
b/drivers/net/wireless/ath/ath9k/hw.c
index f2de7ee..56ba6a8 100644
--- a/drivers/net/wireless/ath/ath9k/hw.c
+++ b/drivers/net/wireless/ath/ath9k/hw.c
@@ -284,7 +284,12 @@ static void ath9k_hw_read_revisions(struct ath_hw *ah)
ah-hw_version.macVersion =
(val AR_SREV_VERSION2) AR_SREV_TYPE2_S;
ah-hw_version.macRev = MS(val, AR_SREV_REVISION2);
- ah-is_pciexpress = (val AR_SREV_TYPE2_HOST_MODE) ? 0 : 1;
+
+ if (AR_SREV_9480(ah))
+ ah-is_pciexpress = true;
+ else
+ ah-is_pciexpress = (val
+AR_SREV_TYPE2_HOST_MODE) ? 0 : 1;
} else {
if (!AR_SREV_9100(ah))
ah-hw_version.macVersion = MS(val, AR_SREV_VERSION);
--
1.7.0.4
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
[ath9k-devel] [PATCH] ath9k: Fix a dma warning/memory leak
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
proper dma_unmapping and freeing of skb's has to be done in the rx
cleanup for EDMA chipsets when the device is unloaded and this also
seems to address the following warning which shows up occasionally when
the device is unloaded
Call Trace:
[c0148cd2] warn_slowpath_common+0x72/0xa0
[c03b669c] ? dma_debug_device_change+0x19c/0x200
[c03b669c] ? dma_debug_device_change+0x19c/0x200
[c0148da3] warn_slowpath_fmt+0x33/0x40
[c03b669c] dma_debug_device_change+0x19c/0x200
[c0657f12] notifier_call_chain+0x82/0xb0
[c0171370] __blocking_notifier_call_chain+0x60/0x90
[c01713bf] blocking_notifier_call_chain+0x1f/0x30
[c044f594] __device_release_driver+0xa4/0xc0
[c044f647] driver_detach+0x97/0xa0
[c044e65c] bus_remove_driver+0x6c/0xe0
[c029af0b] ? sysfs_addrm_finish+0x4b/0x60
[c0450109] driver_unregister+0x49/0x80
[c0299f54] ? sysfs_remove_file+0x14/0x20
[c03c3ab2] pci_unregister_driver+0x32/0x80
[f92c2162] ath_pci_exit+0x12/0x20 [ath9k]
[f92c8467] ath9k_exit+0x17/0x36 [ath9k]
[c06523cd] ? mutex_unlock+0xd/0x10
[c018e27f] sys_delete_module+0x13f/0x200
[c02139bb] ? sys_munmap+0x4b/0x60
[c06547c5] ? restore_all+0xf/0xf
[c0657a20] ? spurious_fault+0xe0/0xe0
[c01832f4] ? trace_hardirqs_on_caller+0xf4/0x180
[c065b863] sysenter_do_call+0x12/0x38
---[ end trace 16e1c1521c06bcf9 ]---
Mapped at:
[c03b7938] debug_dma_map_page+0x48/0x120
[f92ba3e8] ath_rx_init+0x3f8/0x4b0 [ath9k]
[f92b5ae4] ath9k_init_device+0x4c4/0x7b0 [ath9k]
[f92c2813] ath_pci_probe+0x263/0x330 [ath9k]
Signed-off-by: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
---
drivers/net/wireless/ath/ath9k/recv.c | 10 +-
1 files changed, 9 insertions(+), 1 deletions(-)
diff --git a/drivers/net/wireless/ath/ath9k/recv.c
b/drivers/net/wireless/ath/ath9k/recv.c
index bcc0b22..4984350 100644
--- a/drivers/net/wireless/ath/ath9k/recv.c
+++ b/drivers/net/wireless/ath/ath9k/recv.c
@@ -205,14 +205,22 @@ static void ath_rx_remove_buffer(struct ath_softc *sc,
static void ath_rx_edma_cleanup(struct ath_softc *sc)
{
+ struct ath_hw *ah = sc-sc_ah;
+ struct ath_common *common = ath9k_hw_common(ah);
struct ath_buf *bf;
ath_rx_remove_buffer(sc, ATH9K_RX_QUEUE_LP);
ath_rx_remove_buffer(sc, ATH9K_RX_QUEUE_HP);
list_for_each_entry(bf, sc-rx.rxbuf, list) {
- if (bf-bf_mpdu)
+ if (bf-bf_mpdu) {
+ dma_unmap_single(sc-dev, bf-bf_buf_addr,
+ common-rx_bufsize,
+ DMA_BIDIRECTIONAL);
dev_kfree_skb_any(bf-bf_mpdu);
+ bf-bf_buf_addr = 0;
+ bf-bf_mpdu = NULL;
+ }
}
INIT_LIST_HEAD(sc-rx.rxbuf);
--
1.7.0.4
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] Developer documentation
On Tue, Sep 20, 2011 at 11:55 PM, Valentin Rouxel valentin.rou...@etudiant.univ-rennes1.fr wrote: Hello, Hi, I am a French student in computer science. I am working on a class project where we should modified a wireless driver. Our teacher said Madwifi could be an interesting driver but it seams that this driver is not yet maintained and it could be difficult to find some help if necessary. I think ath9k could be an other interesting driver. So I am searching a documentation which explain how works this driver. i am not aware of any public docs that explains ath9k. please start looking at the code and feel free to ask your doubts to this list. you can read/search things in http://blog.gmane.org/gmane.linux.drivers.ath9k.devel and some info in http://linuxwireless.org/en/users/Drivers/ath9k Could someone say me where I could find this documentation ? I am also interested by the ath5k documentation. please also post to ath5k list. Thanking you in advance. Valentin Rouxel ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] Git mirrors
On Wed, Sep 21, 2011 at 4:56 AM, Gabriel Burca gburca-at...@ebixio.com wrote: kernel.org has been down for about 3 weeks now. Is there a git mirror for the ath9k driver, compat and compat-wireless? Could someone mirror them to github.com if they have a recent version? please checkout http://www.spinics.net/lists/linux-wireless/msg76901.html https://lkml.org/lkml/2011/9/13/138 Regards. -- Gabriel Burca ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] How can I use ath9k adapter + Wireshark to disect/monitor wireless 802.11 abgn network traffic.
On Mon, Sep 19, 2011 at 12:53 PM, shashikant ajegaonkar ajegaon...@gmail.com wrote: Hi All, Please forward the earlier mail thread if any or your views on using ath9k adapter + Wireshark to disect/monitor wireless 802.11 abgn network traffic either windows/linux platforms. install ath9k in your linux machine http://linuxwireless.org/en/users/Drivers/ath9k install iw to sniff with ath9k channel 6 HT40+ packets 1.disable network manager 2. sudo iw dev wlan0 set type monitor 3. sudo iw dev wlan0 set channel 6 HT40+ 4. sudo ifconfig wlan0 up 5. sudo wireshark -- Thanks Regards, Shashikant P. Ajegaonkar +91-7207340878 ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] how can i use this function : ath9k_hw_computetxtime?
On Fri, Sep 16, 2011 at 8:32 AM, houchenda2006 houchenda2...@163.com wrote: hello, I want to use ath9k_hw_computetxtime in my application programme.But I don't know how to call the function. Does it have any interface to application, or device file in /dev ? thanks! not a good idea, best way is to understand that function/decode the macros and replicate exactly in your application program. 2011-09-16 houchenda2006 ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] Wireless Card
On Tue, Sep 13, 2011 at 11:54 AM, Amr Al-Hamad amr.alha...@hotmail.com wrote: Hi all, I am a newbie in ath9k. and I am doing some research on wireless LANs. I want to buy a wireless card that works on a 5 GHz frequency band, also I want it to be supported by ath9k driver. I am currently working on a TP-LINK TL-WN951N which does not support this band of frequency. I read that LinksysWMP600n supports this band of frequency, but I want to ask if this card is compatible with ath9k driver? and if not could anyone give me any recommendation for my new wireless card? AR9382, AR9380, AR9280 support 5ghz/2gzh(DB) http://linuxwireless.org/en/users/Drivers/ath9k#supported_chipsets Thank You. ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] Features for FCC test and etc
On Mon, Sep 12, 2011 at 7:08 PM, Jun Xiao jun.x...@sixnet.com wrote: Hi, With all your great efforts developing the driver, our products with AR9271 is on the way of FCC certification tests. Some features are required: 1. Be able to turn on WiFi transmission constantly rfkill? 2. Be able to transmit at its maximum power dev devname set txpower auto|fixed|limit [tx power in mBm] the power set to the hardware will be controlled by regulatory power. 3. Be able to modify its MAC address you can use macchanger application. supported by mac80211 Do we have these features in ath9k-htc driver and what is the handler from user space? If not, are they under development? Thanks in advance. Jun Xiao Sixnet | www.sixnet.com O +1 514 422 9110 Ext. 482 F +1 514 422 3338 j...@sixnet.com ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] Features for FCC test and etc
On Mon, Sep 12, 2011 at 9:01 PM, Mohammed Shafi shafi.wirel...@gmail.com wrote: On Mon, Sep 12, 2011 at 7:08 PM, Jun Xiao jun.x...@sixnet.com wrote: Hi, With all your great efforts developing the driver, our products with AR9271 is on the way of FCC certification tests. Some features are required: 1. Be able to turn on WiFi transmission constantly rfkill? 2. Be able to transmit at its maximum power dev devname set txpower auto|fixed|limit [tx power in mBm] the power set to the hardware will be controlled by regulatory power. sorry the command is iw dev devname set txpower auto|fixed|limit [tx power in mBm] http://linuxwireless.org/en/users/Documentation/iw 3. Be able to modify its MAC address you can use macchanger application. supported by mac80211 Do we have these features in ath9k-htc driver and what is the handler from user space? If not, are they under development? Thanks in advance. Jun Xiao Sixnet | www.sixnet.com O +1 514 422 9110 Ext. 482 F +1 514 422 3338 j...@sixnet.com ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] Oops while loading firmware of ath9k_htc device.
On Tue, Aug 30, 2011 at 5:42 PM, Christian Kapeller christian.kapel...@cmotion.eu wrote: Hi, when loading the ath9k_htc module for my TL-WN722N device, I get an oops. I use the openwrt backfire distribution on an arm device, with kernel 2.6.31.12 and compat-wireless-2011-06-22. The firmware file is at /lib/firmware/ar9271.fw please see whether you are getting the panic when you upgrade your firmware http://linuxwireless.org/en/users/Drivers/ath9k_htc#Firmware please take the 1.3 version http://wireless.kernel.org/download/htc_fw/1.3/ also please take the latest compat wireless. report back if you still get or don't get the oops! thanks! The device identifies as: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n The backtrace looks as follows: Unable to handle kernel NULL pointer dereference at virtual address 0048 pgd = c0004000 [0048] *pgd= Internal error: Oops: 17 [#1] PREEMPT Modules linked in: xt_owner ipt_REDIRECT ipt_NETMAP ipt_MASQUERADE iptable_nat nf_nat xt_CONNMARK xt_recent xt_helper xt_conntrack xt_connmark xt_connbytes xt_NOTRACK iptable_raw xt_state nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack ehci_hcd sd_mod ipt_REJECT xt_TCPMSS ipt_LOG xt_comment xt_multiport xt_mac xt_limit iptable_mangle iptable_filter ext3 jbd vfat fat ntfs ath9k_htc ath9k_common ath9k_hw ath nls_utf8 nls_iso8859_15 nls_iso8859_1 nls_cp437 mac80211 usbcore scsi_mod mbcache cfg80211 compat lib80211_crypt_tkip lib80211_crypt_ccmp lib80211_crypt_wep lib80211 arc4 aes_generic deflate ecb CPU: 0 Not tainted (2.6.31.12 #1) PC is at get_device_parent+0x78/0x14c LR is at get_device_parent+0x70/0x14c pc : [c01afc88] lr : [c01afc80] psr: 8013 sp : c6447b88 ip : c6447b88 fp : c6447ba4 r10: 0001 r9 : c65ffd0c r8 : c661cc60 r7 : c6172af0 r6 : c65992b8 r5 : c65992c0 r4 : c6172af0 r3 : r2 : r1 : r0 : 0001 Flags: Nzcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel Control: 10c5387d Table: 9640c019 DAC: 0017 Process khubd (pid: 728, stack limit = 0xc64462e8) Stack: (0xc6447b88 to 0xc6448000) 7b80: c65992b8 c65992c0 c6599280 c6447bec c6447ba8 7ba0: c01b0cb4 c01afc1c c6172ae8 c6172ae8 c6599280 c6447be0 c6447bc8 7bc0: c01b0128 c6172ae8 c65992b8 c6599280 c661cc60 c65ffd0c 0001 7be0: c6447c1c c6447bf0 bf03b92c c01b0c18 0001 c6172a80 c65ffd00 c6599140 7c00: bf17b4a8 c65ed388 bf17b41c c6447c34 c6447c20 bf03bbcc bf03b7c8 7c20: bf17b41c c6447c64 c6447c38 bf16948c bf03bbb8 c6599160 c6599140 7c40: c6599160 c6599140 c6172a80 bf17b44c bf17b4a8 c6447c94 c6447c68 7c60: bf09ad4c bf1692c4 bf09ac58 c6599160 bf17b44c c01b3528 7c80: c65eed80 bf0ab8d4 c6447cbc c6447c98 c01b33c4 bf09ac64 c661ca20 c6447ca8 7ca0: bf17b44c c6599160 c01b3528 c6447cd4 c6447cc0 c01b356c c01b32e8 7cc0: c6599160 c6447cd8 c6447cfc c6447cd8 c01b2860 c01b3534 c63f4588 c63fbf34 7ce0: c6599194 c6599160 c6599140 c6447d14 c6447d00 c01b35f4 c01b2818 7d00: c6599160 c6599168 c6447d24 c6447d18 c01b268c c01b35a8 c6447d6c c6447d28 7d20: c01b0f60 c01b266c c661c9c0 c6172ae8 c6447d6c c6447d40 c00a24fc c00a090c 7d40: 0009 c6172a80 c65eed80 c6599140 c65eed80 0001 7d60: c6447ddc c6447d70 bf099698 c01b0c18 0001 7d80: 1388 c6447d90 c0287f44 c6599140 c6172a84 c65eed80 7da0: c6172ae8 c65eed84 c661c9c0 0001 c64882a0 c6172a80 bf0abf3c 0001 7dc0: c618d8c0 bf0ab750 c6447e04 c6447de0 bf0a148c bf099174 7de0: c00ec428 c00ec27c c6447e14 c6172ae8 bf0abf3c c01b3528 c6447e14 c6447e08 7e00: bf099958 bf0a1444 c6447e3c c6447e18 c01b33c4 bf099934 c64882a0 7e20: bf0abf3c c6172ae8 c01b3528 c6447e54 c6447e40 c01b356c c01b32e8 7e40: c6172ae8 c6447e58 c6447e7c c6447e58 c01b2860 c01b3534 c63f4588 c63fbdf4 7e60: c6172b1c c6172ae8 c600a300 c6447e94 c6447e80 c01b35f4 c01b2818 7e80: c6172ae8 c6172af0 c6447ea4 c6447e98 c01b268c c01b35a8 c6447eec c6447ea8 7ea0: c01b0f60 c01b266c c6447ed4 c6173be8 3a393831 c00a0031 c6172a80 7ec0: c6172a80 c6172ae8 c6173b80 0001 c618d8c0 0002 7ee0: c6447f0c c6447ef0 bf093098 c01b0c18 c6256280 c6172a80 c6173b80 7f00: c6447fc4 c6447f10 bf094358 bf093040 c6447f44 c6447f20 c0063728 c003beb0 7f20: c035df0c c6032000 c618d8d4 c6447f84 c62562b8 c62562c0 7f40: c6173c1c c6256288 c6256310 0101 c6446000 c6256640 c62562bc c6256280 7f60: c6173b80 c6173d5c c6173b80 c6256660 c6256660 c643a700 7f80: c005eb5c c6447f84 c6447f84 0101 01010001 c6447fc4 c645deb8 7fa0: c6447fcc bf093a30 c6447ff4 c6447fc8 7fc0: c005e8f8 bf093a3c c6447fd0 c6447fd0 7fe0: c6447ff8 c004c50c
Re: [ath9k-devel] HELP! HELP! HELP! HELP!
On Thu, Aug 25, 2011 at 9:15 PM, pangyunong 029...@gmail.com wrote: hi, that is the driver for ath9k indeed. development is done in the git tree, please clone the source code git clone git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-testing.git http://linuxwireless.org/en/developers/Documentation/git-guide http://linuxwireless.org/en/users/Drivers/ath9k looking at the ath9k-devel mailing list archives will provide more information. preliminary thing is to get the hardware and make it start working, doing some basic configuration etc. On Thu, 2011-08-25 at 20:49 +0530, subham das wrote: Dear Sir/Madam, I am doing a project, in developing ath9k driver for Linux (some of those issues that are not solved yet) in my last year of graduation(I.T.). I started with studying the features of all the Linux based opensource/free drivers under various licensed and then came into conclusion, with suggestion from my Supervisor, that developing ath9k would be my project, i found the source codes for ath9k from compat-wireless-3.0-2 in ...\compat-wireless-3.0-2 \drivers\net\wireless\ath\ath9k. I would like to confirm if it is the Source Code for ath9k, moreover i also wanted to know where would i get some manuals or materials to study ath9k driver, so that implementations would be easy, or any references. I am also allowed to have more than one Superisor, so i would also like to request if someone can also Supervise me. Thanking You in Advance. Subham Das (You can reply me in this e-mail:das.subha...@gmail.com, but please do reply!) ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] Should I compile kenerl again?
On Wed, Aug 24, 2011 at 2:27 PM, pangyunong 029...@gmail.com wrote: Hi all, I change the code in ath9k/main.c and net/mac80211/tx.c. how can i use my new version of ath9k driver for my device? Should I make and install the driver again, configure and compile kernel once more? reinstall the compat wireless Yunong Pang Regards, ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] [RFC/RFT] ath9k_htc: Fix memory leak
On Wed, Aug 24, 2011 at 1:15 AM, John W. Linville linvi...@tuxdriver.com wrote: On Mon, Aug 15, 2011 at 05:56:33PM +0530, Mohammed Shafi wrote: On Sun, Aug 14, 2011 at 7:04 AM, Larry Finger larry.fin...@lwfinger.net wrote: Kmemleak shows the following kind of memory leak for ath9k_htc: unreferenced object 0x88004542f200 (size 512): comm khubd, pid 977, jiffies 4317632516 (age 16855.868s) hex dump (first 32 bytes): 00 00 00 0a 00 00 00 00 00 02 01 05 00 00 02 01 00 00 00 00 00 00 81 38 02 00 00 00 33 33 30 30 ...83300 backtrace: [81122d77] create_object+0x127/0x2b0 [813580b1] kmemleak_alloc+0x21/0x50 [8111f383] __kmalloc_node_track_caller+0x153/0x220 [812b703e] __alloc_skb+0x7e/0x170 [a081] htc_connect_service+0x111/0x200 [ath9k_htc] [a083bb90] ath9k_init_htc_services+0x240/0x2b0 [ath9k_htc] [a083c1ca] ath9k_htc_probe_device+0xea/0xa50 [ath9k_htc] [a08338dc] ath9k_htc_hw_init+0xc/0x30 [ath9k_htc] [a08356ba] ath9k_hif_usb_probe+0x1ca/0x420 [ath9k_htc] [a00a2279] usb_probe_interface+0xb9/0x160 [usbcore] [81279379] driver_probe_device+0x89/0x1a0 [8127958b] __device_attach+0x4b/0x60 [81278024] bus_for_each_drv+0x64/0x90 [81279231] device_attach+0xa1/0xb0 [81278a25] bus_probe_device+0x25/0x40 [81276d2a] device_add+0x55a/0x630 The device is a TP-Link TL-WN722N. The output from lsusb is ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n. Signed-off-by: Larry Finger larry.fin...@lwfinger.net Cc: Stable sta...@kernel.org --- This patch certainly fixes a leak. I'm testing to see if there are others. Hi Larry, thanks for finding this. I remember seeing this memleaks sometime back and thought this patch might help(i think same as yours with some more corner cases) https://patchwork.kernel.org/patch/1016752/ but I found there were still some memory leaks, I was unsure where I am missing. if you are sure that this addresses the issue, we can send a patch. Ping? Is this the patch we want? Or something else? Hi John, the complete patch is posted http://www.spinics.net/lists/linux-wireless/msg75134.html Vasanth said that at some scenario's with the above patch it may cause some panics. based on the maintainers concerns/doubts lets drop this patch. myself and Larry still noticed few more memory leaks. I think we better drop this patch and fix it completely/tested. as I am with some other critical tasks we will soon address this. Larry if you have any thoughts, please share. John -- John W. Linville Someday the world will need a hero, and you linvi...@tuxdriver.com might be all we have. Be ready. -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] 'Superchannel'?
On Wed, Aug 24, 2011 at 12:32 PM, Adrian Chadd adr...@freebsd.org wrote: * changing regulatory not advisable This may not be applicable if the amateur licence he has permits him to transmit on these frequencies. oh ok, i don't know much about regulatory *second number is hw specific value for the channel, we use this index to do some HAL configuration like ANI, calibration or any other operation in the driver code using this index for struct ath9k_channel ... and the hardware doesn't have calibration data for those lower frequencies, so you may find you have to do all kinds of crazy hacks in the EEPROM code for things to work. hmmm ok, going to be lots of hardware code reading :) Adrian ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] Building ath9k on a Linux machine and installing on a different one. Both machines run Fedora 12 but with different kernel versions
On Wed, Aug 24, 2011 at 6:44 PM, Fabio Tignanelli fabio.tignane...@paconsulting.com wrote: Hi, I am trying to use compact-wireless to update the driver for an ath9K. The reason why I am emailing you is that, despite trying to follow all the guidelines on How To Ask Questions the Smart Way, I have got nowhere ending up in all sort of dead corners. Current Issue I need to update the driver for an ath9k device connected to an embedded device. The OS on the device is a Fedora 12 but very cut down version (e.g. no source code, or compiler) for space reasons. It’s a 2.6.31.5-127.fc12.686.PAE I have a Fedora 12 (2.6.32.26-175.fc12.686.PAE) running on a laptop and I compiled the latest version of the ath9k driver using compact-wireless (v 3.1-rc1-1). I have done that using the following command seeing that the kernel version installed on the laptop is different from the one installed on the embedded device but it actually contains also the source for 2.6.31.5-127.fc12.686.PAE: I have little idea about this, as I have not tried cross compiling ath9k and using it on some embedded device. i heard that we need tool chains etc. you might be interested in https://openwrt.org/ does some one has more info? make KLIB=lib/modules/2.6.31.5-127.fc12.686.PAE This has generated a number of .o and .ko files. Now I cannot copy wireless-compat on the embedded device and do make install because of space reasons and it seems that even this operation requires the source code of the kernel and a compiler. Question Ideally I would like to copy across the created .ko modules to the embedded device from the Linux laptop and run insmod or modprobe to install the new drivers from command prompt. Is this doable? If yes, which files I should copy across? Using support from Linux Wireless. Being new to the Linux world I must say I have found the support section very hard going. I was expecting a common form to fill in with the problem and a preconfigured list of subjects or a easy-to-search archive with existing threads. I subscribed to the mailing list of ath9k, but I am not sure if the right way to ask for support is emails to ath9k-devel@lists.ath9k.org or directly to digested or undigested member's email addr (whatever digested means). I tried to configure xchat on my fedora12 with no luck (the server id and the channel do not seem to be sufficient to configure the client). I searched the Internet at great lengths. Etc…. Apologies if my email is not what you would expect to receive. But I have run out of options to solve this problem. Any help would be much appreciated. Thanks Fabio P Please consider the environment before printing this e-mail ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] [RFC/RFT] ath9k_htc: Fix memory leak
On Wed, Aug 24, 2011 at 10:19 PM, Larry Finger larry.fin...@lwfinger.net wrote: On 08/24/2011 10:53 AM, Mohammed Shafi wrote: On Wed, Aug 24, 2011 at 1:15 AM, John W. Linville linvi...@tuxdriver.com wrote: On Mon, Aug 15, 2011 at 05:56:33PM +0530, Mohammed Shafi wrote: On Sun, Aug 14, 2011 at 7:04 AM, Larry Fingerlarry.fin...@lwfinger.net wrote: Kmemleak shows the following kind of memory leak for ath9k_htc: unreferenced object 0x88004542f200 (size 512): comm khubd, pid 977, jiffies 4317632516 (age 16855.868s) hex dump (first 32 bytes): 00 00 00 0a 00 00 00 00 00 02 01 05 00 00 02 01 00 00 00 00 00 00 81 38 02 00 00 00 33 33 30 30 ...83300 backtrace: [81122d77] create_object+0x127/0x2b0 [813580b1] kmemleak_alloc+0x21/0x50 [8111f383] __kmalloc_node_track_caller+0x153/0x220 [812b703e] __alloc_skb+0x7e/0x170 [a081] htc_connect_service+0x111/0x200 [ath9k_htc] [a083bb90] ath9k_init_htc_services+0x240/0x2b0 [ath9k_htc] [a083c1ca] ath9k_htc_probe_device+0xea/0xa50 [ath9k_htc] [a08338dc] ath9k_htc_hw_init+0xc/0x30 [ath9k_htc] [a08356ba] ath9k_hif_usb_probe+0x1ca/0x420 [ath9k_htc] [a00a2279] usb_probe_interface+0xb9/0x160 [usbcore] [81279379] driver_probe_device+0x89/0x1a0 [8127958b] __device_attach+0x4b/0x60 [81278024] bus_for_each_drv+0x64/0x90 [81279231] device_attach+0xa1/0xb0 [81278a25] bus_probe_device+0x25/0x40 [81276d2a] device_add+0x55a/0x630 The device is a TP-Link TL-WN722N. The output from lsusb is ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n. Signed-off-by: Larry Fingerlarry.fin...@lwfinger.net Cc: Stablesta...@kernel.org --- This patch certainly fixes a leak. I'm testing to see if there are others. Hi Larry, thanks for finding this. I remember seeing this memleaks sometime back and thought this patch might help(i think same as yours with some more corner cases) https://patchwork.kernel.org/patch/1016752/ but I found there were still some memory leaks, I was unsure where I am missing. if you are sure that this addresses the issue, we can send a patch. Ping? Is this the patch we want? Or something else? Hi John, the complete patch is posted http://www.spinics.net/lists/linux-wireless/msg75134.html Vasanth said that at some scenario's with the above patch it may cause some panics. based on the maintainers concerns/doubts lets drop this patch. myself and Larry still noticed few more memory leaks. I think we better drop this patch and fix it completely/tested. as I am with some other critical tasks we will soon address this. Larry if you have any thoughts, please share. Dropping the current patches seems right with me. I hope to get time to work on this, but I also have some other things to do. Perhaps, we can get a patch with the subset of leaks in the error path that do not have any complications. Those would be easy, and then we can get the others later. yes sure, once I get some time to test and understand this completely. thanks! Larry -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
[ath9k-devel] [RFC] ath9k: Add a debug entry for current tx-power
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
this is the tx-power that seems to be used by the hardware code
Signed-off-by: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
---
drivers/net/wireless/ath/ath9k/debug.c | 43
1 files changed, 43 insertions(+), 0 deletions(-)
diff --git a/drivers/net/wireless/ath/ath9k/debug.c
b/drivers/net/wireless/ath/ath9k/debug.c
index 9bec3b8..982371f 100644
--- a/drivers/net/wireless/ath/ath9k/debug.c
+++ b/drivers/net/wireless/ath/ath9k/debug.c
@@ -176,6 +176,47 @@ static const struct file_operations fops_rx_chainmask = {
.llseek = default_llseek,
};
+static ssize_t read_file_current_txpower(struct file *file,
+char __user *user_buf,
+size_t count, loff_t *ppos)
+{
+ struct ath_softc *sc = file-private_data;
+ char buf[32];
+ unsigned int len;
+
+ len = sprintf(buf, %u\n, sc-curtxpow);
+ return simple_read_from_buffer(user_buf, count, ppos, buf, len);
+}
+
+static ssize_t write_file_current_txpower(struct file *file,
+ const char __user *user_buf,
+ size_t count, loff_t *ppos)
+{
+ struct ath_softc *sc = file-private_data;
+ unsigned long current_tx_power;
+ char buf[32];
+ ssize_t len;
+
+ len = min(count, sizeof(buf) - 1);
+ if (copy_from_user(buf, user_buf, len))
+ return -EFAULT;
+
+ buf[len] = '\0';
+ if (strict_strtoul(buf, 0, current_tx_power))
+ return -EINVAL;
+
+ sc-curtxpow = current_tx_power;
+ return count;
+}
+
+static const struct file_operations fops_current_txpower = {
+ .read = read_file_current_txpower,
+ .write = write_file_current_txpower,
+ .open = ath9k_debugfs_open,
+ .owner = THIS_MODULE,
+ .llseek = default_llseek,
+};
+
static ssize_t read_file_disable_ani(struct file *file, char __user *user_buf,
size_t count, loff_t *ppos)
{
@@ -1253,6 +1294,8 @@ int ath9k_init_debug(struct ath_hw *ah)
sc-debug.debugfs_phy, sc, fops_tx_chainmask);
debugfs_create_file(disable_ani, S_IRUSR | S_IWUSR,
sc-debug.debugfs_phy, sc, fops_disable_ani);
+ debugfs_create_file(current_txpower, S_IRUSR | S_IWUSR,
+ sc-debug.debugfs_phy, sc, fops_current_txpower);
debugfs_create_file(regidx, S_IRUSR | S_IWUSR, sc-debug.debugfs_phy,
sc, fops_regidx);
debugfs_create_file(regval, S_IRUSR | S_IWUSR, sc-debug.debugfs_phy,
--
1.7.0.4
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] Some novice questions
On Tue, Aug 23, 2011 at 11:43 AM, pangyunong 029...@gmail.com wrote: how can i watch the value in offset 0x8084 ? I have no debug in /sys/kernel now. How can i use it? pls read http://linuxwireless.org/en/users/Drivers/ath9k/debug On Mon, 2011-08-01 at 15:38 +0530, Mohammed Shafi wrote: On Mon, Aug 1, 2011 at 3:00 PM, pangyunong 029...@gmail.com wrote: Thank you for your reply! But how can it be modified NAV to be 0 each time I transmit a frame? Can I control the value by flashing the firmware in my network card? no, there is no firmware for ath9k. i tried to force the value of the same via debug some random value... anyway it always shows 0 /sys/kernel/debug/ieee80211/phy0/ath9k# echo 0x8084 regidx cat regval echo 0x5678 regval On Mon, 2011-08-01 at 14:43 +0530, Mohammed Shafi wrote: On Sat, Jul 30, 2011 at 8:56 PM, pangyunong 029...@gmail.com wrote: Hi, I'm very excited in the list. It's my first time to use a mailing list, so I'm afraid there are some impolite to you. If there, please tell me. I have some question about mailing list of ath9k. I want modify NAV value of a MAC frame when sending any frame using AP mode in ath9k. But I have never touch network card driver before, how can I learn that by myself? Could you give me some advices? Thank you very much. The AR_NAV (with offset 0X8084) is the register that provides NAV value. I don't think it can be controlled by software. Regards, Yunong Pang ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] 'Superchannel'?
On Wed, Aug 24, 2011 at 1:35 AM, Alex S. al_91...@hotmail.com wrote: Hi, I am working on an amateur radio project, so I'd like to get access to the 2.4GHz channels below 2412. I'm using OpenWRT and have modified my CRDA regulatory.bin file to allow those frequencies, but I still only have access to channels 1-11. Poking around in the source for ath9k, I see ath9k_2ghz_chantable in init.c. Will adding values here open up extra channels? If so, what exactly is the format of CHAN2G(2467, 11)? The 2467 is obviously the frequency but what is the significance of the second number? I added the channels from 2312-2407 and after recompiling it doesn't seem to have changed anything. * changing regulatory not advisable *second number is hw specific value for the channel, we use this index to do some HAL configuration like ANI, calibration or any other operation in the driver code using this index for struct ath9k_channel *you should have hit BUILD_BUG_ON(ARRAY_SIZE(ath9k_2ghz_chantable) + ARRAY_SIZE(ath9k_5ghz_chantable) != ATH9K_NUM_CHANNELS); Thanks for any help, Alex ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] FEDORA 15 WLAN PROBLEM....HELP NEEDED...PLS DONT IGNORE
I am using Fedora 15(Lovelock), but the WLAN is not working in it. My WLAN driver is ATHEROS AR9285. Can you tell me how to configure it. Is any driver software needed? Can you send me the driver software (or a link to download the driver sofware) for the same. Hi Anoop, please take a look at this link http://people.redhat.com/sgruszka/compat_wireless.html and some more information in http://wireless.kernel.org/en/users/Download thanks. ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] ath9k-devel Digest, Vol 38, Issue 34
On Sat, Aug 20, 2011 at 9:42 AM, mason myongsu.c...@gmail.com wrote: Thanks for your reply. BTW, what is the difference between max_num_sta and MAX_STA_COUNT? sorry MAX_STA_COUNT is 2007 only, i don't know where did i found it as 1024 :) - mason ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] Kernel panic with compat-wireless-2011-07-28
This issue is rare and hard to reproduce. It has only happened once so far in about 10 hours of testing. :( I can try tomorrow in a noisy environment. I am currently running with your patch (with the debug prints) and waiting for this issue to reproduce. sorry, that printk patch is to make sure that we are using ath9k rate control algorithm, otherwise it does not helps anything Please let me know which would be more useful for you: - continuing to run with compat-wireless-2011-07-28 and your patch ath9k-rc-debug.patch - compiling the latest bleeding-edge compat-wireless (should I apply your patch?) and running that no need, if we are sure that we are using ath9k rate control. - compiling wireless-testing (from this address? git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-testing.git) and running that (again should I run it with your debug patch?) thats a bit long process, and you have to compile the kernel(not easy as installing compat wireless). Thanks, Catalin -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] Kernel panic with compat-wireless-2011-07-28
On Sun, Aug 14, 2011 at 2:07 PM, Catalin Drula catalin.dr...@personalnetworks.ro wrote: Hi, I've reproduced again the issue with compat-wireless-2011-08-08; this time I added some debug prints to ath9k/rc.c (as seen in the attached patch). Observations: - the rate table seems to get messed up/overwritten right before the crash; in fact, this is what causes the kernel panic - every time I've reproduced this issue so far there has been a Failed to stop TX DMA! message right before it happened; these messages are otherwise very rare (once every couple of hours), but whenever the crash occurs there is one such message right then Could it be that whatever leads to the Failed to stop TX DMA! message also causes some memory to be overwritten? --- This is the dump with debug information: Aug 13 23:38:09 192.168.50.101 RATE 7: ratekbps 18000 rate_flags 15 Aug 13 23:38:09 192.168.50.101 RATE 8: ratekbps 24000 rate_flags 15 Aug 13 23:38:09 192.168.50.101 RATE 9: ratekbps 36000 rate_flags 15 Aug 13 23:38:09 192.168.50.101 RATE 10: ratekbps 48000 rate_flags 15 Aug 13 23:38:09 192.168.50.101 best_rate: 11 Aug 13 23:38:09 192.168.50.101 [56256.513866] final rate: 11 flags: 15 Aug 13 23:38:09 192.168.50.101 [56256.513871] returning rate on case 3 Aug 13 23:38:09 192.168.50.101 rate_table_size: 12 Aug 13 23:38:09 192.168.50.101 [56256.513900] rate_max_phy: 11 Aug 13 23:38:09 192.168.50.101 [56256.513902] max_valid_rate: 10 Aug 13 23:38:09 192.168.50.101 [56256.513912] RATE 0: ratekbps 1000 rate_flags 15 Aug 13 23:38:09 192.168.50.101 RATE 1: ratekbps 2000 rate_flags 15 Aug 13 23:38:09 192.168.50.101 RATE 2: ratekbps 5500 rate_flags 15 Aug 13 23:38:09 192.168.50.101 RATE 3: ratekbps 11000 rate_flags 15 Aug 13 23:38:09 192.168.50.101 RATE 4: ratekbps 6000 rate_flags 0 Aug 13 23:38:09 192.168.50.101 RATE 5: ratekbps 9000 rate_flags 0 Aug 13 23:38:09 192.168.50.101 RATE 6: ratekbps 12000 rate_flags 15 Aug 13 23:38:09 192.168.50.101 RATE 7: ratekbps 18000 rate_flags 15 Aug 13 23:38:09 192.168.50.101 RATE 8: ratekbps 24000 rate_flags 15 Aug 13 23:38:09 192.168.50.101 RATE 9: ratekbps 36000 rate_flags 15 Aug 13 23:38:09 192.168.50.101 RATE 10: ratekbps 48000 rate_flags 15 Aug 13 23:38:09 192.168.50.101 best_rate: 11 Aug 13 23:38:09 192.168.50.101 [56256.513992] final rate: 11 flags: 15 Aug 13 23:38:09 192.168.50.101 [56256.513997] returning rate on case 3 Aug 13 23:38:09 192.168.50.101 rate_table_size: 12 Aug 13 23:38:09 192.168.50.101 [56256.518708] rate_max_phy: 11 Aug 13 23:38:09 192.168.50.101 [56256.518712] max_valid_rate: 10 Aug 13 23:38:09 192.168.50.101 [56256.518745] RATE 0: ratekbps 33554432 rate_flags 0 Aug 13 23:38:09 192.168.50.101 RATE 1: ratekbps 67174400 rate_flags 0 Aug 13 23:38:09 192.168.50.101 RATE 2: ratekbps 184680448 rate_flags 0 Aug 13 23:38:09 192.168.50.101 RATE 3: ratekbps 369295360 rate_flags 0 Aug 13 23:38:09 192.168.50.101 RATE 4: ratekbps 201588736 rate_flags 0 Aug 13 23:38:09 192.168.50.101 RATE 5: ratekbps 302317568 rate_flags 0 Aug 13 23:38:09 192.168.50.101 RATE 6: ratekbps 403046400 rate_flags 0 Aug 13 23:38:09 192.168.50.101 RATE 7: ratekbps 604438528 rate_flags 0 Aug 13 23:38:09 192.168.50.101 RATE 8: ratekbps 805830656 rate_flags 0 Aug 13 23:38:09 192.168.50.101 RATE 9: ratekbps 1208549376 rate_flags 0 Aug 13 23:38:09 192.168.50.101 RATE 10: ratekbps 1611268096 rate_flags 0 i am not sure how this happening, all the data seems to be invalid. Aug 13 23:38:09 192.168.50.101 best_rate: 8 Aug 13 23:38:09 192.168.50.101 [56256.518815] final rate: 8 flags: 0 Aug 13 23:38:09 192.168.50.101 [56256.518821] [ cut here ] Aug 13 23:38:09 192.168.50.101 [56256.518842] WARNING: at /home/catalin/work/suitable/compat-wireless/compat-wireless-2011-08-08/drivers/net/wireless/ath/ath9k/rc.c:713 ath_get_rate+0x217/0x690 [ath9k]() Aug 13 23:38:09 192.168.50.101 [56256.518854] Hardware name: SG3-360FR Aug 13 23:38:09 192.168.50.101 [56256.518859] Modules linked in: Aug 13 23:38:09 192.168.50.101 cryptd Aug 13 23:38:09 192.168.50.101 aes_x86_64 Aug 13 23:38:09 192.168.50.101 aes_generic Aug 13 23:38:09 192.168.50.101 ath9k Aug 13 23:38:09 192.168.50.101 mac80211 Aug 13 23:38:09 192.168.50.101 ath9k_common Aug 13 23:38:09 192.168.50.101 ath9k_hw Aug 13 23:38:09 192.168.50.101 ath Aug 13 23:38:09 192.168.50.101 cfg80211 Aug 13 23:38:09 192.168.50.101 compat Aug 13 23:38:09 192.168.50.101 pcmcia_core Aug 13 23:38:09 192.168.50.101 led_class Aug 13 23:38:09 192.168.50.101 joydev Aug 13 23:38:09 192.168.50.101 hid_microsoft Aug 13 23:38:09 192.168.50.101 hid_belkin Aug 13 23:38:09 192.168.50.101 xt_tcpudp Aug 13 23:38:09 192.168.50.101 iptable_filter Aug 13 23:38:09 192.168.50.101 ip_tables Aug 13 23:38:09 192.168.50.101 x_tables Aug 13 23:38:09 192.168.50.101 binfmt_misc Aug 13 23:38:09 192.168.50.101 ppdev Aug 13 23:38:09 192.168.50.101 snd_hda_codec_realtek Aug 13 23:38:09 192.168.50.101 arc4
Re: [ath9k-devel] Packet loss regression with Atheros AR9280
On Sat, Aug 13, 2011 at 4:51 PM, Jan Sundman jan.sund...@aland.net wrote: Hi, I'm not sure whether you have found a solution to this issue yet but I thought that I should share my findings. I'm running Arch linux on my laptop which have the AR9280 and I saw massive packet loss as well. is it an in built card? I noticed however that this _only_ occurred when the laptop was on battery power. So it seems to be due to some power save functionality for the card. if its an in built card, then this looks like a platform issue, if so please use http://www.kernel.org/pub/linux/kernel/people/mcgrof/scripts/cpudmalatency.c http://johannes.sipsolutions.net/files/netlatency.c.txt iwconfig wlan0 power off seems to fix it so I added this to my startup script and this fixes it. This is of course not a optimal solution but may point you in the right direction on fixing the problem. Br, /Jan On 12 August 2011 10:27, Robert O'Callahan rob...@ocallahan.org wrote: Anything I can get building with this kernel, I guess. Any particular version I should try? I'd suggest going back a month at a time (http://www.orbit-lab.org/kernel/compat-wireless-2.6/2011/), try each until you find one that works, then report compat-wireless X works, compat-wireless Y doesn't. That'll be a good way to test multiple copies of the development wireless tree. If someone Fedora-clued knows which version(s) of the wireless code are involved with Robert's good and bad behaviour reports, that'll also help. Anything to kick-start a git bisect :-) Ciao, Adrian ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] ath9k power save in AP mode
On Fri, Aug 12, 2011 at 8:04 AM, Harsha Chenji cjker...@gmail.com wrote: Hello list, I was trying to get PSM working with a ath9k and a broadcom based STA (which works with other APs). However, in ath9k's debugfs, total_ps_buffered reads 0. iwconfig shows that power management is on. Still, the STA doesnt do any PSM, which means the AP is not sending PSM frames. please enable CONFIG_MAC80211_VERBOSE_PS_DEBUG in your compat wireless to get more information Could someone please help? compat wireless ver. is 2010-12-09, and has proper iw/iwconfig which support nl80211 based power save API on a 2.6.36.2 kernel. AP power save supports is handled in mac80211, pleast try with the latest compat wireless, one fix related we might be missing in ath9k is.. commit 5519541d5a5f19893546883547e2f0f2e5934df7 Author: Felix Fietkau n...@openwrt.org Date: Sun Apr 17 23:28:09 2011 +0200 ath9k: fix powersave frame filtering/buffering in AP mode Thanks ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] Can't get ath9k_htc to load firmware, target not responsive
On Fri, Aug 12, 2011 at 2:23 PM, Ming-Ching Tiew mct...@yahoo.com wrote: I am using kernel 3.0.1 with compat-wireless backport v3.0-2, and TL WN722N. The system is compiled based on openwrt trunk sdk. I am using htc_9271.fw version 1.3 downloaded from http://wireless.kernel.org/download/htc_fw/; The image when I run natively it is able to download firmware into the usb adapter. Haven't tested if it is working, but at least firmware was loaded, and the device was started in AP mode. However when I run it inside virtualbox 4.1.0, it says target is unresponsive :- please provide your vendor id and device id. thanks! usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272 ath9k_htc 1-1:1.0: ath9k_htc: Target is unresponsive Failed to initialize the device Anything I can do about it ? Thanks ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] Can't get ath9k_htc to load firmware, target not responsive
On Fri, Aug 12, 2011 at 2:34 PM, Mohammed Shafi shafi.wirel...@gmail.com wrote: On Fri, Aug 12, 2011 at 2:23 PM, Ming-Ching Tiew mct...@yahoo.com wrote: I am using kernel 3.0.1 with compat-wireless backport v3.0-2, and TL WN722N. The system is compiled based on openwrt trunk sdk. I am using htc_9271.fw version 1.3 downloaded from http://wireless.kernel.org/download/htc_fw/; The image when I run natively it is able to download firmware into the usb adapter. Haven't tested if it is working, but at least firmware was loaded, and the device was started in AP mode. However when I run it inside virtualbox 4.1.0, it says target is unresponsive :- please provide your vendor id and device id. thanks! if this already a supported device by ath9k_htc then http://www.mailrepository.com/ath9k-devel.lists.ath9k.org/msg/3249192/ usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272 ath9k_htc 1-1:1.0: ath9k_htc: Target is unresponsive Failed to initialize the device Anything I can do about it ? Thanks ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] Can't get ath9k_htc to load firmware, target not responsive
On Fri, Aug 12, 2011 at 3:04 PM, Ming-Ching Tiew mct...@yahoo.com wrote: --- On Fri, 8/12/11, Mohammed Shafi shafi.wirel...@gmail.com wrote: if this already a supported device by ath9k_htc then http://www.mailrepository.com/ath9k-devel.lists.ath9k.org/msg/3249192/ Sorry I am not exactly sure what is required here. I have read the thread prior to my post. Basically the link you post, did not have a resolution. There is another thread ( probably a continuation of the one above ), which the final resolution seems to be :- 1) A patch to the driver, and/or 2) A patch to the firmware. sorry i am not aware of that thread, can you please post the link and the related patch? But I am using a more recent kernel and more recent compat-wireless. I have looked through the sources, it seems the driver patch mentioned has already been included into compat-wireless 3.0-2. As for the firmware, I am using htc_9271.fw version 1.3. The previous post, since are based on older compat-wirelss, are using ar9271.fw. yes, thats the right firmware. Also the SAME boot image when I load it into the a USB flash and boot on a native machine without going through the virtual machine, things are working. It's not working in virtualbox VM. Some timing issues ? so did you try to increase the timeout in Firmware can take up to 50ms to get ready, to be safe use 1 second */ time_left = wait_for_completion_timeout(priv-htc-target_wait, HZ); Best regards. ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] Kernel panic with compat-wireless-2011-07-28
Both interfaces are in station mode. The APs (simulated with Atheros adapters on a different machine) constantly go up and down and change encryption settings, frequency and 802.11n mode (also changing BSSID everytime they came up in a new configuraiton). Hi Catalin, I am unable to recreate the issue here. I just had tried with one station AR9280 in a reasonably noisy environment and sending UDP traffic. I am in wireless-testing 3.1.0-rc1-wl, compiled from the updates obtained few days before. i found from your lspci you have two AR9280 cards active in your machine(may be one inbuilt?) and sending traffic, I cannot simulate the same scenario here. I started to looking at the code and see if there is anything missing. i will also keep running the test. if you are able to recreate the issue with the issue by running a simple UDP traffic between 1 STA and 1 AP it will be great. please try to use the bleeding edge compat-wireless http://wireless.kernel.org/download/compat-wireless-2.6/compat-wireless-2.6.tar.bz2 and please post the panic trace. if you are used to compile wireless-testing, please pull the latest version and obtain the call trace. so that I may able to get the exact line where the kernel is getting paniced with gdb. I am just assuming whatever call trace you had given for debugging. hope i would get the issue here. thanks for your help! -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] ath9k: Network stalls every 30 seconds
On Wed, Aug 10, 2011 at 3:38 AM, Robert Högberg robert.hogb...@gmail.com wrote: Hi, I know NetworkManager scans the network every two minutes. I've had problems with this and disabled it by explicitly setting a BSSID so this is not a problem anymore. I have verified that my problem is related to the noise floor calibrations by modifying the ATH_LONG_CALINTERVAL constant within the ath9k driver. My network freezes each time that calibration timer is triggered. And, if I completely disable the calibrations I have no problems at all. there is a option to disable ani in ath9k via debugfs (/sys/kernel/debug/ieee80211/phy/ath9k/disable_ani) please echo 1 to it and test. I've seen the problem on both Ubuntu 11.04 and Fedora 15, but Windows 7 and FreeBSD seem to work well. Thanks for keeping an eye on this problem Adrian. It was my intention to get back to the ath9k devel list when I had done some more testing on FreeBSD, but I've had some problems getting FreeBSD up and running properly and I've been short on time. When installing FreeBSD the computer locks up when it tries to connect to my AP. I believe this may be caused by WPA because when I first tried FreeBSD using the live CD I disabled the encryption to simplify my testing and then all worked well. But, I would like to do some more tests before I can tell what seems to cause the crashes. Adrian, can you verify that also the FreeBSD driver performs calibrations every 30 seconds? I'll try to get my FreeBSD installation up and running and see if I can get some debug information from there. Is there's something particularly interesting I should try in FreeBSD? Can I get some kind of debug data without recompiling the kernel/ath module? Can I get a backtrace or similar information from a crashed system? Robert 2011/8/9 Galen gal...@zinkconsulting.com: I haven't reviewed the full thread here - but have you made 100% sure that there is not some kind of WiFi connection manager running in the background on the Linux system? Just something to double check... those connection managers frequently probe and cause network stalls, particularly at specific, likely human-programmed intervals (e.g. 30 seconds) like you're describing... Sure, it's stupidly simple, but Linux distros have deeply embedded WiFi connection managers and people sometimes miss them... -Galen On Aug 8, 2011, at 6:13 PM, Adrian Chadd wrote: .. sorry, he isn't having issues with the AR5416 on FreeBSD but is under ath9k. (Wow, is this the second time FreeBSD works where ath9k doesn't? I may have to throw a little private party :-) Would someone like to take up the challenge? I'll help you wade through the HAL if you'd like. Adrian On 9 August 2011 09:12, Adrian Chadd adr...@freebsd.org wrote: Hi all, I'm just forwarding what Robert said. FreeBSD doesn't have the same interruptions as ath9k does on the AR5416. I don't have the time to go digging myself just now. On 3 August 2011 05:37, Robert Högberg robert.hogb...@gmail.com wrote: An update to previous mail.. I tried the i386 version of FreeBSD 9.0 beta (instead of amd64) and that one worked much, much better. No network interruptions every 30 seconds in FreeBSD 9.0 beta 1, but I only ran the test for a few minutes. Would you expect the noise floor calibrations to happen every 30 seconds in FreeBSD also or is the interval different there? I'll continue investigating. (You may want to look into why the ath driver doesn't work on amd64..) Robert 2011/8/2 Robert Högberg robert.hogb...@gmail.com: I tried FreeBSD and the computer crashed when I tried to enable the WLAN. I'm no FreeBSD user so I'm not sure I got things right, but here's what I did: * Boot FreeBSD from USB stick (WLAN device was detected correctly and ath0 created) * ifconfig wlan0 create wlandev ath0 * ifconfig wlan0 up (This caused the computer to freeze. No output, and no input possible. I waited minutes but nothing happened.) I attach dmesg output after boot. /Robert 2011/8/2 Adrian Chadd adr...@freebsd.org: Ah, that it works well in Windows is a good sign. Would you mind doing me a favour? Could you spin up FreeBSD-9.0-BETA1 on a temporary disk (eg a USB thumb drive) and see if it exhibits the same behaviour? Adrian On 2 August 2011 04:19, Robert Högberg robert.hogb...@gmail.com wrote: 2011/7/30 Adrian Chadd adr...@freebsd.org: Have you tried another ath9k NIC? Another AR5416 NIC? I've tried an AR9271 NIC (USB ID 0cf3:9271) and it works very well. I only have one AR5416 NIC to test I'm afraid. Is it possible this NIC is slightly weirdly damaged? Maybe, but the card works well with the Windows 7 drivers. But I guess it's possible that the noise floor calibration functionality is broken/problematic on this card and the Windows driver knows this and avoids or adapts to the problem. After all, I don't see any problems with the calibration disabled so
Re: [ath9k-devel] about mac80211 architeture
On Thu, Aug 11, 2011 at 2:27 PM, pangyunong 029...@gmail.com wrote:
hi ,
I read the code all along today. I just know hostAP control nl80211
which is upper the cfg80211 and mac80211.
And then I read mac80211, but all functions are provided to be used by
upper layer. There is something confusing me.
Like that ieee80211_beacon_get_tim(), it is a generating beacon
function. But it only responses for generating a template of Beacon
frame, where its beacon timer to be set?
based on SWBA Software Beacon Alert Interrupt. please grep for
ATH9K_INT_SWBA, it provides more idea.
But why ath9k/beacon.c will call these interface provided by mac80211?
is this architecture right?
some more functions that were called are
{ 0x5d8b5707, ieee80211_queue_work },
{ 0x9c64fbd, ieee80211_frequency_to_channel },
{ 0x7514a8c3, ieee80211_beacon_get_tim },
{ 0x76bedf4e, ieee80211_unregister_hw },
{ 0xb45657d2, ieee80211_iterate_active_interfaces_atomic },
{ 0x52621d21, ieee80211_stop_queues },
{ 0xebf90528, ieee80211_stop_queue },
{ 0x17e071d0, ieee80211_tx_status },
{ 0x7e86ca89, ieee80211_rate_control_register },
{ 0xc8319d94, ieee80211_wake_queues },
{ 0x766fbc0e, ieee80211_rx },
{ 0x745211f8, ieee80211_find_sta_by_ifaddr },
{ 0x3cc930bc, ieee80211_queue_delayed_work },
{ 0xf36854a6, wiphy_to_ieee80211_hw },
{ 0x9b6d091e, ieee80211_stop_tx_ba_cb_irqsafe },
{ 0x80b77801, ieee80211_get_buffered_bc },
{ 0x3bd3c60e, ieee80211_wake_queue },
{ 0xb695fd7b, __ieee80211_get_radio_led_name },
{ 0x348bcbb, ieee80211_get_hdrlen_from_skb },
{ 0xefac7fe4, ieee80211_rate_control_unregister },
{ 0xab37adee, __ieee80211_create_tpt_led_trigger },
{ 0x23849a62, ieee80211_register_hw },
{ 0x386a2172, ieee80211_sta_set_tim },
{ 0xac653cb0, ieee80211_start_tx_ba_session },
{ 0x805d7dd7, ieee80211_alloc_hw },
{ 0x5c1501cd, ieee80211_free_hw },
{ 0xdb101d74, ieee80211_start_tx_ba_cb_irqsafe },
Yunong Pang
Regards,
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
--
shafi
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] Kernel panic with compat-wireless-2011-07-28
On Fri, Aug 12, 2011 at 3:26 AM, Catalin Drula catalin.dr...@personalnetworks.ro wrote: Hi, I get the following kernel panic after a few hours of stress testing (continuous associations and sending data through) two Atheros AR928X devices. thanks for reporting. *please provide lspci -xxx *are you having one AR928X as AP and the other as station? Environment info: - Ubuntu 10.04.3 LTS - kernel 2.6.32-33-generic x86_64 - compat-wireless-2011-07-28 Aug 11 13:30:52 192.168.50.101 [175277.554563] ath: Aug 11 13:30:52 192.168.50.101 Failed to stop TX DMA! Aug 11 14:31:05 192.168.50.101 [178889.524658] ath: Aug 11 14:31:05 192.168.50.101 Failed to stop TX DMA! Aug 11 14:59:01 192.168.50.101 [180564.555107] ath: Aug 11 14:59:01 192.168.50.101 Failed to stop TX DMA! Aug 11 15:45:36 192.168.50.101 [183359.534036] ath: Aug 11 15:45:36 192.168.50.101 Failed to stop TX DMA! Aug 11 16:20:50 192.168.50.101 [185473.117808] ath: Aug 11 16:20:50 192.168.50.101 Failed to stop TX DMA! Aug 11 16:20:54 192.168.50.101 [185477.136682] ath: Aug 11 16:20:54 192.168.50.101 Failed to stop TX DMA! Aug 11 16:20:54 192.168.50.101 [185477.143343] ath: Aug 11 16:20:54 192.168.50.101 Failed to stop TX DMA! Aug 11 16:29:14 192.168.50.101 [185976.524928] ath: Aug 11 16:29:14 192.168.50.101 Failed to stop TX DMA! Aug 11 16:51:20 192.168.50.101 [187302.444025] ath: Aug 11 16:51:20 192.168.50.101 Failed to stop TX DMA! Aug 11 16:51:20 192.168.50.101 [187302.444354] [ cut here ] Aug 11 16:51:20 192.168.50.101 [187302.444362] kernel BUG at /home/catalin/work/suitable/compat-wireless/compat-wireless-2011-07-28/net/mac80211/rate.c:353! Aug 11 16:51:20 192.168.50.101 [187302.444365] invalid opcode: [#1] Aug 11 16:51:20 192.168.50.101 SMP Aug 11 16:51:20 192.168.50.101 Aug 11 16:51:20 192.168.50.101 [187302.444370] last sysfs file: /sys/devices/pci:00/:00:11.0/host0/target0:0:0/0:0:0:0/block/sda/uevent Aug 11 16:51:20 192.168.50.101 [187302.444373] CPU 1 Aug 11 16:51:20 192.168.50.101 Aug 11 16:51:20 192.168.50.101 [187302.444375] Modules linked in: Aug 11 16:51:20 192.168.50.101 xt_tcpudp Aug 11 16:51:20 192.168.50.101 iptable_filter Aug 11 16:51:20 192.168.50.101 ip_tables Aug 11 16:51:20 192.168.50.101 x_tables Aug 11 16:51:20 192.168.50.101 cryptd Aug 11 16:51:20 192.168.50.101 aes_x86_64 Aug 11 16:51:20 192.168.50.101 aes_generic Aug 11 16:51:20 192.168.50.101 joydev Aug 11 16:51:20 192.168.50.101 hid_microsoft Aug 11 16:51:20 192.168.50.101 hid_belkin Aug 11 16:51:20 192.168.50.101 binfmt_misc Aug 11 16:51:20 192.168.50.101 ppdev Aug 11 16:51:20 192.168.50.101 snd_hda_codec_realtek Aug 11 16:51:20 192.168.50.101 arc4 Aug 11 16:51:20 192.168.50.101 snd_hda_intel Aug 11 16:51:20 192.168.50.101 snd_hda_codec Aug 11 16:51:20 192.168.50.101 snd_hwdep Aug 11 16:51:20 192.168.50.101 snd_pcm_oss Aug 11 16:51:20 192.168.50.101 snd_mixer_oss Aug 11 16:51:20 192.168.50.101 snd_pcm Aug 11 16:51:20 192.168.50.101 snd_seq_dummy Aug 11 16:51:20 192.168.50.101 snd_seq_oss Aug 11 16:51:20 192.168.50.101 snd_seq_midi Aug 11 16:51:20 192.168.50.101 snd_rawmidi Aug 11 16:51:20 192.168.50.101 snd_seq_midi_event Aug 11 16:51:20 192.168.50.101 snd_seq Aug 11 16:51:20 192.168.50.101 ath9k Aug 11 16:51:20 192.168.50.101 netconsole Aug 11 16:51:20 192.168.50.101 configfs Aug 11 16:51:20 192.168.50.101 mac80211 Aug 11 16:51:20 192.168.50.101 snd_timer Aug 11 16:51:20 192.168.50.101 snd_seq_device Aug 11 16:51:20 192.168.50.101 ath9k_common Aug 11 16:51:20 192.168.50.101 fbcon Aug 11 16:51:20 192.168.50.101 tileblit Aug 11 16:51:20 192.168.50.101 font Aug 11 16:51:20 192.168.50.101 bitblit Aug 11 16:51:20 192.168.50.101 softcursor Aug 11 16:51:20 192.168.50.101 ath9k_hw Aug 11 16:51:20 192.168.50.101 ath Aug 11 16:51:20 192.168.50.101 snd Aug 11 16:51:20 192.168.50.101 fglrx(P) Aug 11 16:51:20 192.168.50.101 vga16fb Aug 11 16:51:20 192.168.50.101 vgastate Aug 11 16:51:20 192.168.50.101 lp Aug 11 16:51:20 192.168.50.101 cfg80211 Aug 11 16:51:20 192.168.50.101 compat Aug 11 16:51:20 192.168.50.101 psmouse Aug 11 16:51:20 192.168.50.101 serio_raw Aug 11 16:51:20 192.168.50.101 parport Aug 11 16:51:20 192.168.50.101 i2c_piix4 Aug 11 16:51:20 192.168.50.101 soundcore Aug 11 16:51:20 192.168.50.101 snd_page_alloc Aug 11 16:51:20 192.168.50.101 pcmcia_core Aug 11 16:51:20 192.168.50.101 led_class Aug 11 16:51:20 192.168.50.101 edac_core Aug 11 16:51:20 192.168.50.101 edac_mce_amd Aug 11 16:51:20 192.168.50.101 shpchp Aug 11 16:51:20 192.168.50.101 usbhid Aug 11 16:51:20 192.168.50.101 hid Aug 11 16:51:20 192.168.50.101 usb_storage Aug 11 16:51:20 192.168.50.101 r8169 Aug 11 16:51:20 192.168.50.101 mii Aug 11 16:51:20 192.168.50.101 ahci Aug 11 16:51:20 192.168.50.101 Aug 11 16:51:20 192.168.50.101 [187302.444652] Pid: 17614, comm: python Tainted: P W 2.6.32-33-generic #71-Ubuntu SG3-360FR Aug 11 16:51:20
Re: [ath9k-devel] ath9k: Network stalls every 30 seconds
On Thu, Aug 11, 2011 at 11:43 PM, Robert Högberg robert.hogb...@gmail.com wrote: 2011/8/11 Mohammed Shafi shafi.wirel...@gmail.com: On Wed, Aug 10, 2011 at 3:38 AM, Robert Högberg robert.hogb...@gmail.com wrote: I have verified that my problem is related to the noise floor calibrations by modifying the ATH_LONG_CALINTERVAL constant within the ath9k driver. My network freezes each time that calibration timer is triggered. And, if I completely disable the calibrations I have no problems at all. there is a option to disable ani in ath9k via debugfs (/sys/kernel/debug/ieee80211/phy/ath9k/disable_ani) please echo 1 to it and test. Disabling ani seems to also fix the problem. What does this indicate? that just completely disables the ANI algorithm running in ath9k, so it looks like there is some problem in ANI for your card. I used bleeding edge compat-wireless when testing. so the problem occurs even with bleeding edge compat-wireless. Robert -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] is nl80211 being used now?
On Wed, Aug 10, 2011 at 10:39 PM, pangyunong 029...@gmail.com wrote: Hi all, I see something in http://linuxwireless.org/en/developers/Documentation/nl80211 it said nl80211 still be under development. does the current version we use use nl80211 already? yes, when we use a command like iw dev wlan0 set type managed we are using nl80211 - About nl80211 nl80211 is the new 802.11 netlink interface public header. Together with cfg80211 it is intended to replace Wireless-Extensions. nl80211 and cfg80211 still under development. - thanks, Yunong Pang Regards, ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] Atheros 5416 on a D-Link DWA-552 in host mode bug
On Tue, Aug 9, 2011 at 9:55 AM, Bugs fr...@solprime.net wrote: Hi, I am trying to run a Atheros 5416 on a D-Link DWA-552 in host mode for 802.11n I seem to be having a problem that looks like the one patched in https://patchwork.kernel.org/patch/694461/ however I am running the current driver, and at least mac.c seems to match that patch, and still have this issue when starting host mode. I am new to HostAP and have spent a considerable amount of time working on this issue, and I hope I am not wasting your time, but I think this is a legitimate bug I am experiencing. hi, we will try to recreate it here, also its a bit of old card. Here are some details: Linux kernel 3.0.1 Full Kernel config at: http://pastebin.com/f3BZpVVd Likely relevant kernel config: http://pastebin.com/RHHguFvF dmesg right after starting hostapd: http://pastebin.com/XL5shUxZ hostapd config: http://pastebin.com/6au0qajF I am willing to test code if anyone has patches to try. If this is not a bug, I apologize for taking up your time and would appreciate any suggestions on what to read / google to get this working. Thank you for your time. Fred Dinkler IV ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] The difference between ath9k and ar9170
On Thu, Aug 4, 2011 at 10:21 PM, pangyunong 029...@gmail.com wrote: Hello, Is it ath9k more complex than ar9170? do you know something about the difference between them? which you prefer? no, i don't know. Ccing list and carl9170 maintainer. I have seen into the code and found the architecture of ar9170 is more concise than the ath9k... Could I ask for help with ar9170 in the list? http://wireless.kernel.org/en/users/Drivers/carl9170 I want to insert my own module with modified driver and what kinds of device I needs? Is it any device containing ath9k or ar9170 chipset can use these drivers that published here? Thanks a lot for your help! Yunong Pang Regards, -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] eeprom txGainType overridden if minor version 19
On Wed, Aug 3, 2011 at 12:33 PM, Marek Lindner lindner_ma...@yahoo.de wrote: On Wednesday, August 03, 2011 08:48:12 Adrian Chadd wrote: Hm, I just checked the reference code and it doesn't at all look like that check is actually needed; it's only needed for Merlin. So, good catch! Thanks for the info! I'll fix FreeBSD; who wants to fix ath9k? :) I could post the patch I am already using. It goes to linux-wireless, right ? also please do mention, what it fixes. Regards, Marek -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] Important misprint in ar9003_phy.h
On Tue, Aug 2, 2011 at 1:25 PM, Alex Hacker hac...@epn.ru wrote: I think it looks like misprint which can lead to incorrect calibration process. true. looks like a typo, I will check with Vasanth. thanks. --- ar9003_phy.h.orig 2011-08-01 09:53:05.0 +0600 +++ ar9003_phy.h 2011-08-02 13:47:07.0 +0600 @@ -850,7 +850,7 @@ #define AR_PHY_TPC_11_B1 (AR_SM1_BASE + 0x220) #define AR_PHY_PDADC_TAB_1 (AR_SM1_BASE + 0x240) #define AR_PHY_TX_IQCAL_STATUS_B1 (AR_SM1_BASE + 0x48c) -#define AR_PHY_TX_IQCAL_CORR_COEFF_B1(_i) (AR_SM_BASE + 0x450 + ((_i) 2)) +#define AR_PHY_TX_IQCAL_CORR_COEFF_B1(_i) (AR_SM1_BASE + 0x450 + ((_i) 2)) /* * Channel 2 Register Map Best regrads, Alex. -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] Important misprint in ar9003_phy.h
On Tue, Aug 2, 2011 at 1:40 PM, Mohammed Shafi shafi.wirel...@gmail.com wrote: On Tue, Aug 2, 2011 at 1:25 PM, Alex Hacker hac...@epn.ru wrote: I think it looks like misprint which can lead to incorrect calibration process. true. looks like a typo, I will check with Vasanth. thanks. this change looks fine. Alex, please send a patch to wireless-testing. thanks. --- ar9003_phy.h.orig 2011-08-01 09:53:05.0 +0600 +++ ar9003_phy.h 2011-08-02 13:47:07.0 +0600 @@ -850,7 +850,7 @@ #define AR_PHY_TPC_11_B1 (AR_SM1_BASE + 0x220) #define AR_PHY_PDADC_TAB_1 (AR_SM1_BASE + 0x240) #define AR_PHY_TX_IQCAL_STATUS_B1 (AR_SM1_BASE + 0x48c) -#define AR_PHY_TX_IQCAL_CORR_COEFF_B1(_i) (AR_SM_BASE + 0x450 + ((_i) 2)) +#define AR_PHY_TX_IQCAL_CORR_COEFF_B1(_i) (AR_SM1_BASE + 0x450 + ((_i) 2)) /* * Channel 2 Register Map Best regrads, Alex. -- shafi -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] eeprom txGainType overridden if minor version 19
On Tue, Aug 2, 2011 at 1:58 PM, Marek Lindner lindner_ma...@yahoo.de wrote: Hi, I was having some output power problems with a device using AR7240/AR9285. After digging into the ath9k driver I realized that it would override the power settings (txGainType) configured in the eeprom if the minor version does not meet its expectations. This is why it would not use the appropriate high power settings. The offending lines from eeprom_4k.c: if (ver_minor = AR5416_EEP_MINOR_VER_19) return pBase-txGainType; else return AR5416_EEP_TXGAIN_ORIGINAL; My minor version is 14 and consequently fell through the cracks. The commit introducing the check in question was 970bf9d40c03e48cc34ee2c1a70693a0e0fca3f6 but it does not explain why the minor version has to be 19 or higher. Does anyone know the magic behind version 19 ? I could easily post a patch to remove that check if it causes no harm. lets be careful while changing this, we must also note things like, /* PA CAL is not needed for high power solution */ if (ah-eep_ops-get_eeprom(ah, EEP_TXGAIN_TYPE) == AR5416_EEP_TXGAIN_HIGH_POWER) return; Regards, Marek ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] eeprom txGainType overridden if minor version 19
On Tue, Aug 2, 2011 at 3:45 PM, Marek Lindner lindner_ma...@yahoo.de wrote: On Tuesday, August 02, 2011 12:09:59 Mohammed Shafi wrote: lets be careful while changing this, we must also note things like, /* PA CAL is not needed for high power solution */ if (ah-eep_ops-get_eeprom(ah, EEP_TXGAIN_TYPE) == AR5416_EEP_TXGAIN_HIGH_POWER) return; I have that seen too and disabled that check in my code but I intended to make further tests before bringing this up. Let me emphasize again that the correct eeprom value is returned once your minor version is 19 or above. Only the smaller versions are overridden by the driver. Therefore I don't see a direct relation to the code you posted. Can you clarify ? if the ver 19 then we are sure that the code will never return from the above check ? am i missing something ? Regards, Marek -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] eeprom txGainType overridden if minor version 19
On Tue, Aug 2, 2011 at 8:07 PM, Marek Lindner lindner_ma...@yahoo.de wrote: On Tuesday, August 02, 2011 13:13:27 Adrian Chadd wrote: Right, so it's an embedded board inside a wireless router? Which router? :) The OM2P but how is this going to help ? I have the feeling we are not getting closer to answer my question: Why does ath9k_hw_4k_get_eeprom() requires the minor version 19 or above before even considering to read the eeprom value ? Can I propose a patch that removes that check ? I already have that patch working for me - just wanted to be sure it does no harm. hi, yes, looks like the check should not be there for common, but I don't know for what reason the developer made it as a common check. let me check it out. please wait. does any one has any comments. can you please share what is the issue you are issuing Regards, Marek ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] eeprom txGainType overridden if minor version 19
On Tue, Aug 2, 2011 at 8:36 PM, Mohammed Shafi shafi.wirel...@gmail.com wrote: On Tue, Aug 2, 2011 at 8:07 PM, Marek Lindner lindner_ma...@yahoo.de wrote: On Tuesday, August 02, 2011 13:13:27 Adrian Chadd wrote: Right, so it's an embedded board inside a wireless router? Which router? :) The OM2P but how is this going to help ? I have the feeling we are not getting closer to answer my question: Why does ath9k_hw_4k_get_eeprom() requires the minor version 19 or above before even considering to read the eeprom value ? Can I propose a patch that removes that check ? I already have that patch working for me - just wanted to be sure it does no harm. hi, yes, looks like the check should not be there for common, but I don't know for what reason the developer made it as a common check. let me check it out. please wait. does any one has any comments. can you please share what is the issue you are issuing adding the people who made those changes, I am also unable to understand. verified with the internal code base, the check was not there. Regards, Marek ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] Some novice questions
On Sat, Jul 30, 2011 at 8:56 PM, pangyunong 029...@gmail.com wrote: Hi, I'm very excited in the list. It's my first time to use a mailing list, so I'm afraid there are some impolite to you. If there, please tell me. I have some question about mailing list of ath9k. I want modify NAV value of a MAC frame when sending any frame using AP mode in ath9k. But I have never touch network card driver before, how can I learn that by myself? Could you give me some advices? Thank you very much. The AR_NAV (with offset 0X8084) is the register that provides NAV value. I don't think it can be controlled by software. Regards, Yunong Pang ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] Some novice questions
On Mon, Aug 1, 2011 at 3:00 PM, pangyunong 029...@gmail.com wrote: Thank you for your reply! But how can it be modified NAV to be 0 each time I transmit a frame? Can I control the value by flashing the firmware in my network card? no, there is no firmware for ath9k. i tried to force the value of the same via debug some random value... anyway it always shows 0 /sys/kernel/debug/ieee80211/phy0/ath9k# echo 0x8084 regidx cat regval echo 0x5678 regval On Mon, 2011-08-01 at 14:43 +0530, Mohammed Shafi wrote: On Sat, Jul 30, 2011 at 8:56 PM, pangyunong 029...@gmail.com wrote: Hi, I'm very excited in the list. It's my first time to use a mailing list, so I'm afraid there are some impolite to you. If there, please tell me. I have some question about mailing list of ath9k. I want modify NAV value of a MAC frame when sending any frame using AP mode in ath9k. But I have never touch network card driver before, how can I learn that by myself? Could you give me some advices? Thank you very much. The AR_NAV (with offset 0X8084) is the register that provides NAV value. I don't think it can be controlled by software. Regards, Yunong Pang ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] Atheros WiFi only works when I reboot from windows.
On Fri, Jul 29, 2011 at 5:07 PM, Vic Demuzere v...@demuzere.be wrote: On 29 July 2011 12:41, Mohammed Shafi shafi.wirel...@gmail.com wrote: please provide lspci I have attached the output of lspci. what is the kernel version you are using , can you get debug messages http://linuxwireless.org/en/users/Drivers/ath9k/debug I'm currently on kernel 2.6.39-ARCH. Is it really necessary to compile a new kernel to enable debug messages? I've never done that, and I'd like to avoid it if there is any other way.. yes, or can other option is to use compat wireless http://wireless.kernel.org/en/users/Download -- v...@demuzere.be :: http://vic.demuzere.be :: PGP: 0x6690CF94 My software never contains bugs, it just develops random features. -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] ath9k_htc, 2.6.36 and
On Sat, Jul 30, 2011 at 6:53 PM, Levi Civita tullio.levi.civ...@gmail.com wrote: Rajkumar Manoharan rmanoharan at atheros.com writes: On Fri, Dec 03, 2010 at 04:06:45PM +0530, Rajkumar Manoharan wrote: On Mon, Nov 22, 2010 at 09:17:16PM +0530, Petr Štetiar wrote: Mohammed Shafi shafi.wireless at gmail.com [2010-11-22 19:11:53]: Can you just please look into the status of CONFIG_PM in include/generated/autoconf.h, what is its value ? I don't use PM, so it's not in this file. Please apply the following patch and try again https://patchwork.kernel.org/patch/369751/ Please apply the following firmware patch on linux-firmware git then use the updated ar9271.fw http://marc.info/?l=linux-wirelessm=128214177613540w=3 -- Rajkumar ___ ath9k-devel mailing list ath9k-devel at lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel Hey guys, I have the exact same problem as described in this thread. I am not a Linux expert though. How do I apply the patch you linked above to the firmware? please jut download the ar9271.fw from (search ar9271.fw after you had gone into the link). http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git;a=tree interested in trying latest with compat wireless, read http://linuxwireless.org/en/users/Drivers/ath9k_htc Here is my dmesg log: $ grep ath9k /var/log/dmesg [ 23.842332] usb 1-3: ath9k_htc: Transferred FW: ar9271.fw, size: 51312 [ 24.841586] usb 1-3: ath9k_htc: Target is unresponsive [ 24.843046] ath9k_hif_usb: probe of 1-3:1.0 failed with error -22 [ 24.843087] usbcore: registered new interface driver ath9k_hif_usb Thanks! ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] Ubiquity SR71-E: direct probe timed out
On Fri, Jul 29, 2011 at 12:01 AM, Grant emailgr...@gmail.com wrote: I've installed my Ubiquity SR71-E with a PCIe adapter but I get: wlan0: direct probe to xx.xx.xx.xx.xx.xx (try 1/3) wlan0: direct probe to xx.xx.xx.xx.xx.xx (try 2/3) wlan0: direct probe to xx.xx.xx.xx.xx.xx (try 3/3) wlan0: direct probe to xx.xx.xx.xx.xx.xx timed out I'm connecting to a WPA2 AP and I'm using the same settings that work with an ath5k card. please provide the following details: *lspci *which version of compat wireless or wireless testing you are using *is it a noisy environment and how far is the distance between AP and Station. if you can please provide *wpa-supplicant version * does the same thing happens with no security? - Grant ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] Ubiquity SR71-E: direct probe timed out
On Fri, Jul 29, 2011 at 12:04 PM, Mohammed Shafi shafi.wirel...@gmail.com wrote: On Fri, Jul 29, 2011 at 12:01 AM, Grant emailgr...@gmail.com wrote: I've installed my Ubiquity SR71-E with a PCIe adapter but I get: wlan0: direct probe to xx.xx.xx.xx.xx.xx (try 1/3) wlan0: direct probe to xx.xx.xx.xx.xx.xx (try 2/3) wlan0: direct probe to xx.xx.xx.xx.xx.xx (try 3/3) wlan0: direct probe to xx.xx.xx.xx.xx.xx timed out I'm connecting to a WPA2 AP and I'm using the same settings that work with an ath5k card. please provide the following details: *lspci *which version of compat wireless or wireless testing you are using *is it a noisy environment and how far is the distance between AP and Station. if you can please provide *wpa-supplicant version * does the same thing happens with no security? we can identify if some thing is wrong, (like 4-way handshake timeout) by looking at /var/log/daemon.log and for this please enable the debugging messages in usr/share/dbus-1$ vi system-services/fi.epitest.hostap.WPASupplicant.service [D-BUS Service] Name=fi.epitest.hostap.WPASupplicant Exec=/sbin/wpa_supplicant -u -s -dKt User=root ~ ~ ~ ~ - Grant ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] Atheros WiFi only works when I reboot from windows.
On Fri, Jul 29, 2011 at 3:28 PM, Vic Demuzere v...@demuzere.be wrote: Hi there, I have a really strange issue with my Atheros WiFi card. It doesn't manage to connect to my wireless AP, except when I first boot windows and then reboot to Arch linux. So it looks like ath9k doesn't manage to start the card properly. Output from dmesg is the same in both cases, and the card correctly shows up in lspci. please provide lspci [sorcix@morpheus ~]$ dmesg | grep ath ath9k :01:0b.0: PCI INT A - Link[APC3] - GSI 18 (level, low) - IRQ 18 ath: EEPROM regdomain: 0x30 ath: EEPROM indicates we should expect a direct regpair map ath: Country alpha2 being used: AM ath: Regpair used: 0x30 ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control' Registered led device: ath9k-phy0 I tried Arch netcfg, networkmanager and manually using wpa_supplicant. When I didn't boot windows first, the card seems to connect to the AP, and then disconnect again. wlan0: deauthenticating from xx:xx:xx:xx:xx:xx by local choice (reason=3) It then starts looping trying to reconnect. After first booting into windows, it simply connects and stays connected. Everything works fine then. Note that it always works fine in windows, so it isn't a hardware problem. Does anyone else have this problem, or knows how to fix it? what is the kernel version you are using , can you get debug messages http://linuxwireless.org/en/users/Drivers/ath9k/debug -- v...@demuzere.be :: http://vic.demuzere.be :: PGP: 0x6690CF94 My software never contains bugs, it just develops random features. ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] HT-delayed block ack
On Tue, Jul 26, 2011 at 11:54 PM, Triangle Men triangle...@hotmail.com wrote: Greetings, Correct me if I'm wrong, but ath9k currently does not support the delayed block acknowledgement policy described in IEEE Std. 802.11-2007. Is there a register on the AR9220 which sets the immediate/delayed policy? If the 9220/9280 series does not support delayed block acks, is there another chipset which does? ath9k does not seems to support Delayed Block Ack... let me find out why Regards, Trianglemen ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] Ath9k Rate Control
On Thu, Jul 28, 2011 at 1:26 PM, Fred Matthews fre...@hotmail.co.uk wrote: Hi again, I would heavily appreciate any response to my query regarding ath9k -rate-control. a basic outline, is a packet is tried at some rate(highest rate) and the hw reports Tx Ack status and based on this PER(Packet Error is updated)... and if the PER goes high we may switch to a lower rate ... the rate probing interval is 50ms .. for aggregated frames we take care of failed subframes and calculate PER.. please go through rc.h, rc.c and xmit.c which will more idea than what i had told(or I could have said some thing incorrect) Many thanks On Tue, Jul 26, 2011 at 3:46 PM, Fred Matthews fre...@hotmail.co.uk wrote: Hi all, Can anyone advise on what rate control mechanism ath9k-rate-control is based on, as for example Atheros chipsets use Onoe, and Minstrel Rate Adaptation, from what I know is based on SampleRate. Also is there any documentation on the ath9k-rate-control algorithm, and/or can someone give a general idea of how the algorithm works. Thank you very much ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] Ath9k Rate Control
On Thu, Jul 28, 2011 at 3:04 PM, Fred Matthews fre...@hotmail.co.uk wrote: Thank you all for your responses, I am going through the code, but I just thought there might be some documentation for ath9k rate control, that would be helpful to understand the code and reasoning. please feel free to ask doubts to the list... currently I am not up-to the level of mastering ath9k rate control so that I can document it :) On Thu, Jul 28, 2011 at 9:14 AM, Mohammed Shafi shafi.wirel...@gmail.com wrote: On Thu, Jul 28, 2011 at 1:26 PM, Fred Matthews fre...@hotmail.co.uk wrote: Hi again, I would heavily appreciate any response to my query regarding ath9k -rate-control. a basic outline, is a packet is tried at some rate(highest rate) and the hw reports Tx Ack status and based on this PER(Packet Error is updated)... and if the PER goes high we may switch to a lower rate ... the rate probing interval is 50ms .. for aggregated frames we take care of failed subframes and calculate PER.. please go through rc.h, rc.c and xmit.c which will more idea than what i had told(or I could have said some thing incorrect) Many thanks On Tue, Jul 26, 2011 at 3:46 PM, Fred Matthews fre...@hotmail.co.uk wrote: Hi all, Can anyone advise on what rate control mechanism ath9k-rate-control is based on, as for example Atheros chipsets use Onoe, and Minstrel Rate Adaptation, from what I know is based on SampleRate. Also is there any documentation on the ath9k-rate-control algorithm, and/or can someone give a general idea of how the algorithm works. Thank you very much ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] which part do the real aggregation?
On Fri, Jul 22, 2011 at 9:16 PM, Y QM littlecircl...@gmail.com wrote: Hi there, These days I focused on the ath9k codes and function flows. Though I have more understanding of the functionality of ath9k. I still confused about the aggregation. I wonder which part do the real aggregation? In the ath9k_tasklet - ath_tx_tasklet or in the transmission ieee80211_tx_prepare - ieee80211_tx_prep_agg. Maybe this question is naive, but it's really tough for me. Any clue will be appreciated. the real aggregation is done in ath9k_tasklet-ath_tx_tasklet path. thanks to Vasanth. currently I also don't have a complete/much understanding of tx path... let me start seeing it now. if any one else in the list has more thoughts about this please share your thoughts .. Thanks QM ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] which part do the real aggregation?
On Tue, Jul 26, 2011 at 6:47 PM, Adrian Chadd adr...@freebsd.org wrote: The aggregation is done in the xmit.c routines in ath9k. The mac80211 stuff manages part of the node/queue/tid state. The actual dequeueing, aggregation and retransmit happens in the xmit.c routines. Adrian, thanks! I am looking into xmit.c modules HTH, Adrian On 26 July 2011 18:07, Mohammed Shafi shafi.wirel...@gmail.com wrote: On Fri, Jul 22, 2011 at 9:16 PM, Y QM littlecircl...@gmail.com wrote: Hi there, These days I focused on the ath9k codes and function flows. Though I have more understanding of the functionality of ath9k. I still confused about the aggregation. I wonder which part do the real aggregation? In the ath9k_tasklet - ath_tx_tasklet or in the transmission ieee80211_tx_prepare - ieee80211_tx_prep_agg. Maybe this question is naive, but it's really tough for me. Any clue will be appreciated. the real aggregation is done in ath9k_tasklet-ath_tx_tasklet path. thanks to Vasanth. currently I also don't have a complete/much understanding of tx path... let me start seeing it now. if any one else in the list has more thoughts about this please share your thoughts .. Thanks QM ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] which part do the real aggregation?
On Tue, Jul 26, 2011 at 7:21 PM, qingmei yao y.qing...@gmail.com wrote: On Tue, Jul 26, 2011 at 8:46 AM, qingmei yao y.qing...@gmail.com wrote: From my tracing part, the real tx path is: ip_queue_xmit - dev_queue_xmit - sch_direct_xmit - dev_hard_start_xmit - ieee80211_subif_start_xmit -ieee80211_xmit - ieee80211_tx -ieee80211_tx_prepare(may call ieee80211_tx_prep_agg)/__ieee80211_tx - ath9k_tx -ath_tx_start / (ath_tx_start_dma - ath_tx_send_normal/ampdu). However when I read the code of ieee80211_tx_skb, I found the comments : *The other path calling ieee80211_xmit is from the tasklet, * and while we can handle concurrent transmissions locking * requirements are that we do not come into tx with bhs on. Then I am confused, cause I never see some function call from the tx tasklet. Or maybe I missed something? My point now is that we really do something from the ath9k_tasklet - ath_tx_tasklet such as aggregation or update information. However how could we combine the traced tx path with this tx tasklet together? ath9k_tasklet tx interrupt comes ATH9K_INT_TX assume non-edma ath_tx_tasklet ath_processq ath_txq_schedule(this will be called only when SC_OP_TXAGGR is called) ath_tx_sched_aggr ath_tx_form_aggr ath_buf_set-_rate ... and ath_tx_complete_aggr ath_rc_status (there is a link with rate control and which will determine the length of aggregate, retries etc) ok then need to look at rc.c ath_complete_buf etc just an outline... i am not yet into the complete details, philosophy, and picture -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] which part do the real aggregation?
On Tue, Jul 26, 2011 at 7:48 PM, Mohammed Shafi shafi.wirel...@gmail.com wrote: On Tue, Jul 26, 2011 at 7:21 PM, qingmei yao y.qing...@gmail.com wrote: On Tue, Jul 26, 2011 at 8:46 AM, qingmei yao y.qing...@gmail.com wrote: From my tracing part, the real tx path is: ip_queue_xmit - dev_queue_xmit - sch_direct_xmit - dev_hard_start_xmit - ieee80211_subif_start_xmit -ieee80211_xmit - ieee80211_tx -ieee80211_tx_prepare(may call ieee80211_tx_prep_agg)/__ieee80211_tx - ath9k_tx -ath_tx_start / (ath_tx_start_dma - ath_tx_send_normal/ampdu). However when I read the code of ieee80211_tx_skb, I found the comments : *The other path calling ieee80211_xmit is from the tasklet, * and while we can handle concurrent transmissions locking * requirements are that we do not come into tx with bhs on. Then I am confused, cause I never see some function call from the tx tasklet. Or maybe I missed something? My point now is that we really do something from the ath9k_tasklet - ath_tx_tasklet such as aggregation or update information. However how could we combine the traced tx path with this tx tasklet together? ath9k_tasklet tx interrupt comes ATH9K_INT_TX assume non-edma ath_tx_tasklet ath_processq ath_txq_schedule(this will be called only when SC_OP_TXAGGR is called) ath_tx_sched_aggr ath_tx_form_aggr ath_buf_set-_rate ... and ath_tx_complete_aggr ath_rc_status (there is a link with rate control and which will determine the length of aggregate, retries etc) ok then need to look at rc.c ath_complete_buf etc just an outline... i am not yet into the complete details, philosophy, and picture also looking at what the code does specifically SC_OP_TXAGGR flag will provide some idea.. -- shafi -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] AR9380 unable to connect via hostapd - wrong essid
On Mon, Jul 25, 2011 at 7:50 PM, Lito Kriara l.kri...@sms.ed.ac.uk wrote:
Hello,
from the beginning I had no network manager procedure working, and I
double-checked now and still the same issue.
I am using the following:
Ubuntu with kernel version 2.6.38-10-generic
the latest compat-wireless (from about the end of last week).
ok are you saying that the station is not even getting connected (or)
the iwconfig thing showing some junk SSID?
I would really appreciate any help.
Thank you very much,
Lito
Quoting Adrian Chadd adr...@freebsd.org on Mon, 25 Jul 2011 09:56:02
+0800:
I occasionally get this with my older ubuntu install, on an AR2427
(AR9285 without 11n.)
So I don't think it's chipset specific.
Adrian
On 24 July 2011 21:21, Mohammed Shafi shafi.wirel...@gmail.com wrote:
On Sat, Jul 23, 2011 at 10:42 AM, Lito Kriara l.kri...@sms.ed.ac.uk
wrote:
Hello all,
I have an issue with some AR9380 cards I am using.
* My first issue is that when I try to connect to a specific network
(e.g. iwconfig wlan0 essid OpenWrt), and I then want to see what has
happened by iwconfig wlan0 I get the following result:
wlan0 IEEE 802.11abgn
ESSID:\x05\xEF\xF7\x00\xE9\xA1:\xE5\xCA\x0B\xCB\xD0HGd\xBD\x1F#\x1E\xA8\x1C{d\xC5\x14sZ\xC5^Kyc
Mode:Managed Access Point: Not-Associated Tx-Power=18 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:on
Does anyone have any idea on how could I fix that?
please disable the Network-manager if you are using iwconfig/iw to
connect to an AP.
or connect to the network using Network manager without any commands.
--
shafi
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.
--
shafi
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] AR9380 unable to connect via hostapd - wrong essid
On Sat, Jul 23, 2011 at 10:42 AM, Lito Kriara l.kri...@sms.ed.ac.uk wrote:
Hello all,
I have an issue with some AR9380 cards I am using.
* My first issue is that when I try to connect to a specific network
(e.g. iwconfig wlan0 essid OpenWrt), and I then want to see what has
happened by iwconfig wlan0 I get the following result:
wlan0 IEEE 802.11abgn
ESSID:\x05\xEF\xF7\x00\xE9\xA1:\xE5\xCA\x0B\xCB\xD0HGd\xBD\x1F#\x1E\xA8\x1C{d\xC5\x14sZ\xC5^Kyc
Mode:Managed Access Point: Not-Associated Tx-Power=18 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:on
Does anyone have any idea on how could I fix that?
please disable the Network-manager if you are using iwconfig/iw to
connect to an AP.
or connect to the network using Network manager without any commands.
--
shafi
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] [PATCH] fix a typo in ignore_reg_update in ath9k
On Sun, Jul 24, 2011 at 7:15 PM, Mihai Moldovan io...@ionic.de wrote:
Just a typo fix changing regulaotry to regulatory.
Signed-off-by: Mihai Moldovan io...@ionic.de
please send to linux-wireless
http://linuxwireless.org/en/developers/Documentation/git-guide
---
net/wireless/reg.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/net/wireless/reg.c b/net/wireless/reg.c
index 1ad0f39..d99ead3 100644
--- a/net/wireless/reg.c
+++ b/net/wireless/reg.c
@@ -903,7 +903,7 @@ static bool ignore_reg_update(struct wiphy *wiphy,
initiator != NL80211_REGDOM_SET_BY_COUNTRY_IE
!is_world_regdom(last_request-alpha2)) {
REG_DBG_PRINT(Ignoring regulatory request %s
- since the driver requires its own regulaotry
+ since the driver requires its own regulatory
domain to be set first,
reg_initiator_name(initiator));
return true;
--
1.7.6
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
--
shafi
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] [PATCH] fix a typo in ignore_reg_update in ath9k
On Sun, Jul 24, 2011 at 8:04 PM, Mihai Moldovan io...@ionic.de wrote: * On 24.07.2011 04:29 PM, Mohammed Shafi wrote: please send to linux-wireless http://linuxwireless.org/en/developers/Documentation/git-guide Oh I'm sorry, I've seen several patches posted here and figured this was the way to go. Will do. yes, you can send ath9k related RFC patches to this list for the maintainers to review it. -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] AP + IBSS in different ath9k versions
On Fri, Jul 22, 2011 at 7:14 PM, Gabriel Tolón gto...@inti.gob.ar wrote:
Thank you for your answer. I´ll put it in two different cases:
1) with the ath9k driver with comes with compat wireless 2.6.39-1:
Yes, like you said that ´s the message i get from dmesg when i try to
create the ad-hoc interface after another interface is up. However if i
first create the ad-hoc interface then i can bring up the original wlan0
and run hostapd on it. But when i try to create an IBSS with ibss join i
get device or resource bussy. I don´t know why the order of interface
creation/bringing up is important in this case.
this check might be missing there
commit 59575d1c717815d62f1b5aeac74e5e60a1b27428
Author: Rajkumar Manoharan rmanoha...@atheros.com
Date: Mon Apr 4 22:56:16 2011 +0530
ath9k: deny new interface addtion on IBSS mode
The present check denies the IBSS interface addtion if we
already have any other vifs. But it fails to deny interface
addition if IBSS was already present.
Signed-off-by: Rajkumar Manoharan rmanoha...@atheros.com
Signed-off-by: John W. Linville linvi...@tuxdriver.com
2) with older ath9k versions, for example compat wireless 2.6.32-16:
In this case i can run hostapd in wlan0 and then create and bring up an
ad-hoc interface without problems, furthermore i can join to an ibss with
iw ibss join and all works fine.
commit 4801416c76a3a355076d6d371c00270dfe332e1c
Author: Ben Greear gree...@candelatech.com
Date: Sat Jan 15 19:13:48 2011 +
ath9k: Fix up hardware mode and beacons with multiple vifs.
The main doubt i have is why the case 2) is not supported anymore, if is
something wrong about it. Thank you again.
I am not aware of the details, but I think it is because of TSF timer
handling in driver
El 22/07/2011 02:03 a.m., Mohammed Shafi escribió:
On Fri, Jul 22, 2011 at 1:15 AM, Gabriel Tolóngto...@inti.gob.ar wrote:
Hi
I´ve been using an Atheros 9285 chipset in a 2.6.32-32 kernel with ath9k
and two virtual interfaces, one in ad-hoc mode and the other in master
mode using hostapd. That configuration worked fine, with some computers
connected to the Acces Point and others to the IBSS running in the
ad-hoc interface. The only problem was that when bringing up the IBSS
(using iw) the interface using hostapd stopped sending beacons, but as
far as i understood all kept working thanks to the probe requests and
responses.
Then i upgraded the ath9k driver using compat wireless-2.6.32.16 and all
worked like before. But when i used the ath9k driver of compat
wireless-2.6.39-1 i couldn ´t bring the IBSS up when the hostapd was
running (i could bring the ad hoc interface up, but not the IBSS with
iw ibss join). I´d like to know if this configuration is not supported
or will not be supported anymore, and if it could be possible to have
the AP beaconing together with an IBSS. Thank you!
you would have got ?
[ 2841.528600] ath: Cannot create ADHOC interface when other
interfaces already exist.
because of this check in main.c
if ((ah-opmode == NL80211_IFTYPE_ADHOC) ||
((vif-type == NL80211_IFTYPE_ADHOC)
sc-nvifs 0)) {
ath_err(common, Cannot create ADHOC interface when other
interfaces already exist.\n);
ret = -EINVAL;
goto out;
}
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
--
shafi
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
