On Thu, Jun 09, 2011 at 08:17:59PM +0800, Adrian Chadd wrote:
> Right, and the original poster:
>
> > Today after installing compat-wireless modules with
> > still no luck as a last resort i decided to turn of BT and take out BT
> > dongles from hotspot's USB HUB.
Oh, yeah, I did miss that comple
I'd likely slide it in somewhere after ath9k_hw_process_ini() in
ath9k_hw_reset().
Good luck!
Adrian
On 9 June 2011 21:54, Liang wrote:
> Hi,
> There are three functions where AR_DIAG_SW is set with REG_SET_BIT(), but
> I'm not sure in which function I should add REG_SET_BIT(ah,
> AR_DIAG_SW,
Hi,
There are three functions where AR_DIAG_SW is set with REG_SET_BIT(), but
I'm not sure in which function I should add REG_SET_BIT(ah,
AR_DIAG_SW, AR_DIAG_ACK_DIS). Do you have any suggestions?
function1: ath9k_hw_abort_tx_dma()
REG_SET_BIT(ah, AR_DIAG_SW, AR_DIAG_FORCE_CH_IDLE_HIGH);
funct
On 9 June 2011 20:00, Bob Copeland wrote:
>> http://linuxwireless.org/en/users/Documentation/Bluetooth-coexistence
>
> From that page:
>
> Apart from AFS and channel skipping techniques Bluetooth
> coexistence is typically tested with bundled 802.11 and Bluetooth
> devices. This becomes
On Thu, Jun 09, 2011 at 10:55:11AM +0800, Adrian Chadd wrote:
> On 9 June 2011 09:01, Bob Copeland wrote:
>
> >> Hm, is there BT coexistance support for ath5k?
> >
> > No, but my understanding is that BT coex support is only for co-located
> > devices, so unless the phone is using ath5k it wouldn
Best thing to do is look at the code that disables ACK in the TX
descriptor and set that.
There's also the DIAG register, as mentioned. For ath9k:
reg.h:#define AR_DIAG_SW 0x8048
reg.h:#define AR_DIAG_ACK_DIS 0x0002
Find where AR_DIAG_SW is set in the ath9k code
Hi Adrian,
Thank you. May I ask how to set these registers to disable the ACK in the
ath5k/ath9k driver?
Best,
Leon
On Thu, Jun 9, 2011 at 2:32 PM, Adrian Chadd wrote:
> No, retry doesn't stop ack's, it just stops the hardware from retrying
> a packet if it hasn't heard an ACK.
>
> You can fid
