On Wed, Aug 10, 2011 at 3:07 PM, Daniel Golle dgo...@allnet.de wrote:
Hi!
I'm currently playing with an AR9385 mini-PCIe module. From what I see
in the code, support for 3T3R chips seems not ready yet.
I added the device-id and ath9k loads fine, identifies the card as
AR9300 Rev.3 and
On Tue, Mar 29, 2011 at 3:25 PM, Y QM littlecircl...@gmail.com wrote:
Hello everyone,
I am a newbie in ath9k. I wonder if someone can help me to get a clear frame
transmission function flow in ath9k? Or if there are some documents can help
me get a clear concept of function flows in ath9k
On Mon, Mar 21, 2011 at 3:57 PM, Kucherenko Valeriy darkside...@ukr.net wrote:
I have a TP-Link TL-WN951N wireless PCI device (AR5008) and trying to make it
work in 802.11n mode with HT and MIMO. According to specifications (
-WN821N
both on Windows7. The results are the same.
--- Исходное сообщение ---
От кого: Brian Prodoehl bprodo...@gmail.com
Кому: Kucherenko Valeriy darkside...@ukr.net
Дата: 21 марта 2011, 23:13:44
Тема: Re: [ath9k-devel] AR5008 and RX/TX STBC
On Mon, Mar 21, 2011 at 3:57 PM
On Wed, Mar 2, 2011 at 7:38 PM, Luis R. Rodriguez mcg...@gmail.com wrote:
On Wed, Mar 2, 2011 at 4:27 PM, crocket crockabisc...@gmail.com wrote:
What about
https://lists.ath9k.org/pipermail/ath9k-devel/2011-February/005157.html
This is a FreeBSD issue, not Linux issue, see: The problem is
On Fri, Feb 25, 2011 at 4:02 AM, Thomas Andrews tandr...@grok.co.za wrote:
Hi,
Is DELAYED-BA implemented?
I get this error when I try to use it:
Driver does not support configured HT capability [DELAYED-BA]
I have the following versions installed:
Linux atom 2.6.35-22-generic-pae
On Wed, Feb 16, 2011 at 9:47 AM, Baldomero Coll baldo.at...@gmail.com wrote:
I'm not sure, but I've read somewhere that by default the two antennas are
used.
It is true that I'm not interested in selecting the number of antennas, what
I really want is that the MIMO capability is exploited if
On Tue, Jan 18, 2011 at 7:34 PM, Nikolay Martynov mar.ko...@gmail.com wrote:
Hi.
I have TRENDnet TEW-632BRP running trunk of openwrt.
When it boots I see in dmesg:
ath: DMA failed to stop in 10 ms AR_CR=0x0024 AR_DIAG_SW=0x4220
ath: Could not stop RX, we could be confusing the DMA
2011/1/18 JD jd1...@gmail.com:
On 01/18/2011 11:23 AM, Rafał Miłecki wrote:
2011/1/18 JDjd1...@gmail.com:
TP-Link TL-WN861N
see
http://www.tp-link.com/products/productDetails.asp?class=content=spepmodel=TL-WN861N
https://forum.openwrt.org/viewtopic.php?id=25431
On Wed, Jan 12, 2011 at 12:04 PM, JD jd1...@gmail.com wrote:
How can I extract the manufacturer's device ID from the mini-pci wifi card?
Or could someone at least point me to a working windws XP(32)
driver, since the Linux ath9k (Kernel 2.6.37) driver is unable to work with
this card.
On
This patch adds error vector magnitude collection to AR9001 and
AR9002, as well as my best attempt at making sense of what the EVM
numbers actually mean. There was an obvious problem with the
AR_RxEVMn macros (parts of status4 were being used for rssi, and all
of status4 was also being used for
On Jan 9, 2011 10:20 AM, Felix Fietkau n...@openwrt.org wrote:
On 2011-01-09 1:07 AM, Brian Prodoehl wrote:
This patch adds error vector magnitude collection to AR9001 and
AR9002, as well as my best attempt at making sense of what the EVM
numbers actually mean. There was an obvious problem
What's the story on reading a register in ath9k and getting
0xDEADBEEF? I know this has come up before, and whatever the symptom
is sort of goes away and everyone moves on, but I haven't seen a
discussion of why deadbeef comes up in the first place. A couple
weeks ago I had a calibration fail on
On Fri, Jan 7, 2011 at 11:50 AM, Galen gal...@zinkconsulting.com wrote:
On Jan 6, 2011, at 1:21 PM, Luis R. Rodriguez wrote:
On Thu, Jan 6, 2011 at 10:29 AM, Galen gal...@zinkconsulting.com wrote:
Last I checked, RIFS support was not implemented in ath9k. Is the lack of
support due to
On Fri, Jan 7, 2011 at 12:24 PM, Ben Greear gree...@candelatech.com wrote:
On 01/07/2011 08:55 AM, Senthilkumar Balasubramanian wrote:
On Fri, Jan 7, 2011 at 10:04 PM, Brian Prodoehlbprodo...@gmail.com
wrote:
What's the story on reading a register in ath9k and getting
0xDEADBEEF? I know
On Fri, Jan 7, 2011 at 12:23 PM, Galen gal...@zinkconsulting.com wrote:
At the moment, it seems that ath9k + mac80211 only supports channels 36-64;
100-140; 149-165. Obviously, available channels (and on what basis) are
determined based on various regulatory settings in your particular
On Fri, Jan 7, 2011 at 4:55 PM, Peter Stuge pe...@stuge.se wrote:
First of all, sorry for dropping linux-wireless from my previous
message, it was mostly about my understanding of ath9k processes.
Crossposting is a bit unnatural for me, I usually strictly use
list-reply. Let's try with this
On Wed, Dec 29, 2010 at 1:10 AM, Robert Chan robert.chan.l...@gmail.com wrote:
Dear all,
After some research done on ath9k's support of HT on Adhoc mode, I found on
the mac80211 driver page (http://wireless.kernel.org/en/users/Drivers) that
ath9k seems to support IBSS *and/or* mesh *and/or*
On Sun, Nov 21, 2010 at 7:21 PM, Brian Prodoehl bprodo...@gmail.com wrote:
I'm trying to poke the AR_PHY_SPECTRAL_SCAN register to see what it
does. What is its purpose? Has anyone used this spectral scan
feature?
-Brian
It appears that Mikrotik and Cisco both have software utilizing
On Tue, Dec 14, 2010 at 8:16 PM, Tao Jin jintao@gmail.com wrote:
Dear all,
I read the ath9k_htc driver, which seems not to have quite complete
feature as ath9k and ath5k. For example, the rate control is handled
in firmware/hardware, and no per packet tx status report, etc.
However, such
On Wed, Dec 8, 2010 at 3:26 AM, Adrian Chadd adr...@freebsd.org wrote:
On 8 December 2010 03:10, Blaise Gassend bla...@willowgarage.com wrote:
Turns out that this bug was fixed a couple of days ago by this patch
(but it still exists in eeprom_9287.c and ar9003_eeprom.c):
On Tue, Dec 7, 2010 at 2:47 AM, Blaise Gassend bla...@willowgarage.com wrote:
Which chipset are you using? On which cards? With the AR9280/AR9220,
I see the output power is pretty close to what is being set through iw
(measured with a spectrum analyzer). I've been selecting output
levels
On Mon, Dec 6, 2010 at 8:05 PM, Blaise Gassend bla...@willowgarage.com wrote:
I have made a bit of progress on my problems with setting txpower in
master mode on ath9k. It turns out that setting txpower does work, but
that the settings that get sent to the adapter for a given requested
txpower
it is -67dBm). Maybe
getting those readings correct is as simple as using the noise floor
determined by the do_getnf priv op.
Brian Prodoehl
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
24 matches
Mail list logo
