linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Arend van Spriel <arend@broadcom.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: implicit band switch or not
Date: Wed, 09 Feb 2011 06:22:32 -0800	[thread overview]
Message-ID: <4D52A328.3010009@candelatech.com> (raw)
In-Reply-To: <op.vqmzowhl3ri7v4@arend-laptop>

On 02/09/2011 04:59 AM, Arend van Spriel wrote:
> Hi Johannes,
>
> With our mac80211-based driver I was associated with 5GHz AP and ran into an assert. Investigating this I found that a software scan was initiated and our
> driver got a probe request from mac80211 to be transmitted. However, it turned out that the transmit rate was a 2GHz rate and our driver was still configured to
> 5GHz band. The ieee80211_tx_info also contained the band and indeed that was for 2GHz. Given the comment for the band attribute I am wondering whether we should
> a band switch implicitly or not:
>
> * @band: the band to transmit on (use for checking for races)
>
> Any suggestions? Are we have a race condition here?

What kernel revision was this happening in?  I just changed the scanning logic
a bit in wireless-testing...I don't think I would have caused this, but it's possible.

Thanks,
Ben

>
> Gr. AvS


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

  reply	other threads:[~2011-02-09 14:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-09 12:59 implicit band switch or not Arend van Spriel
2011-02-09 14:22 ` Ben Greear [this message]
2011-02-09 14:48   ` Arend van Spriel
2011-02-09 17:10     ` Ben Greear
2011-02-14 10:05 ` 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=4D52A328.3010009@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=arend@broadcom.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    /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).