linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: John W Linville <linville@tuxdriver.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Regression in 3.7-rc2 for b43 and b43legacy
Date: Wed, 24 Oct 2012 21:09:36 -0500	[thread overview]
Message-ID: <50889F60.5090406@lwfinger.net> (raw)

Johannes,

I have discovered that both b43 and b43legacy broke somewhere between 3.7-rc1 
and 3.7-rc2. The problem was bisected to commit fe57d9f. The commit message is

commit fe57d9f5c0a2c1ef97ba8cdc42cfda5743f287b8
Author: Johannes Berg <johannes.berg@intel.com>
Date:   Thu Jul 26 14:55:08 2012 +0200

     mac80211: track whether to use channel contexts

     Depending on the driver, channel contexts may be used or
     not. If they are used, the driver must have support for
     hardware scan and remain-on-channel; otherwise the driver
     must not advertise support for multiple channels.

     Also prohibit WDS type interfaces when channel contexts
     are to be used as there's no clear definition of which
     channel they use.

     Signed-off-by: Johannes Berg <johannes.berg@intel.com>

It seems likely that the drivers are inadvertently advertising support for 
multiple channels, What must be done to turn off this "feature"?

Thanks,

Larry

             reply	other threads:[~2012-10-25  2:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-25  2:09 Larry Finger [this message]
2012-10-25  2:19 ` Regression in 3.7-rc2 for b43 and b43legacy Sujith Manoharan
2012-10-25  6:00   ` Larry Finger
2012-10-25  7:21     ` Johannes Berg
2012-10-25 17:11     ` Regression in 3.7-rc2 for b43 and b43legacy [and ath9k] Henry Ptasinski

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=50889F60.5090406@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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).