2012/7/31 Mohammed Shafi :
> On Sun, Jul 29, 2012 at 4:21 PM, Frederic Crozat wrote:
>> Hi all,
>>
>> while upgrading my openSUSE 12.1 to 12.2RC2, I've noted a (big)
>> regression for my PCI-express wifi card (TP-Link WDN4800), which uses
>> a AR9300 (168c:0030) chipset.
>>
>> With openSUSE 12.2 R
Hi,
I have some problems with the ath9k driver.
Some Wifi-frames don't aperar in the ath9k_tasklet() function.
Within this function I logged all apearing frames using printk(). I accessed
the Wifi-framecontet by reading "skb->data".
I monitored on an other computer Wifi traffic using wireshark a
On Tue, Jul 31, 2012 at 9:01 PM, Yevgeniy Melnichuk
wrote:
> hi Mohammed,
>
> CONFIG_ATH9K_BTCOEX_SUPPORT is set to Y and it looks like btcoex_enable is
> enabled by default, because wlan+bt work together without me changing any
> module-parameters.
no . i think you got to do sudo modprobe -v ath
hi Mohammed,
CONFIG_ATH9K_BTCOEX_SUPPORT is set to Y and it looks like btcoex_enable is
enabled by default, because wlan+bt work together without me changing any
module-parameters.
Yevgeniy
2012/7/31 Mohammed Shafi
> Hi,
>
> ensure if you are using WLAN + BT, make sure you enable BTCOEX in
>
Hi,
ensure if you are using WLAN + BT, make sure you enable BTCOEX in
.config and as a module param
http://linuxwireless.org/en/users/Drivers/ath9k/btcoex
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/a
Hi,
On Tue, Jul 31, 2012 at 8:00 PM, Yevgeniy Melnichuk
wrote:
> Hi Mohammed,
>
> i made a mistake while patching ath3k.c, but now i got it working.
> Thx for your help. Patch is attached.
awesome! just now figured out for 3012 devices we have to add VID/PID
some thing like this
http://lkml.ind
Hi Mohammed,
i made a mistake while patching ath3k.c, but now i got it working.
Thx for your help. Patch is attached.
Yevgeniy
2012/7/30 Yevgeniy Melnichuk
> Hi Mohammed,
>
> thx again for the answer.
> My mistake was to think AR9485 is responsible for wireless and bluetooth.
>
> i followed th
To whom it may concern,
I was wondering if anyone can help me with this issue. With the current
ath9k driver when I capture packets in MAC level(Radio header section) the
MAC Timestamp will be placed at the end of MPDU that means if for example
you make a "ping 192.168.1.1" or "ping -s 1500 192.16
