From: Christian Lamparter <chunkeey@googlemail.com>
To: Adrian Chadd <adrian@freebsd.org>
Cc: Zefir Kurtisi <zefir.kurtisi@neratec.com>,
"Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>,
linux-wireless@vger.kernel.org, ath9k-devel@lists.ath9k.org,
kgiori@qca.qualcomm.com, nbd@openwrt.org
Subject: Re: [RFC 5/6] ath9k: enable DFS pulse detection
Date: Tue, 4 Oct 2011 19:49:35 +0200 [thread overview]
Message-ID: <201110041949.35321.chunkeey@googlemail.com> (raw)
In-Reply-To: <CAJ-Vmo=1riCHbC56_UR+EXUrB6T_=_FjTdNKFm6-XuSq2UOTzg@mail.gmail.com>
On Tuesday, October 04, 2011 07:03:10 PM Adrian Chadd wrote:
> Nope, what I'm saying is that someone's likely just copy/paste'd the
> "we support x and y!" from some marketing material and then suggested
> people use linux/openwrt/ath9k without really looking at it.
I'm still curious how they got the Apple access point through the FCC
testing back then. Well, I guess we'll never know for sure.
> There were plenty of people advertising the AR9160 as a "3x3 MIMO"
> when it's a 2x2 stream device with 3 antennas. I know this confused me
> when I started tinkering with wifi stuff.
AFAIK the 3x3 really just stands for the amount of tx X rx chains [and
not antennas]. So if the hardware has 3 tx and rx chains it can be sold
as a "3x3" device even if does not support 3 streams.
> Anyway, we're getting off-track here.
we can stop anytime.
next prev parent reply other threads:[~2011-10-04 17:49 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 10:29 [RFC 0/6] ath9k: DFS pattern detection Zefir Kurtisi
2011-10-03 10:29 ` [RFC 1/6] ath9k: add DFS statistics to debugfs Zefir Kurtisi
2011-10-03 18:14 ` Luis R. Rodriguez
2011-10-04 8:27 ` Zefir Kurtisi
2011-10-03 10:29 ` [RFC 2/6] ath9k: add DFS debug flag Zefir Kurtisi
2011-10-03 18:15 ` Luis R. Rodriguez
2011-10-04 8:31 ` Zefir Kurtisi
2011-10-04 9:40 ` Mohammed Shafi
2011-10-03 10:29 ` [RFC 3/6] ath9k: initial radar pulse detection for DFS Zefir Kurtisi
2011-10-03 11:57 ` Adrian Chadd
2011-10-03 12:23 ` Zefir Kurtisi
2011-10-03 12:43 ` Adrian Chadd
2011-10-03 14:21 ` Zefir Kurtisi
2011-10-03 14:23 ` Adrian Chadd
2011-10-03 10:29 ` [RFC 4/6] ath9k: add DFS build parameter Zefir Kurtisi
2011-10-03 18:26 ` Luis R. Rodriguez
2011-10-04 9:55 ` Zefir Kurtisi
2011-10-04 10:37 ` Felix Fietkau
2011-10-04 12:25 ` Adrian Chadd
2011-10-05 22:20 ` Luis R. Rodriguez
2011-10-03 10:29 ` [RFC 5/6] ath9k: enable DFS pulse detection Zefir Kurtisi
2011-10-03 18:27 ` Luis R. Rodriguez
2011-10-03 19:24 ` Christian Lamparter
2011-10-03 19:31 ` Luis R. Rodriguez
2011-10-04 13:38 ` Christian Lamparter
2011-10-04 14:17 ` Zefir Kurtisi
2011-10-04 14:34 ` Adrian Chadd
2011-10-05 22:31 ` Luis R. Rodriguez
2011-10-04 14:42 ` Christian Lamparter
2011-10-04 14:50 ` Adrian Chadd
2011-10-04 15:26 ` Christian Lamparter
2011-10-04 15:57 ` Adrian Chadd
2011-10-04 16:42 ` Christian Lamparter
2011-10-04 17:03 ` Adrian Chadd
2011-10-04 17:49 ` Christian Lamparter [this message]
2011-10-05 22:37 ` Luis R. Rodriguez
2011-10-04 16:26 ` Zefir Kurtisi
2011-10-05 22:30 ` Luis R. Rodriguez
2011-10-05 22:27 ` [ath9k-devel] " Luis R. Rodriguez
2011-10-06 16:49 ` Christian Lamparter
2011-10-06 18:36 ` Luis R. Rodriguez
2011-10-06 18:41 ` Luis R. Rodriguez
2011-10-06 20:32 ` Zefir Kurtisi
2011-10-06 20:41 ` Luis R. Rodriguez
2011-10-06 21:08 ` Zefir Kurtisi
2011-10-06 21:12 ` Luis R. Rodriguez
2011-10-07 3:06 ` Adrian Chadd
2011-10-07 7:54 ` Luis R. Rodriguez
2011-10-07 8:48 ` Zefir Kurtisi
2011-10-07 11:43 ` Adrian Chadd
2011-10-04 10:11 ` Zefir Kurtisi
2011-10-05 22:23 ` Luis R. Rodriguez
2011-10-03 10:29 ` [RFC 6/6] ath9k: handle pulse data reported by DFS HW Zefir Kurtisi
2011-10-03 18:30 ` Luis R. Rodriguez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201110041949.35321.chunkeey@googlemail.com \
--to=chunkeey@googlemail.com \
--cc=adrian@freebsd.org \
--cc=ath9k-devel@lists.ath9k.org \
--cc=kgiori@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@openwrt.org \
--cc=rodrigue@qca.qualcomm.com \
--cc=zefir.kurtisi@neratec.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).