From: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>
To: "John W . Linville" <linville@tuxdriver.com>,
Johannes Berg <johannes@sipsolutions.net>
Cc: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>,
<linux-wireless@vger.kernel.org>,
"Luis R . Rodriguez" <rodrigue@qca.qualcomm.com>
Subject: [PATCH v1 0/2] High bitrate support
Date: Wed, 4 Jul 2012 10:21:58 +0300 [thread overview]
Message-ID: <1341386520-25244-1-git-send-email-qca_vkondrat@qca.qualcomm.com> (raw)
I rephrased comments following Luis's input.
As for the name for new option, still have no idea what
is the best name, thus leaving NL80211_RATE_INFO_BITRATE_HT
Anyone to suggest better name?
Proposed patches solve issue with high bitrates not fitting into u16.
I split it into 2 patches: one introduces new u32 bitrate,
and 2-nd adds 60g specific calculations.
Idea is to report (in nl80211) both old and new values,
or only new if it not fits into u16.
User space tools encouraged to migrate to the new bitrate.
cfg80211_calculate_bitrate() changed to return u32
There are few places where cfg80211_calculate_bitrate() used
besides nl80211.c; but these places are OK with bitrate changing
from u16 to u32.
Vladimir Kondratiev (2):
{nl,cfg}80211: support high bitrates
cfg80211: bitrate calculation for 60g
include/linux/nl80211.h | 8 ++++++++
include/net/cfg80211.h | 4 +++-
net/wireless/nl80211.c | 9 +++++++--
net/wireless/util.c | 51 ++++++++++++++++++++++++++++++++++++++++++++++-
4 files changed, 68 insertions(+), 4 deletions(-)
--
1.7.9.5
next reply other threads:[~2012-07-04 7:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 7:21 Vladimir Kondratiev [this message]
2012-07-04 7:21 ` [PATCH v1 1/2] {nl,cfg}80211: support high bitrates Vladimir Kondratiev
2012-07-04 7:22 ` [PATCH v1 2/2] cfg80211: bitrate calculation for 60g Vladimir Kondratiev
2012-07-04 7:28 ` [PATCH v1 0/2] High bitrate support Johannes Berg
2012-07-04 7:54 ` Johannes Berg
2012-07-04 8:46 ` Vladimir Kondratiev
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=1341386520-25244-1-git-send-email-qca_vkondrat@qca.qualcomm.com \
--to=qca_vkondrat@qca.qualcomm.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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