From: Oleksij Rempel <linux@rempel-privat.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Standardisation - adding 2 bit STBC and Ness to MCS
Date: Wed, 01 May 2013 16:34:21 +0200 [thread overview]
Message-ID: <518127ED.9060900@rempel-privat.de> (raw)
Hallo all,
> http://www.radiotap.org/suggested-fields/MCS%20extension%20for%20STBC%20and%20Ness
>
> I have posted 3 patches on the proposal page (see Attachments):
>
> 1. A patch that applies to the Linux kernel v3.7-rc1 to collect the new
> STBC and Ness parameters from a wireless driver, and add them into the
> MCS radiotap field.
> 2. A patch to the Intel wireless driver in the kernel to collect STBC
> and Ness information.
> 3. A patch to wireshark to display STBC and Ness information.
>
> With this I believe we have everything needed to start the 3 week
> comment period.
There is a bit more then 3 week now. I would like to have this approved :)
Are there any thing needed to finish this?
Beside, i have one question about how STBC work. According to differnet
docs, i assume that:
- STBC is done by sending, at least, two stream with same data in
different order.
- It means for me, that real use of STBC can be made only on MIMO hardware.
- If 1x1 receiver indicates that it got STBC encoded frame, it dos not
meant, it would be able to use redundant data from second stream.
- There are fallowing STBC schemes: Alamouti?s
STBC for 2 transmit antennas and orthogonal STBC for 3 and 4 transmit
antennas.
According to this information, what do we call 1,2 or 3 stream STBC?
Since STBC should have minimal 2 stream, but in same time we have 1x1
and 2x2 hardware which able to receive and decode STBC stream i assume:
- RX-STBC1 is for compatibility only. No data redundancy.
- RX-STBC12 - can be used Alamouti?s schema with 2 streams. Mostly used
method.
- RX-STBC123 - is orthogonal schema and not widely used method. Since
last method use wide spectrum to transmit data comparable to SISO
stream, it makes almost no sense. But 3-stream method get optimal error
corect in compare with 2 and 4 strea schemas.
Do this assumptions correct?
PS: My assumptions based on "MIMO Space-Time Block Coding (STBC):
Simulations and Results"
--
Regards,
Oleksij
WARNING: multiple messages have this Message-ID (diff)
From: Oleksij Rempel <linux@rempel-privat.de>
To: radiotap@NetBSD.org, simon@superduper.net,
johannes@sipsolutions.net, Adrian Chadd <adrian@freebsd.org>
Cc: "ath9k-devel@lists.ath9k.org" <ath9k-devel@lists.ath9k.org>,
linux-wireless@vger.kernel.org
Subject: Re: Standardisation - adding 2 bit STBC and Ness to MCS
Date: Wed, 01 May 2013 16:34:21 +0200 [thread overview]
Message-ID: <518127ED.9060900@rempel-privat.de> (raw)
Hallo all,
> http://www.radiotap.org/suggested-fields/MCS%20extension%20for%20STBC%20and%20Ness
>
> I have posted 3 patches on the proposal page (see Attachments):
>
> 1. A patch that applies to the Linux kernel v3.7-rc1 to collect the new
> STBC and Ness parameters from a wireless driver, and add them into the
> MCS radiotap field.
> 2. A patch to the Intel wireless driver in the kernel to collect STBC
> and Ness information.
> 3. A patch to wireshark to display STBC and Ness information.
>
> With this I believe we have everything needed to start the 3 week
> comment period.
There is a bit more then 3 week now. I would like to have this approved :)
Are there any thing needed to finish this?
Beside, i have one question about how STBC work. According to differnet
docs, i assume that:
- STBC is done by sending, at least, two stream with same data in
different order.
- It means for me, that real use of STBC can be made only on MIMO hardware.
- If 1x1 receiver indicates that it got STBC encoded frame, it dos not
meant, it would be able to use redundant data from second stream.
- There are fallowing STBC schemes: Alamouti’s
STBC for 2 transmit antennas and orthogonal STBC for 3 and 4 transmit
antennas.
According to this information, what do we call 1,2 or 3 stream STBC?
Since STBC should have minimal 2 stream, but in same time we have 1x1
and 2x2 hardware which able to receive and decode STBC stream i assume:
- RX-STBC1 is for compatibility only. No data redundancy.
- RX-STBC12 - can be used Alamouti’s schema with 2 streams. Mostly used
method.
- RX-STBC123 - is orthogonal schema and not widely used method. Since
last method use wide spectrum to transmit data comparable to SISO
stream, it makes almost no sense. But 3-stream method get optimal error
corect in compare with 2 and 4 strea schemas.
Do this assumptions correct?
PS: My assumptions based on "MIMO Space-Time Block Coding (STBC):
Simulations and Results"
--
Regards,
Oleksij
next reply other threads:[~2013-05-01 14:34 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 14:34 Oleksij Rempel [this message]
2013-05-01 14:34 ` Standardisation - adding 2 bit STBC and Ness to MCS Oleksij Rempel
[not found] ` <518127ED.9060900-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org>
2013-05-02 20:44 ` Johannes Berg
2013-05-02 20:44 ` [ath9k-devel] " Johannes Berg
2013-05-02 20:44 ` Johannes Berg
[not found] ` <1367527479.11375.19.camel-8Nb76shvtaUJvtFkdXX2HixXY32XiHfO@public.gmane.org>
2013-05-03 19:53 ` Patches for STBC Standartisation Oleksij Rempel
2013-05-07 7:40 ` Standardisation - adding 2 bit STBC and Ness to MCS Oleksij Rempel
2013-05-03 19:53 ` [ath9k-devel] Patches for STBC Standartisation Oleksij Rempel
2013-05-03 19:53 ` Oleksij Rempel
2013-05-03 19:53 ` [ath9k-devel] [PATCH 1/3] mac80211: add STBC flag for radiotap Oleksij Rempel
2013-05-03 19:53 ` Oleksij Rempel
[not found] ` <1367610836-3303-1-git-send-email-linux-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org>
2013-05-03 19:53 ` Oleksij Rempel
2013-05-03 19:53 ` [PATCH 2/3] ath9k: remove useless flag conversation Oleksij Rempel
2013-05-03 19:53 ` [PATCH 3/3] ath9k: check for Rx-STBC flag and pass it to ieee80211 Oleksij Rempel
2013-05-03 19:53 ` [PATCH] tcpdump: add STBC Rx support Oleksij Rempel
2013-05-03 19:53 ` [ath9k-devel] [PATCH 2/3] ath9k: remove useless flag conversation Oleksij Rempel
2013-05-03 19:53 ` Oleksij Rempel
2013-05-03 19:53 ` [ath9k-devel] [PATCH 3/3] ath9k: check for Rx-STBC flag and pass it to ieee80211 Oleksij Rempel
2013-05-03 19:53 ` Oleksij Rempel
2013-05-03 19:53 ` [ath9k-devel] [PATCH] tcpdump: add STBC Rx support Oleksij Rempel
2013-05-03 19:53 ` Oleksij Rempel
2013-05-03 19:58 ` [ath9k-devel] " Guy Harris
2013-05-03 19:58 ` Guy Harris
2013-05-03 19:58 ` Guy Harris
2013-05-03 20:04 ` [ath9k-devel] " Oleksij Rempel
2013-05-03 20:04 ` Oleksij Rempel
[not found] ` <15EBD372-C4E3-4DA3-9ED9-47B238654587-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>
2013-05-03 20:04 ` Oleksij Rempel
2013-05-04 6:22 ` [ath9k-devel] Patch for radiotap library Oleksij Rempel
2013-05-04 6:22 ` Oleksij Rempel
2013-05-04 6:22 ` Oleksij Rempel
2013-05-07 7:40 ` [ath9k-devel] Standardisation - adding 2 bit STBC and Ness to MCS Oleksij Rempel
2013-05-07 7:40 ` Oleksij Rempel
2013-05-07 13:54 ` [ath9k-devel] " Johannes Berg
2013-05-07 13:54 ` Johannes Berg
[not found] ` <1367934867.8328.31.camel-8Nb76shvtaUJvtFkdXX2HixXY32XiHfO@public.gmane.org>
2013-05-07 13:55 ` Johannes Berg
2013-05-07 13:55 ` [ath9k-devel] " Johannes Berg
2013-05-07 13:55 ` Johannes Berg
2013-05-07 14:25 ` [ath9k-devel] " Oleksij Rempel
2013-05-07 14:25 ` Oleksij Rempel
2013-05-07 14:25 ` Oleksij Rempel
2013-05-07 14:59 ` Jonathan Bither
2013-05-07 15:03 ` Oleksij Rempel
[not found] ` <518917C4.9090607-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org>
2013-05-07 16:09 ` Jonathan Bither
2013-05-07 16:09 ` Jonathan Bither
[not found] ` <518916D1.4070902-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-05-07 15:03 ` Oleksij Rempel
[not found] ` <5188AFFE.6070804-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org>
2013-05-07 13:54 ` Johannes Berg
2013-05-03 21:12 ` [ath9k-devel] " Simon Barber
2013-05-03 21:12 ` Simon Barber
2013-05-03 21:12 ` Simon Barber
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=518127ED.9060900@rempel-privat.de \
--to=linux@rempel-privat.de \
--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.