From: Johannes Berg <johannes@sipsolutions.net>
To: victorg@ti.com
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC 3/5] nl80211/cfg80211: adding intermediate scan result event.
Date: Thu, 08 Sep 2011 16:42:21 +0200 [thread overview]
Message-ID: <1315492941.16729.12.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4E68D3BF.5090201@ti.com>
On Thu, 2011-09-08 at 17:39 +0300, Victor Goldenshtein wrote:
> > No, I don't think you can advertise wiphy.flags since those flags are
> > internal -- you'll have to map single wiphy flags to single capability
> > flags which are also defined in nl80211.h.
> >
> > I'd call it "NL80211_ATTR_CAPABILITIES" to sidestep the issue of it
> > being a driver of HW or whatever capability.
> Sorry, I'm not sure that I'm entirely understand, you mean to create
> *nested* "NL80211_ATTR_CAPABILITIES" attribute which will contain all
> new capability flags, mapped from wiphy.flags? and to do it within
> existing nl80211_send_wiphy() function?
No, I mean just add a U32 NL80211_ATTR_CAPABILITIES and put new flags
there, like this in nl80211.h:
enum nl80211_device_capabilities {
NL80211_DEV_CAPA_XXX = (1<<0);
etc...
};
Just don't use wiphy.flags directly since that's internal flags.
johannes
next prev parent reply other threads:[~2011-09-08 14:42 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-05 12:02 [RFC 0/5] Scan optimization Victor Goldenshtein
2011-09-05 12:02 ` [RFC v2 1/5] nl80211/cfg80211: adding 'scan_cancel' command Victor Goldenshtein
2011-09-05 12:05 ` Johannes Berg
[not found] ` <4E6736CE.20004@ti.com>
2011-09-07 9:26 ` Johannes Berg
2011-09-05 12:02 ` [RFC v2 2/5] mac80211: " Victor Goldenshtein
2011-09-05 12:06 ` Johannes Berg
2011-09-05 12:02 ` [RFC 3/5] nl80211/cfg80211: adding intermediate scan result event Victor Goldenshtein
2011-09-05 12:08 ` Johannes Berg
2011-09-05 12:08 ` Johannes Berg
[not found] ` <4E6736D9.3070804@ti.com>
2011-09-07 9:26 ` Johannes Berg
2011-09-08 6:31 ` Victor Goldenshtein
2011-09-08 6:49 ` Johannes Berg
2011-09-08 8:56 ` Victor Goldenshtein
2011-09-08 9:27 ` Johannes Berg
2011-09-08 14:39 ` Victor Goldenshtein
2011-09-08 14:42 ` Johannes Berg [this message]
2011-09-21 15:31 ` Jouni Malinen
2011-09-21 15:45 ` Luciano Coelho
2011-09-21 16:28 ` Victor Goldenshtein
2011-09-21 16:38 ` Johannes Berg
2011-09-22 6:41 ` Victor Goldenshtein
2011-09-22 6:49 ` Luciano Coelho
2011-09-22 7:13 ` Victor Goldenshtein
2011-09-22 7:15 ` Luciano Coelho
2011-09-22 7:54 ` Johannes Berg
2011-09-21 8:19 ` Victor Goldenshtein
2011-09-21 8:35 ` Johannes Berg
2011-09-21 9:03 ` Luciano Coelho
2011-09-21 10:16 ` Johannes Berg
2011-09-05 12:02 ` [RFC 4/5] mac80211: adding intermediate scan result event call Victor Goldenshtein
2011-09-05 12:02 ` [RFC 5/5] nl80211/cfg80211: adding intermediate scan result filter Victor Goldenshtein
2011-09-05 12:11 ` 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=1315492941.16729.12.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=victorg@ti.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).