linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felix Fietkau <nbd@openwrt.org>
To: Oleksij Rempel <linux@rempel-privat.de>
Cc: Adrian Chadd <adrian@freebsd.org>,
	ath9k-devel@lists.ath9k.org, linux-wireless@vger.kernel.org
Subject: Re: [ath9k-devel] [PATCH 1/2] ath9k_htc: add STBC TX support
Date: Thu, 02 May 2013 20:01:00 +0200	[thread overview]
Message-ID: <5182A9DC.6030203@openwrt.org> (raw)
In-Reply-To: <5182A341.8050704@rempel-privat.de>

On 2013-05-02 7:32 PM, Oleksij Rempel wrote:
> Am 02.05.2013 18:55, schrieb Adrian Chadd:
>> On 2 May 2013 01:11, Oleksij Rempel <linux@rempel-privat.de> wrote:
>>
>>> +#define WLAN_RC_TX_STBC_FLAG 0x20 /* TX STBC */
>>> +#define WLAN_RC_RX_STBC_FLAG 0xC0 /* RX STBC ,2 bits */
>>
>> I thought we covered this; why are you marking two bits here?
> 
> becouse firmware checks for two bits (and then use it as bool ;)), so i 
> pass what firmware can handle.
> 
>> Atheros 11n hardware only supports 1-stream STBC RX.
> 
> Did you got my email with lots of assumptions and questions?
> What do you mean by 1-stream STBC RX? After i did some home work on STBC 
> i see that it encoded from at least two spatial streams.
> Is
> 1-stream STBC RX = 2 spatial streams with mirrored data?
> and
> 2-stream STBC RX = 4 spatial streams with mirrored data?
> 
> or
> 
> 1-stream STBC RX = compatibility mode for one stream hardware(so only of 
> two streams received)?
When you're talking about 'streams', please specify where you're talking
about Spatial Streams (Nss, defined by the MCS), or Space-Time Streams
(Nsts). STBC is useful whenever the number of possible Space-Time
streams exceeds the number of Spatial streams, i.e. if the number of tx
chains is bigger than the number of spatial streams.
There's an asymmetry between Rx and Tx here. If a receiver has 1 chain
and the transmitter has 2 chains, tx can use 2 Space-Time streams to
encode 1 Spatial stream to improve the reliability of the signal.
The HT STBC capability field indicates the maximum number of Spatial
Streams, not Space-Time streams. Atheros hardware only supports STBC
with Nss = 1, so announcing 2-stream STBC is definitely wrong.

> That would make sense for 1x1:1 hardware, but if you say all atheros N 
> hardware support only 1-stream STBC RX, will mean that STBC is useless 
> on this hardware.
Only STBC With Nss=1, Nsts=2 is supported, but this does not make it
useless at all. It helps, even if the receiver only has one antenna.

- Felix

  reply	other threads:[~2013-05-02 18:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-02  8:11 [PATCH 0/2] work sync Oleksij Rempel
2013-05-02  8:11 ` [PATCH 1/2] ath9k_htc: add STBC TX support Oleksij Rempel
2013-05-02 16:55   ` Adrian Chadd
2013-05-02 17:32     ` Oleksij Rempel
2013-05-02 18:01       ` Felix Fietkau [this message]
2013-05-02 20:15         ` [ath9k-devel] " Adrian Chadd
2013-05-04  6:50           ` Oleksij Rempel
2013-05-04  6:55             ` Oleksij Rempel
2013-05-04 10:02             ` Felix Fietkau
2013-05-04 11:08               ` Oleksij Rempel
2013-05-04 11:16                 ` Felix Fietkau
2013-05-04 11:28                   ` Oleksij Rempel
2013-05-04 14:49                   ` Adrian Chadd
2013-05-04 17:50                   ` Adrian Chadd
2013-05-04 18:29                     ` Oleksij Rempel
2013-05-04  7:33           ` [PATCH v2] " Oleksij Rempel
2013-05-04 10:59           ` [PATCH] " Oleksij Rempel
2013-05-04 11:32           ` [PATCH v4] " Oleksij Rempel
2013-05-02 20:32         ` [ath9k-devel] [PATCH 1/2] " Oleksij Rempel
2013-05-02  8:11 ` [PATCH 2/2] ath9k: remove useless flag conversation Oleksij Rempel

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=5182A9DC.6030203@openwrt.org \
    --to=nbd@openwrt.org \
    --cc=adrian@freebsd.org \
    --cc=ath9k-devel@lists.ath9k.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linux@rempel-privat.de \
    /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).