From: Ben Greear <greearb@candelatech.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: mac80211-hwsim and tx-rates.
Date: Wed, 11 Mar 2015 14:07:55 -0700 [thread overview]
Message-ID: <5500AEAB.8010605@candelatech.com> (raw)
When using the user-space transport, the netlink frame sent to user-space
has a rate index and retry count, and nothing else. Is there a
reliable way to know in user-space what index maps to what actual rate?
If not, any suggestions for how to improve this? Maybe add
a new object that passes up a bunch more info about the actual
rates instead of just the rate idx?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2015-03-11 21:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 21:07 Ben Greear [this message]
2015-03-11 21:31 ` mac80211-hwsim and tx-rates Arend van Spriel
2015-03-11 22:06 ` Ben Greear
2015-03-14 10:47 ` Bob Copeland
2015-03-14 16:14 ` Ben Greear
2015-03-14 17:48 ` Bob Copeland
2015-03-14 18:04 ` Ben Greear
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=5500AEAB.8010605@candelatech.com \
--to=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.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).