linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vladimir Koutny <vlado@work.ksp.sk>
To: "John W. Linville" <linville@tuxdriver.com>, mcgrof@gmail.com
Cc: Michael Buesch <mb@bu3sch.de>,
	Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless@vger.kernel.org
Subject: Re: 2.6.24, mac80211 and b/g switching
Date: Tue, 11 Mar 2008 17:30:52 +0100	[thread overview]
Message-ID: <47D6B3BC.9010000@work.ksp.sk> (raw)
In-Reply-To: <47D1A7AC.6010307@work.ksp.sk>

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

Hi,

> Ok, thanks for this info, I might change my plans then. I'll try this
> way first, or (if that fails) the compat-wireless-2.6 path suggested by
> Luis.

So I've opted for compat-wireless-2.6 way, and as my first concern was
to see if cw_min is being set correctly I've immediately come across an
issue here:

conf_tx (called from ieee80211_sta_set_ssid) is being called before
IEEE80211_SDATA_OPERATING_GMODE flag is set/cleared (which is done in
ieee80211_rx_mgmt_assoc_resp). That means conf_tx will use cw_min
parameters from previous association, so when you switch between B and G
APs, you will end up with wrong cw_min.

Shouldn't conf_tx better be called only/also after association finishes?
 Or should the IEEE80211_SDATA_OPERATING_GMODE flag be set prior to
auth/assoc based on previous beacon/probe response info?

Regards,
 Vlado


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

  reply	other threads:[~2008-03-11 16:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-07 15:36 2.6.24, mac80211 and b/g switching Vladimir Koutny
2008-03-07 17:12 ` Johannes Berg
2008-03-07 17:43   ` Vladimir Koutny
2008-03-07 18:16     ` Michael Buesch
2008-03-07 19:34       ` John W. Linville
2008-03-07 20:38         ` Vladimir Koutny
2008-03-11 16:30           ` Vladimir Koutny [this message]
2008-03-12 14:53             ` Johannes Berg
2008-03-07 19:40       ` Luis R. Rodriguez

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=47D6B3BC.9010000@work.ksp.sk \
    --to=vlado@work.ksp.sk \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mb@bu3sch.de \
    --cc=mcgrof@gmail.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).