From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC 1/2] wireless: Show sta_flags for status in /proc/net/wireless
Date: Thu, 30 Sep 2010 08:31:12 -0700 [thread overview]
Message-ID: <4CA4AD40.1010309@candelatech.com> (raw)
In-Reply-To: <1285832587.3639.1.camel@jlt3.sipsolutions.net>
On 09/30/2010 12:43 AM, Johannes Berg wrote:
> On Wed, 2010-09-29 at 16:57 -0700, greearb@candelatech.com wrote:
>
>> User-space can then decode the flags to determine associated,
>> scanning, and other states.
>
> I really don't think we should be extending the useful life of wireless
> extensions.
>
>
>> * @signal: signal strength of last received packet in dBm
>> + * @status: ieee80211_sta_info_flags plus: (1<<15) Scanning.
>
>
> And are you seriously proposing to make internal mac80211 flags part of
> the externally visible cfg80211 API??
It would of course be easy to map them to a stable set of flags, but if you
don't want to fix /proc/net/wireless anyway, then I might as well do minimal changes
to make it easier to keep the patch in my own tree.
Aside from listening to 'iw event', is there any way to know if a STA is scanning,
authenticated, associated, etc? Some of this can be obtained from debugfs, but
that's not a fun api to code against...
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2010-09-30 15:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 23:57 [RFC 1/2] wireless: Show sta_flags for status in /proc/net/wireless greearb
2010-09-29 23:57 ` [RFC 2/2] wireless: Report noise to /proc/net/wireless greearb
2010-09-30 7:45 ` Johannes Berg
2010-09-30 15:35 ` Ben Greear
2010-09-30 7:43 ` [RFC 1/2] wireless: Show sta_flags for status in /proc/net/wireless Johannes Berg
2010-09-30 15:31 ` Ben Greear [this message]
2010-09-30 15:39 ` Johannes Berg
2010-09-30 16:49 ` 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=4CA4AD40.1010309@candelatech.com \
--to=greearb@candelatech.com \
--cc=johannes@sipsolutions.net \
--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).