From: Derek Atkins <warlord@MIT.EDU>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: network manager <networkmanager-list@gnome.org>,
Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org, "Winkler\,
Tomas" <tomas.winkler@intel.com>,
ipw3945-devel@lists.sourceforge.net
Subject: Re: [ipw3945-devel] chaning mode only when interface down?
Date: Fri, 03 Aug 2007 11:10:36 -0400 [thread overview]
Message-ID: <sjmhcngwt5f.fsf@pgpdev.ihtfp.org> (raw)
In-Reply-To: <20070803145305.GE5137@tuxdriver.com> (John W. Linville's message of "Fri\, 3 Aug 2007 10\:53\:05 -0400")
"John W. Linville" <linville@tuxdriver.com> writes:
> On Fri, Aug 03, 2007 at 10:33:07AM -0400, Derek Atkins wrote:
>> Johannes Berg <johannes@sipsolutions.net> writes:
>>
>> > On Thu, 2007-08-02 at 14:48 +0200, dragoran wrote:
>> >
>> >> > Nono, you cannot solve it in the driver. The whole design of mac80211
>> >> > mandates that assumption and I think it is a valid one to make.
>> >> why? did the old way (allow mode changing while up) caused any problems?
>> >
>> > Why should it be allowed? Can you come up with a good reason for that
>> > since you lose all state anyway when doing mode transitions?
>>
>> Um, what state? Sure you lose your layer 2 state, but why force a
>> layer 3 lossage when you don't necessarily have to do so? For
>> example, I've seen plenty of networks that have both 802.11(a) and
>> 802.11(b/g) networks that share absolutely everything at layer 3.
>
> I think you are confusing a/b/g "mode" (which is _not_ the topic)
> with AP/STA/IBSS/monitor "mode" (which is the topic).
Indeed I am, mea culpa. I'll go shut up now.
> John
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
warlord@MIT.EDU PGP key available
next prev parent reply other threads:[~2007-08-03 15:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 7:44 chaning mode only when interface down? dragoran
2007-08-02 9:14 ` Johannes Berg
2007-08-02 9:16 ` dragoran
2007-08-02 12:17 ` [ipw3945-devel] " Winkler, Tomas
2007-08-02 12:34 ` Johannes Berg
2007-08-02 12:41 ` Winkler, Tomas
2007-08-02 12:46 ` Johannes Berg
2007-08-02 13:11 ` Tomas Winkler
2007-08-02 12:48 ` dragoran
2007-08-02 12:53 ` Johannes Berg
[not found] ` <f6ca9fed0708020643p53ceedcav76b14814b1b1cabd@mail.gmail.com>
2007-08-02 15:52 ` Derek Atkins
2007-08-03 9:41 ` Johannes Berg
2007-08-03 14:33 ` Derek Atkins
2007-08-03 14:50 ` Johannes Berg
2007-08-03 14:53 ` John W. Linville
2007-08-03 15:10 ` Derek Atkins [this message]
2007-08-02 18:51 ` Dan Williams
2007-08-03 9:42 ` Johannes Berg
2007-08-03 11:20 ` Dan Williams
2007-08-30 22:24 ` blocking in dev->open (was: [ipw3945-devel] chaning mode only when interface down?) Johannes Berg
2007-08-02 9:18 ` chaning mode only when interface down? Andy Green
2007-08-02 9:59 ` Johannes Berg
2007-08-02 18:47 ` Dan Williams
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=sjmhcngwt5f.fsf@pgpdev.ihtfp.org \
--to=warlord@mit.edu \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=networkmanager-list@gnome.org \
--cc=tomas.winkler@intel.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).