From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Bob Copeland <me@bobcopeland.com>
Subject: Re: question on "mac80211_hwsim: support any address in userspace"
Date: Wed, 16 Dec 2015 14:42:42 +0100 [thread overview]
Message-ID: <1450273362.8247.15.camel@sipsolutions.net> (raw)
In-Reply-To: <567168AF.4060804@candelatech.com>
On Wed, 2015-12-16 at 05:35 -0800, Ben Greear wrote:
> Well, the old code used it as a key, and the old documentation used
> it as a key, so it is a bit of a regression to change the behaviour
> now.
But it's still used as a key, no? Just the value changed. If you treat
it as a key then you'd just have it for a frame incoming and outgoing?
> > I think this is pretty much a done deal by now though since I don't
> > really want to break wmediumd.
>
> It was not the only user-space to use the API :)
So you're saying you have code that broke? How did it break though, I
don't really see it yet. Can you explain?
> Well, that would be fine too. The nice thing about the
> address,though, is that you can query it as part of
> /sys/class/ieee..... and other already-implemented
> interfaces. Finding the radio-id would require new API in this case,
> which is a bit of work.
Well, it was always rather awkward since it was the *second* address :)
You can query the ID/index already through the netlink API, or even
from sysfs since the virtual device name is essentially
sprintf(name, "hwsim%d", idx)
johannes
next prev parent reply other threads:[~2015-12-16 13:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-16 3:29 question on "mac80211_hwsim: support any address in userspace" Ben Greear
2015-12-16 9:17 ` Johannes Berg
2015-12-16 13:13 ` Ben Greear
2015-12-16 13:25 ` Johannes Berg
2015-12-16 13:35 ` Ben Greear
2015-12-16 13:42 ` Johannes Berg [this message]
2015-12-16 14:11 ` Ben Greear
2015-12-16 14:14 ` Johannes Berg
2015-12-16 14:15 ` Johannes Berg
2015-12-16 14:59 ` Bob Copeland
2015-12-16 15:52 ` Ben Greear
2015-12-16 17:30 ` Adam R. Welle
2015-12-16 17:46 ` Bob Copeland
2015-12-16 18:57 ` Adam R. Welle
2015-12-16 22:14 ` Ben Greear
2015-12-16 22:56 ` Adam R. Welle
2015-12-16 23:20 ` Ben Greear
2015-12-16 23:56 ` Adam R. Welle
2015-12-17 13:26 ` Bob Copeland
2015-12-16 13:21 ` me@bobcopeland.com >> Bob Copeland
2015-12-16 13:27 ` Ben Greear
2015-12-16 13:57 ` me@bobcopeland.com >> Bob Copeland
2015-12-16 14:16 ` Ben Greear
2015-12-16 14:33 ` me@bobcopeland.com >> Bob Copeland
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=1450273362.8247.15.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
--cc=me@bobcopeland.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).