linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Dan Williams <dcbw@redhat.com>
Cc: "Winkler, Tomas" <tomas.winkler@intel.com>,
	dragoran <drago01@gmail.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: Fri, 03 Aug 2007 11:42:57 +0200	[thread overview]
Message-ID: <1186134177.4647.19.camel@johannes.berg> (raw)
In-Reply-To: <1186080675.9527.10.camel@xo-13-A4-25.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]

On Thu, 2007-08-02 at 14:51 -0400, Dan Williams wrote:

> Well, to be honest none of the drivers before mac80211 required you to
> down the device to change modes.  But they were mostly fullmac, or
> half-mac like ipw2x00.  Since mac80211 has only just become useful in
> the past couple of months for most people, it's not really fair to
> expect versions of NM that were out before mac80211 landed to play nice
> with what mac80211 expects, which is different from what other drivers
> implement.

True.

> Not to say NM shouldn't be fixed for this.  The other problem is that
> there's really not a good way to determine whether the driver is
> actually _ready_ after down it and bringing it back up.  You basically
> have to spin & block until the interface gets IFF_UP set on it again,
> and even then that's not entirely reliable.

Not sure I understand? Drivers can fully well block the userspace task
that is doing the IFF_UP until they're read? bcm43xx does that.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

  reply	other threads:[~2007-08-03  9:43 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
2007-08-02 18:51         ` Dan Williams
2007-08-03  9:42           ` Johannes Berg [this message]
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=1186134177.4647.19.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=dcbw@redhat.com \
    --cc=drago01@gmail.com \
    --cc=ipw3945-devel@lists.sourceforge.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).