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, 14 Apr 2015 17:06:30 +0200 [thread overview]
Message-ID: <1429023990.3019.15.camel@sipsolutions.net> (raw)
In-Reply-To: <552D2A90.1070307@candelatech.com>
On Tue, 2015-04-14 at 07:56 -0700, Ben Greear wrote:
> > Well, the question isn't really that offloading, the question is what
> > happens with the hw-scan logic in hwsim? Though I guess now that I think
> > about it, that wouldn't show up in userspace at all with your changes.
>
> I think for HW scan and related matters, you treat user-space like a firmware
> target, so you send it a message, and then get some response or action, similar
> to how you would request ath10k or some USB dongle NIC to do things for you.
That's not really how it works today, but it's one possible (probably
the only possible) approach.
> My own interest in hwsim user-space is to make it act more like ath9k
> than a firmware target driver, but I don't think my changes preclude doing
> target based emulation in the future.
True, although I'd like to see the multi-channel issue addressed better.
johannes
next prev parent reply other threads:[~2015-04-14 15:06 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
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 [this message]
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=1429023990.3019.15.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 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).