Re: [ath9k-devel] insmod ath9k error

2013-04-08 Thread bing_chou
Hi Adrian Because it is included in the branches of attitude_adjustment -Original Message- From: adrian.ch...@gmail.com [mailto:adrian.ch...@gmail.com] On Behalf Of Adrian Chadd Sent: Tuesday, April 09, 2013 1:07 PM To: bing_chou Cc: ath9k-devel@lists.ath9k.org Subject: Re: [ath9k-devel]

Re: [ath9k-devel] insmod ath9k error

2013-04-08 Thread Adrian Chadd
Ok. AR9341, so wasp. OpenWRT runs fine on that. I know, i have a big stack of wasp boards at work. Some may even run openwrt. Question though - why are you using a compat-wireless from Sep 2012? Adrian ___ ath9k-devel mailing list ath9k-devel@lists.a

Re: [ath9k-devel] insmod ath9k error

2013-04-08 Thread bing_chou
Hi Adrian Thanks for your answer Our cpu is AR9341 check out svn version is svn://svn.openwrt.org/openwrt/branches/attitude_adjustment rev: 36088 thanks -Original Message- From: adrian.ch...@gmail.com [mailto:adrian.ch...@gmail.com] On Behalf Of Adrian Chadd Sent: Tuesday, April 09,

Re: [ath9k-devel] AR9287 ; 2-wire coexistence expected behavior

2013-04-08 Thread Adrian Chadd
yes, there's GPIO MUX modes for: * RX clear (but I think this "Wlan active" pin is likely triggering on RX_CLEAR, which I think gets asserted for both TX and RX busy. I'll have to check. * TX active Check the GPIO MUX pin definitions to see. But if I understand this right, if you have the correc

Re: [ath9k-devel] insmod ath9k error

2013-04-08 Thread Adrian Chadd
Hi! You need to tell us which version of the hardware you're using. Who knows at this point. thanks, adrian On 8 April 2013 04:59, bing_chou wrote: > Hi all > > > > I got a error when insmod ath9k.ko and the “art block” is null that it will > show “data bus error” below > > root@OpenWrt:/#

Re: [ath9k-devel] AR9287 ; 2-wire coexistence expected behavior

2013-04-08 Thread sandeep suresh
Hello Mr.Adrian and Mr.Sujith, As I understand WLAN_ACTIVE is asserted whenever either WLAN_TX or WLAN_Rx is asserted. Hence the pulse trains that I am observing during BT_ACTIVE  asserted might be those corresponding to WLAN_RX. Hence is it possible to route the status of WLAN_TX and WLAN_RX

[ath9k-devel] insmod ath9k error

2013-04-08 Thread bing_chou
Hi all I got a error when insmod ath9k.ko and the “art block” is null that it will show “data bus error” below root@OpenWrt:/# insmod ath9k [ 143.20] Data bus error, epc == 83b83ed8, ra == 83b83ed8 [ 143.20] Oops[#1]: [ 143.20] Cpu 0 [ 143.20] $ 0 : 0061

Re: [ath9k-devel] master firmware version bumped to 1.4; 1.3 branched

2013-04-08 Thread Eugene Krasnikov
Ok let's start with something like this and change when feature bitmap is implemented: >From 6420a7bc940fb0d5f8c0cb3d22df5062c9cf69c9 Mon Sep 17 00:00:00 2001 From: Eugene Krasnikov Date: Thu, 4 Apr 2013 18:49:16 +0200 Subject: [PATCH] Add support opensource firmware Opensource firmware was bran

Re: [ath9k-devel] AR9287 ; 2-wire coexistence expected behavior

2013-04-08 Thread sandeep suresh
Mr.Adrian, Thanks for your mail. In FreeBSD, where can I find the 2-wire/3-wire pin definitions, weight register settings, stomping etc. For AR9287, Should I need to look at AR5416 under /sys/dev/ath/ath_hal? Regards Sandeep. From: Adrian Chadd To: sandeep

Re: [ath9k-devel] AR9287 ; 2-wire coexistence expected behavior

2013-04-08 Thread Adrian Chadd
Also, I don't know why you're writing both config values out to BTCOEX_MODE and BTCOEX_MODE2. MODE2 has a _totally_ different register layout to AR_BT_COEX_MODE. Please make sure you read the register definitions in the header file(s) before you write values out. :-) Adrian ___

Re: [ath9k-devel] AR9287 ; 2-wire coexistence expected behavior

2013-04-08 Thread Adrian Chadd
hi, I'd first double-check that you've correctly configured the btactive GPIO pin to be an input and the mux config makes it be BT_ACTIVE. I can't really help you more than this right now; I haven't sat down and actually tried this. :-( But it doesn't look like much else needs to happen besides