Hi Mohammed,
2012/3/5 Mohammed Shafi :
> Hi Matt,
>
>> echo 0x404c to which file in /sys/kernel/debug/ath9k ?
>
> root@shafi-laptop:/sys/kernel/debug/ieee80211/phy0/ath9k# echo 0x404c > regidx
> root@shafi-laptop:/sys/kernel/debug/ieee80211/phy0/ath9k# cat regval
> 0x0c45
> root@shafi-laptop:/
Hi Matt,
> yes, those are working to me now, but see the file "regval", it is
> allowed to be written. I tried to echo a value to it, and cat it, it
> seems not work right to me. :(
>
> You may try to echo "0x0c45" > regval when the regval is
> "0x0c55". Then cat regval again, see if it ch
On Wed, Mar 7, 2012 at 3:11 PM, Mohammed Shafi wrote:
> Hi Matt,
>
>> yes, those are working to me now, but see the file "regval", it is
>> allowed to be written. I tried to echo a value to it, and cat it, it
>> seems not work right to me. :(
>>
>> You may try to echo "0x0c45" > regval when th
Dears,
I wonder how to get Atheros AR9280 reference design so that I can
contribute to the development of ath9k driver.
Regards,
Abdel-Latif
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/a
Hi,
those are confidential and proprietary of the company. i think those
will be provided to people who to developers/contractors/interns who
should have signed NDA.
anyway ath9k is lot lot more than open compared to all other drivers.
you can understand lots of HAL code with logic alone. debuggin
On 2012-02-29 10:35 PM, Kim Lidström wrote:
> Hello!
> A while ago I had a situation where my AR9485 would lock up the kernel
> so bad and two very nice guys(Mohammed Shafi and Adrian.. Uhm.. Sorry I
> forgot his last name) were very patient in helping me and trying to
> debug it through patches, e
On Wed, 07 Mar 2012 18:29:56 +0100, Felix Fietkau wrote:
> On 2012-02-29 10:35 PM, Kim Lidström wrote:
>> Hello!
>> A while ago I had a situation where my AR9485 would lock up the
>> kernel
>> so bad and two very nice guys(Mohammed Shafi and Adrian.. Uhm..
>> Sorry I
>> forgot his last name) wer
On 2012-03-07 7:37 PM, Paul Farrow wrote:
>
> On Wed, 07 Mar 2012 18:29:56 +0100, Felix Fietkau wrote:
>> On 2012-02-29 10:35 PM, Kim Lidström wrote:
>>> Hello!
>>> A while ago I had a situation where my AR9485 would lock up the
>>> kernel
>>> so bad and two very nice guys(Mohammed Shafi and Adri
On Wed, 07 Mar 2012 20:42:35 +0100, Felix Fietkau wrote:
> On 2012-03-07 7:37 PM, Paul Farrow wrote:
>>
>> On Wed, 07 Mar 2012 18:29:56 +0100, Felix Fietkau wrote:
>>> On 2012-02-29 10:35 PM, Kim Lidström wrote:
Hello!
A while ago I had a situation where my AR9485 would lock up the
I put two ath9k (AR9300) nics in one machine, with
6 antenna poking out, and had one NIC be the AP
for the other.
It works, but I'm seeing lots of CRC errors and station-to-station throughput
is only about 5Mbps (one sending to the other).
I tried setting xmit power lower (to 4, for instance), bu
Hi Felix
I would like to try your patch to see if it stops my Tx DMA errors on
my AR9280 chipset pcie card.
1. Do you think it might work?
2. What is the best way to apply this patch?
Please be gentle with me as I am linux hobbyist and I am keen to get my
Tx DMA error problem sorted.
Thanks
hi,
I am trying the following experiment:
1. I am downloading file from my laptop through a file (say ubuntu ISO) and
the AP is secure.
2. From two other machines, atheros card(AR922X) is used with ath9k driver
on each. This card has one of its interfaces in adhoc mode, The other
interface is in mo
From: Ben Greear
On systems with multiple NICs, it's nice to know which
one is producing warnings. Here is an example of the
new ouput:
ath: wiphy0: Failed to stop TX DMA, queues=0x005!
Signed-off-by: Ben Greear
---
:100644 100644 efc0111... 54f255d... M drivers/net/wireless/ath/ath.h
:10064
On 03/07/2012 01:17 PM, Ben Greear wrote:
> I put two ath9k (AR9300) nics in one machine, with
> 6 antenna poking out, and had one NIC be the AP
> for the other.
I was using TCP before on 3.3.0-rc5+...
I upgraded to 3.3.0-rc6+, and saw around 10Mbps performance.
I tried 3.0.23 and saw around 19Mbp
On 7 March 2012 13:17, Ben Greear wrote:
> I put two ath9k (AR9300) nics in one machine, with
> 6 antenna poking out, and had one NIC be the AP
> for the other.
How far apart are there?
> It works, but I'm seeing lots of CRC errors and station-to-station throughput
> is only about 5Mbps (one sen
On 03/07/2012 05:00 PM, Adrian Chadd wrote:
> On 7 March 2012 13:17, Ben Greear wrote:
>> I put two ath9k (AR9300) nics in one machine, with
>> 6 antenna poking out, and had one NIC be the AP
>> for the other.
>
> How far apart are there?
Well, here's a picture:
http://www.candelatech.com/images
On Wed, 2012-03-07 at 16:05 -0800, gree...@candelatech.com wrote:
> From: Ben Greear
>
> On systems with multiple NICs, it's nice to know which
> one is producing warnings. Here is an example of the
> new ouput:
>
> ath: wiphy0: Failed to stop TX DMA, queues=0x005!
Makes some sense.
> diff --
Dear Mohammed,
Thanks for your response. Can I modify Ath9k to do some modifications on
the protocol, f.e., I want to change the channel access to be time based
(TDMA) to allow for multiple Access Points to cooperate?
Regards,
Abdel-Latif
-Original Message-
From: Mohammed Shafi [mailto
18 matches
Mail list logo
