From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC] mac80211_hwsim: notify user-space about channel change.
Date: Tue, 24 Feb 2015 15:40:34 +0100 [thread overview]
Message-ID: <1424788834.2192.34.camel@sipsolutions.net> (raw)
In-Reply-To: <54EC8C5D.5090400@candelatech.com>
On Tue, 2015-02-24 at 06:36 -0800, Ben Greear wrote:
> We could push more and more of this to user-space and let it decide whether and
> how to forward or accept frames for particular radios.
Sure, no objection to that. However, just arbitrarily adding a "change
channel" call, without thinking about the realities of the code already
supporting multi-channel concurrency, remain-on-channel and hw-scan
operations won't get us very far and just lead to issues with the API.
> But, to do that, we need the low-level settings sent to user-space
> (such as current channel). Encryption keys could be a future enhancement
> here, so that we can do 'hardware' encryption in hwsim (and handle encrypt/decrypt
> logic however we want in user-space).
Sure. I'd just like to ask that the API is actually useful in more than
the default single-channel support BSS-only case :)
johannes
next prev parent reply other threads:[~2015-02-24 14:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-17 23:59 [RFC] mac80211_hwsim: notify user-space about channel change greearb
2015-02-23 11:49 ` Johannes Berg
2015-02-23 17:43 ` Ben Greear
2015-02-24 10:11 ` Johannes Berg
2015-02-24 14:36 ` Ben Greear
2015-02-24 14:40 ` Johannes Berg [this message]
2015-03-11 21:05 ` Ben Greear
2015-03-31 14:27 ` Johannes Berg
2015-03-31 15:56 ` Ben Greear
2015-04-14 8:13 ` Johannes Berg
2015-04-14 14:56 ` Ben Greear
2015-04-14 15:06 ` Johannes Berg
2015-04-14 15:55 ` Ben Greear
2015-04-15 9:33 ` Johannes Berg
2015-04-15 15:06 ` Ben Greear
2015-04-17 11:25 ` Johannes Berg
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=1424788834.2192.34.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.