From: "Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Vladimir Kondratiev <vkondrat_qca@qca.qualcomm.com>,
Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>,
"John W . Linville" <linville@tuxdriver.com>,
<linux-wireless@vger.kernel.org>
Subject: Re: [RFC 60g 5/5] wireless: bitrate calculation for 60g
Date: Mon, 2 Jul 2012 13:13:10 -0700 [thread overview]
Message-ID: <20120702201310.GD21658@tux> (raw)
In-Reply-To: <1341259898.19776.0.camel@jlt3.sipsolutions.net>
On Mon, Jul 02, 2012 at 10:11:38PM +0200, Johannes Berg wrote:
> On Mon, 2012-07-02 at 12:28 -0700, Luis R. Rodriguez wrote:
>
> > > Expanding bitrate to u32 would break all userspace tools.
> >
> > Unless userspace is told that a new high value is used. We could
> > for example attach a flag to tell userspace that a different
> > bitrate type should be used. We can also just get new userspace
> > to start embracing the new data type, and old userspace would
> > simply not support that bit rate.
>
> The solution Vladimir proposed addresses all of that :-)
To the hip hop.. hippity hop !
Luis
prev parent reply other threads:[~2012-07-02 20:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 11:16 [RFC 60g 0/5] Infrastructure for 60g (802.11ad) Vladimir Kondratiev
2012-06-28 11:16 ` [RFC 60g 1/5] wireless: add 802.11ad (60gHz band) Vladimir Kondratiev
2012-06-28 18:03 ` Johannes Berg
2012-06-28 11:16 ` [RFC 60g 2/5] wireless: rate check logic for 60g Vladimir Kondratiev
2012-06-28 18:04 ` Johannes Berg
2012-07-01 12:05 ` Vladimir Kondratiev
2012-06-28 11:16 ` [RFC 60g 3/5] wireless: regulatory " Vladimir Kondratiev
2012-06-28 11:16 ` [RFC 60g 4/5] wireless: 60g protocol constants Vladimir Kondratiev
2012-06-28 18:06 ` Johannes Berg
2012-06-28 11:17 ` [RFC 60g 5/5] wireless: bitrate calculation for 60g Vladimir Kondratiev
2012-06-28 18:07 ` Johannes Berg
[not found] ` <1703117.VxUDt2UvbQ@lx-vladimir>
[not found] ` <2090114.iKoJhGKOAs@lx-vladimir>
2012-07-02 19:28 ` Luis R. Rodriguez
2012-07-02 20:11 ` Johannes Berg
2012-07-02 20:13 ` Luis R. Rodriguez [this message]
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=20120702201310.GD21658@tux \
--to=rodrigue@qca.qualcomm.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=qca_vkondrat@qca.qualcomm.com \
--cc=vkondrat_qca@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;
as well as URLs for NNTP newsgroup(s).