From: Ivo van Doorn <ivdoorn@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: netdev <netdev@vger.kernel.org>,
"John W. Linville" <linville@tuxdriver.com>,
Jiri Benc <jbenc@suse.cz>, Jouni Malinen <jkm@devicescape.com>,
Simon Barber <simon@devicescape.com>,
Hong Liu <hong.liu@intel.com>,
Michael Wu <flamingice@sourmilk.net>,
Michael Buesch <mbuesch@freenet.de>,
David Kimdon <david.kimdon@devicescape.com>,
James Ketrenos <jketreno@linux.intel.com>
Subject: Re: [PATCH 0/11] convert d80211 to a proper protocol
Date: Sun, 5 Nov 2006 17:54:33 +0100 [thread overview]
Message-ID: <200611051754.34099.IvDoorn@gmail.com> (raw)
In-Reply-To: <1162741174.24574.22.camel@johannes.berg>
Hi,
> I figured I'd look how hard it actually was to convert d80211 to a
> proper protocol. And contrary to my own expectations I succeeded in
> doing that in just over a day. Just like 8021q, it has virtual devices.
>
> The patchset is huge and can be found at
> http://johannes.sipsolutions.net/files/d80211-proto/
I have a question regarding the enabling and disabling the radio
in this new layout.
Previously the open() and stop() methods in ieee80211_hw had been
deprecated and the driver should enable or disable the radio
based on the add_interface and remove_interface() functions.
Now that the driver should provide open() and stop() for the netdevice
structure does this mean that these 2 methods are back in control
for enabling and disabling the radio? And if so what should the
add_interface and remove_interface, should they be only in charge of
triggering some configuration changes (like mode and mac address)?
Ivo
next prev parent reply other threads:[~2006-11-05 16:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-05 15:39 [PATCH 0/11] convert d80211 to a proper protocol Johannes Berg
2006-11-05 16:54 ` Ivo van Doorn [this message]
2006-11-05 17:05 ` Johannes Berg
2006-11-05 17:09 ` Johannes Berg
2006-11-05 17:06 ` Johannes Berg
2006-11-06 20:01 ` Jiri Benc
2006-11-06 21:09 ` Johannes Berg
2006-11-08 11:58 ` Jiri Benc
2006-11-08 12:33 ` Johannes Berg
2006-11-08 13:36 ` Jeff Garzik
2006-11-06 23:06 ` Johannes Berg
2006-11-08 12:09 ` Jiri Benc
2006-11-08 12:53 ` Johannes Berg
2006-11-07 18:52 ` Johannes Berg
2006-11-07 19:02 ` Ivo van Doorn
2006-11-07 20:33 ` 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=200611051754.34099.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=david.kimdon@devicescape.com \
--cc=flamingice@sourmilk.net \
--cc=hong.liu@intel.com \
--cc=jbenc@suse.cz \
--cc=jketreno@linux.intel.com \
--cc=jkm@devicescape.com \
--cc=johannes@sipsolutions.net \
--cc=linville@tuxdriver.com \
--cc=mbuesch@freenet.de \
--cc=netdev@vger.kernel.org \
--cc=simon@devicescape.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.