Linux wireless drivers development
 help / color / mirror / Atom feed
From: Vladimir Kondratiev <vkondrat_qca@qca.qualcomm.com>
To: "Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>
Cc: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>,
	"John W . Linville" <linville@tuxdriver.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/2] {nl,cfg}80211: support high bitrates
Date: Wed, 04 Jul 2012 08:41:08 +0300	[thread overview]
Message-ID: <1631430.V8ZCGtcpIm@lx-vladimir> (raw)
In-Reply-To: <CAB=NE6WqzHkyg94hif7hZ2EqE5EQgAX8QbexhGNoQcu27Mt2cA@mail.gmail.com>

On Tuesday, July 03, 2012 09:04:38 AM Luis R. Rodriguez wrote:
> On Tue, Jul 3, 2012 at 1:37 AM, Vladimir Kondratiev
> 
> <qca_vkondrat@qca.qualcomm.com> wrote:
> > User space tools should switch to new bitrate. Old one is deprecated and
> > going to be removed in the future.
> 
> Removed?? No way. You can't make old userspace break.
> 
> > @@ -1638,12 +1638,16 @@ struct nl80211_sta_flag_update {
> > 
> >   *
> >   * These attribute types are used with %NL80211_STA_INFO_TXRATE
> >   * when getting information about the bitrate of a station.
> > 
> > + * Legacy bitrate represented with 16-bit value, while new
> > + * "high throughput" bitrate uses 32-bit value. User space tools
> > + * should use new bitrate.
> 
> Something a bit more clearer would say that we send both, and that
> userspace should use the new one given that new technologies required
> a higher data type. 

Agree - I'll rephrase

> Also explaining what gets sent to userspace for
> those high data bit rates on the old data type would help -- from what
> I read in your patch we set those high bit rates to 0 on the old data
> type.

Not exactly. If value is 0, it is just not send:
(bitrate_compat > 0 &&
	     nla_put_u16(msg, NL80211_RATE_INFO_BITRATE, bitrate_compat)

> 
> >   *
> >   * @__NL80211_RATE_INFO_INVALID: attribute number 0 is reserved
> >   * @NL80211_RATE_INFO_BITRATE: total bitrate (u16, 100kbit/s)
> >   * @NL80211_RATE_INFO_MCS: mcs index for 802.11n (u8)
> >   * @NL80211_RATE_INFO_40_MHZ_WIDTH: 40 Mhz dualchannel bitrate
> >   * @NL80211_RATE_INFO_SHORT_GI: 400ns guard interval
> > 
> > + * @NL80211_RATE_INFO_BITRATE_HT: total bitrate (u32, 100kbit/s)
> 
> NL80211_RATE_INFO_BITRATE_HT seems misleading as likely we will also
> use this for VHT, and whatever other fun acronym the industry comes up
> with for bitrates for 802.11.

In case "HT" for "High Throuput" is misleading, I am open to any
other proposals. What name can you suggest?

Thanks, Vladimir

  reply	other threads:[~2012-07-04  5:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-03  8:37 [PATCH 0/2] High bitrate support Vladimir Kondratiev
2012-07-03  8:37 ` [PATCH 1/2] {nl,cfg}80211: support high bitrates Vladimir Kondratiev
2012-07-03 16:04   ` Luis R. Rodriguez
2012-07-04  5:41     ` Vladimir Kondratiev [this message]
2012-07-03  8:37 ` [PATCH 2/2] cfg80211: bitrate calculation for 60g Vladimir Kondratiev
2012-07-03 11:55 ` [PATCH 0/2] High bitrate support Johannes Berg
2012-07-03 18:01   ` Luis R. Rodriguez

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=1631430.V8ZCGtcpIm@lx-vladimir \
    --to=vkondrat_qca@qca.qualcomm.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=qca_vkondrat@qca.qualcomm.com \
    --cc=rodrigue@qca.qualcomm.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