From: Michael Buesch <mb@bu3sch.de>
To: Jiri Benc <jbenc@suse.cz>
Cc: Michael Wu <flamingice@sourmilk.net>,
Ulrich Kunitz <kune@deine-taler.de>,
"John W. Linville" <linville@tuxdriver.com>,
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 23:39:52 +0200 [thread overview]
Message-ID: <200707312339.53025.mb@bu3sch.de> (raw)
In-Reply-To: <20070731230613.6d0a0856@logostar.upir.cz>
On Tuesday 31 July 2007 23:06:13 Jiri Benc wrote:
> On Mon, 30 Jul 2007 22:22:58 -0700, Michael Wu wrote:
> > On Monday 30 July 2007 16:05, Michael Buesch wrote:
> > > 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.
> > >
> > Requiring refcounting for monitor interfaces is fairly dumb since mac80211
> > does the exact same refcounting. I haven't bothered to do it in any driver
> > ports yet for this reason. This part of the mac80211 driver api needs to be
> > fixed.
>
> Ouch, I thought we don't bother drivers with more than one monitor
> interface at a time. Apparently I forgot to fix that.
>
> > Also, I'm not entirely convinced that eliminating the open/close callbacks is
> > a good idea,
>
> Why?
Yeah, I don't see the need for open/close, either.
We can live perfectly well without them. It even reduces code complexity
and makes drivers more readable.
In add/remove you better know anyway, if the interface is up or down.
So if it's down in add_interface, just init it. It's a matter of an if statement.
Really nothing more.
--
Greetings Michael.
next prev parent reply other threads:[~2007-07-31 21:40 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
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 [this message]
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=200707312339.53025.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=dsd@gentoo.org \
--cc=flamingice@sourmilk.net \
--cc=jbenc@suse.cz \
--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).