linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: Ulrich Kunitz <kune@deine-taler.de>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	Michael Wu <flamingice@sourmilk.net>,
	Daniel Drake <dsd@gentoo.org>,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH] zd1211rw-mac80211: debug output for mac80211 ops
Date: Tue, 31 Jul 2007 01:05:55 +0200	[thread overview]
Message-ID: <200707310105.55863.mb@bu3sch.de> (raw)
In-Reply-To: <20070730225205.GA17252@deine-taler.de>

On Tuesday 31 July 2007, Ulrich Kunitz wrote:
> What about add_interface/remove_interfaces and monitor interfaces?
> 
> There seems to be difference between "hard" and "soft" monitor
> mode. Currently I'm not sure what the semantics is. There seems to
> be also calls to add_interface/remote_interface with if_id -1. I
> guess that means something like all interfaces. The expected
> behaviour is not documented for that case. 

I suggest you look at bcm43xx-mac80211.
You will need to introduce refcounting for your monitor interfaces
and I _really_ suggest to get rid of the zd_op_open() and zd_op_close()
functions. Just include that in add/remove interface. You need
to refcount your interfaces anyway.

I don't know what you mean by hard/soft monitor.

Don't care about the id_id. It's a cookie and it's opaque to
the driver.

Semantics are pretty easy for add/remove interface. The function
is called every time the user adds/removes an interface. :)

  reply	other threads:[~2007-07-30 23:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070730023128.99E927B409F@zog.reactivated.net>
2007-07-30  3:21 ` [PATCH] zd1211rw-mac80211: debug output for mac80211 ops Michael Wu
2007-07-30 14:51   ` John W. Linville
2007-07-30 22:52     ` Ulrich Kunitz
2007-07-30 23:05       ` Michael Buesch [this message]
2007-07-30 23:25         ` Andy Green
2007-07-31 21:12           ` Jiri Benc
2007-07-31 21:30             ` Michael Buesch
2007-07-31 21:42               ` Andy Green
2007-07-31 21:50             ` Andy Green
2007-07-31  5:22         ` Michael Wu
2007-07-31  9:39           ` Michael Buesch
2007-07-31 21:06           ` Jiri Benc
2007-07-31 21:39             ` Michael Buesch
2007-07-31  5:06       ` Michael Wu
2007-07-31 21:00       ` Jiri Benc
2007-07-31 21:37         ` Michael Buesch
2007-07-31 22:10           ` Jiri Benc

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=200707310105.55863.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=dsd@gentoo.org \
    --cc=flamingice@sourmilk.net \
    --cc=kune@deine-taler.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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).