From: "Alina Friedrichsen" <x-alina@gmx.net>
To: mb@bu3sch.de
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2] mac80211: Call commit() on channel setting
Date: Fri, 27 Feb 2009 16:39:21 +0100 [thread overview]
Message-ID: <20090227153921.254900@gmx.net> (raw)
In-Reply-To: <20090227153516.318880@gmx.net>
> I think after all changes which affect the selected network a rejoin
> should be done.
>=20
> For example you have at channel 4 a AP with the SSID "test" und at ch=
annel
> 11 an other AP with the same SSID, too.
>=20
> If you now first say set_ssid("test") and then set_channel(11), we fi=
rst
> join the network at channel 4 and then we switch the hardware low-lev=
el to
> channel 11. So we hang now in channel 4 with the BSSID of the network=
in
> channel 4 and nothing works anymore.
So we hang now in channel _11_ with the BSSID of the network in
channel 4 and nothing works anymore.
> I think the order of the commands should not affect the result on the=
end
> and the driver should never hang in an broken/undefined state if it c=
an be
> recovered.
--=20
Computer Bild Tarifsieger! GMX FreeDSL - Telefonanschluss + DSL
f=FCr nur 17,95 =BF/mtl.!* http://dsl.gmx.de/?ac=3DOM.AD.PD003K11308T45=
69a
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-02-27 15:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-26 23:43 [PATCH v2] mac80211: Call commit() on channel setting Alina Friedrichsen
2009-02-27 14:03 ` Michael Buesch
2009-02-27 15:35 ` Alina Friedrichsen
2009-02-27 15:39 ` Alina Friedrichsen [this message]
[not found] ` <20090227153418.254900@gmx.net>
2009-02-27 16:14 ` Michael Buesch
2009-02-27 17:16 ` Alina Friedrichsen
2009-02-27 18:25 ` [PATCH v3] " Alina Friedrichsen
2009-02-27 16:20 ` [PATCH v2] " Johannes Berg
2009-02-27 21:26 ` Alina Friedrichsen
2009-02-27 21:35 ` 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=20090227153921.254900@gmx.net \
--to=x-alina@gmx.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
/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.