From: Felix Fietkau <nbd@nbd.name>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] AR9285 and Thompson TG585 v8 connection problems
Date: Mon, 31 Oct 2011 22:05:32 +0100 [thread overview]
Message-ID: <4EAF0D9C.6000806@nbd.name> (raw)
In-Reply-To: <CAJ-VmonGdGVqLx2bwUB5+C36GQTHskomC1qEQ6BC31iPPFTv9w@mail.gmail.com>
On 2011-10-31 9:24 PM, Adrian Chadd wrote:
> On 1 November 2011 00:04, Mohammed Shafi<shafi.wireless@gmail.com> wrote:
>> On Sat, Oct 29, 2011 at 9:02 PM, David Summers
>
>> i assume if we remove the antenna in chain0, the performance will be
>> bad. as per my assumption tx will always happen in chain0.(does we
>> have some tx diversity?)
>
> If you have an AR9285 with an antenna switch (and I don't have one, so
> I can't test) then you MAY be ok. But Felix and others have removed
> that TX diversity code from ath9k.
> So I'm not sure whether the antenna switch based TX diversity code
> would work. FreeBSD? It may work.
>
> But unless you're very lucky, I suggest "no" to the AR9285 + TX diversity :)
>
> (I'll see if I can source some more AR9285's, hopefully one will have
> the antenna switch hardware attached.)
As far as I know, the AR9285 chip does not have any tx diversity.
- Felix
next prev parent reply other threads:[~2011-10-31 21:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-02 16:48 [ath9k-devel] AR9285 and Thompson TG585 v8 connection problems David Summers
2011-10-09 15:42 ` David Summers
2011-10-17 20:52 ` David Summers
2011-10-17 22:42 ` Adrian Chadd
2011-10-18 21:29 ` David Summers
2011-10-27 10:35 ` David Summers
2011-10-27 11:23 ` Adrian Chadd
2011-10-29 15:32 ` David Summers
2011-10-29 17:13 ` Adrian Chadd
2011-10-31 13:04 ` Mohammed Shafi
2011-10-31 20:24 ` Adrian Chadd
2011-10-31 21:05 ` Felix Fietkau [this message]
2011-11-01 20:24 ` David Summers
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=4EAF0D9C.6000806@nbd.name \
--to=nbd@nbd.name \
--cc=ath9k-devel@lists.ath9k.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.