Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Subject: nl/cfg80211 scan result/event handling
Date: Sat, 16 Jun 2007 21:49:32 +0200	[thread overview]
Message-ID: <1182023372.9058.68.camel@johannes.berg> (raw)

[-- Attachment #1: Type: text/plain, Size: 1235 bytes --]

Hey,

Just a few notes as I'm thinking about these things. I probably won't be
implementing this quickly so I'm telling you, but who knows, maybe I'll
get around to it and then... Here's hoping for some feedback :)

Right now I'm thinking along the lines of:
void cfg80211_key_threshold_notify(struct wireless_dev *wdev,
				   int txrx_count,
				   u8 *mac);

or
void cfg80211_radar_notify(struct wireless_dev *wdev,
			   phymode, channel, ...)

and then cfg80211 is responsible for sending the appropriate nl80211
messages or doing whatever else to notify userspace.

As for scan results, we want those broadcast as well. I was thinking
that we have basically these choices:
 1) drivers (stack) aggregate data
 2) drivers (stack) call a function for each result
 3) hybrid

I tend towards 3 because it allows both, in a fashion like this:

cfg80211_add_scan_result(struct wireless_dev *wdev,
			 int n_results,
			 struct scan_result **sr);
cfg80211_scan_finished(struct wireless_dev *wdev);

and for the add_scan_result calls cfg80211 simply starts creating the
nl80211 message and then multicasts it to those who want it
(NL80211_GROUP_SCAN or such) on _scan_finished()

Thoughts?

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

             reply	other threads:[~2007-06-16 19:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-16 19:49 Johannes Berg [this message]
2007-06-17 15:13 ` nl/cfg80211 scan result/event handling Dan Williams
2007-06-18  8:37   ` 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=1182023372.9058.68.camel@johannes.berg \
    --to=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