From: Oleksij Rempel <linux-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org>
To: radiotap-qavaossjCcEdnm+yROfE0A@public.gmane.org,
simon-vp0mx6+5gkqFX2APIN6yfw@public.gmane.org,
johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org,
Adrian Chadd <adrian-h+KGxgPPiopAfugRpC6u6w@public.gmane.org>
Cc: "ath9k-devel-xDcbHBWguxHbcTqmT+pZeQ@public.gmane.org"
<ath9k-devel-xDcbHBWguxHbcTqmT+pZeQ@public.gmane.org>,
linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.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__40512.8046324991$1367418879$gmane$org@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: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 14:34 Oleksij Rempel [this message]
[not found] <518127ED.9060900@rempel-privat.de>
[not found] ` <518127ED.9060900-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org>
2013-05-02 20:44 ` Standardisation - adding 2 bit STBC and Ness to MCS Johannes Berg
2013-05-03 21:12 ` Simon Barber
[not found] ` <1367527479.11375.19.camel@jlt4.sipsolutions.net>
[not found] ` <1367527479.11375.19.camel-8Nb76shvtaUJvtFkdXX2HixXY32XiHfO@public.gmane.org>
2013-05-07 7:40 ` Oleksij Rempel
[not found] ` <5188AFFE.6070804@rempel-privat.de>
[not found] ` <5188AFFE.6070804-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org>
2013-05-07 13:54 ` Johannes Berg
[not found] ` <1367934867.8328.31.camel@jlt4.sipsolutions.net>
[not found] ` <1367934867.8328.31.camel-8Nb76shvtaUJvtFkdXX2HixXY32XiHfO@public.gmane.org>
2013-05-07 13:55 ` Johannes Berg
[not found] ` <1367934904.8328.32.camel@jlt4.sipsolutions.net>
[not found] ` <1367934904.8328.32.camel-8Nb76shvtaUJvtFkdXX2HixXY32XiHfO@public.gmane.org>
2013-05-07 14:25 ` Oleksij Rempel
[not found] ` <518916D1.4070902@gmail.com>
[not found] ` <518916D1.4070902-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-05-07 15:03 ` Oleksij Rempel
[not found] ` <518917C4.9090607@rempel-privat.de>
[not found] ` <518917C4.9090607-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org>
2013-05-07 16:09 ` Jonathan Bither
-- strict thread matches above, loose matches on Subject: below --
2012-05-11 0:31 MCS field - STBC and Ness Simon Barber
2012-05-11 7:04 ` Wojciech Dubowik
2012-05-11 16:44 ` Simon Barber
2012-05-11 16:53 ` Simon Barber
2012-05-11 18:35 ` Johannes Berg
2012-05-12 4:27 ` Simon Barber
2012-07-05 9:12 ` Johannes Berg
2012-11-01 0:22 ` Simon Barber
2012-11-02 0:24 ` Simon Barber
[not found] ` <509312DB.7070100-vp0mx6+5gkqFX2APIN6yfw@public.gmane.org>
2012-11-17 6:32 ` Standardisation - adding 2 bit STBC and Ness to MCS 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__40512.8046324991$1367418879$gmane$org@rempel-privat.de' \
--to=linux-yek0n+yfykbzxqdaratxbw@public.gmane.org \
--cc=adrian-h+KGxgPPiopAfugRpC6u6w@public.gmane.org \
--cc=ath9k-devel-xDcbHBWguxHbcTqmT+pZeQ@public.gmane.org \
--cc=johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=radiotap-qavaossjCcEdnm+yROfE0A@public.gmane.org \
--cc=simon-vp0mx6+5gkqFX2APIN6yfw@public.gmane.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 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).