linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Derek Atkins <warlord@MIT.EDU>
To: dragoran <drago01@gmail.com>
Cc: "Johannes Berg" <johannes@sipsolutions.net>, "Winkler\,
	Tomas" <tomas.winkler@intel.com>,
	linux-wireless@vger.kernel.org,
	network manager <networkmanager-list@gnome.org>,
	ipw3945-devel@lists.sourceforge.net
Subject: Re: [ipw3945-devel] chaning mode only when interface down?
Date: Thu, 02 Aug 2007 11:52:26 -0400	[thread overview]
Message-ID: <sjmir7yx7b9.fsf@pgpdev.ihtfp.org> (raw)
In-Reply-To: <f6ca9fed0708020643p53ceedcav76b14814b1b1cabd@mail.gmail.com> (dragoran's message of "Thu\, 2 Aug 2007 15\:43\:24 +0200")

dragoran <drago01@gmail.com> writes:

> On 8/2/07, Johannes Berg <johannes@sipsolutions.net> wrote:
>
>     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?
>    
>     Until then (and I guess somebody *really* wants it) it's just a lot
>     easier to not even try to change these low-level things while the
>     interface is operating.
>
> ok fair enough

Well, for one thing in many cases the interface needs to be "up" in
order to scan.  Also, many times the driver itself will incorrectly
associate on insert before NetworkManager gets a chance to chime in
and then you're stuck in a situation where you never get to the band
you want.

Regardless, you should NEVER require a driver reload to switch bands
and if you do that's a bug.  If mac80211 requires a driver reload then
that's a MAJOR flaw in that layer.

Still, NM keeps the interface "up" even when there's no packets,
because it's required to scan.  So that may be why I've had trouble
going between 802.11(a) and 802.11(b/g) networks at times.  It's quite
frustrating.

-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

  parent reply	other threads:[~2007-08-02 16:22 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 [this message]
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
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=sjmir7yx7b9.fsf@pgpdev.ihtfp.org \
    --to=warlord@mit.edu \
    --cc=drago01@gmail.com \
    --cc=ipw3945-devel@lists.sourceforge.net \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --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).