linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felix Fietkau <nbd@openwrt.org>
To: Adrian Chadd <adrian@freebsd.org>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	Jonas Gorski <jogo@openwrt.org>,
	linux-wireless@vger.kernel.org,
	"John W. Linville" <linville@tuxdriver.com>,
	Nishant Sarmukadam <nishants@marvell.com>,
	Yogesh Ashok Powar <yogeshp@marvell.com>,
	Lennert Buytenhek <buytenh@wantstofly.org>
Subject: Re: [RFC/RFT] mwl8k: don't expose non-standard rates
Date: Sun, 14 Apr 2013 00:08:00 +0200	[thread overview]
Message-ID: <5169D740.7070206@openwrt.org> (raw)
In-Reply-To: <CAJ-Vmo=bwcxRHB2vESVAy-3_svM+7dDj3o5D=bWgAedMV0ZsBA@mail.gmail.com>

On 2013-04-13 8:59 PM, Adrian Chadd wrote:
> On 13 April 2013 09:18, Johannes Berg <johannes@sipsolutions.net> wrote:
> 
>>> Are these "turbo" mode rates? ie, 40MHz wide channels with pre-11n
>>> rates on them?
>>
>> 22 actually *is* a standard rate, it's just that almost nobody
>> implements it.
> 
> Well, is it the 20mhz rate or a 40mhz turbo rate?
> 
>> The original problem seems a bit strange though, seems those should just
>> not be marked basic?
> 
> Again, if its a custom rate for 11a/11g 40MHz static turbo style
> configurations, it should only be exposed when the AP is running in
> that particular mode.
> 
> And yes, if the hardware does support it, then it should really only
> not be configured for basic rates. That way mwl8k<->mwl8k hardware can
> take advantage of it when those stations are talking to each other.
> 
> (Yeah, I come from a world where FreeBSD users still want to run
> Turbo/Static-40MHz operation with things like fast frames and turbo
> rates.. damned legacy hardware. :-)
I really don't think this is a 40 MHz thing, the driver does not seem to
have any concept of a non-standard legacy 40 MHz mode. I think they
simply added different modulation for the 72 MBit/s rate.
Keeping this rate doesn't even make sense for mwl8k<->mwl8k, as it's a
non-standard legacy rate, whereas the device can do much better with
plain 802.11n :)

- Felix

  reply	other threads:[~2013-04-13 22:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-13 10:31 [RFC/RFT] mwl8k: don't expose non-standard rates Jonas Gorski
2013-04-13 14:29 ` Adrian Chadd
2013-04-13 16:18   ` Johannes Berg
2013-04-13 18:59     ` Adrian Chadd
2013-04-13 22:08       ` Felix Fietkau [this message]
2013-04-14 10:49     ` Jonas Gorski
2013-04-14 12:11 ` [PATCH] mwl8k: remove nonstandard rate 72 Mbps Jonas Gorski
2013-04-15  6:38   ` Yogesh Ashok Powar
2013-04-15  7:53     ` Jonas Gorski

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=5169D740.7070206@openwrt.org \
    --to=nbd@openwrt.org \
    --cc=adrian@freebsd.org \
    --cc=buytenh@wantstofly.org \
    --cc=jogo@openwrt.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=nishants@marvell.com \
    --cc=yogeshp@marvell.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).