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: Michael Buesch <mb@bu3sch.de>,
	linux-wireless@vger.kernel.org,
	John Linville <linville@tuxdriver.com>
Subject: Re: [RFT 3/3] b43/legacy: port to cfg80211 rfkill
Date: Tue, 02 Jun 2009 18:26:52 -0500	[thread overview]
Message-ID: <4A25B53C.3040101@lwfinger.net> (raw)
In-Reply-To: <1243976470.7176.12.camel@johannes.local>

Johannes Berg wrote:
> 
> Thanks for testing. This doesn't happen on a current wireless-testing
> tree I hope? I'll look more into it tomorrow, need some sleep now.

Unfortunately it does happen on the current w-t tree.

The oops is the statement BUG_ON(!list_empty(&work->entry)); at
kernel/workqueue.c:192.

The following hack lets the computer boot with the BCM43XX device
working, but obviously the radio kill switch does not work.

Larry

Index: wireless-testing/drivers/net/wireless/b43/main.c
===================================================================
--- wireless-testing.orig/drivers/net/wireless/b43/main.c
+++ wireless-testing/drivers/net/wireless/b43/main.c
@@ -4330,7 +4330,7 @@ static int b43_op_start(struct ieee80211
        }

        /* XXX: only do if device doesn't support rfkill irq */
-       wiphy_rfkill_start_polling(hw->wiphy);
+//     wiphy_rfkill_start_polling(hw->wiphy);

  out_mutex_unlock:
        mutex_unlock(&wl->mutex);



  reply	other threads:[~2009-06-02 23:26 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-02 11:10 [RFT 0/3] driver rfkill to cfg80211 ports Johannes Berg
2009-06-02 11:10 ` [RFT 1/3] iwlwifi: port to cfg80211 rfkill Johannes Berg
2009-06-03 21:12   ` reinette chatre
2009-06-04  9:03     ` Johannes Berg
2009-06-04 16:02       ` reinette chatre
2009-06-02 11:10 ` [RFT 2/3] ath9k: " Johannes Berg
2009-06-10 13:20   ` Vasanthakumar Thiagarajan
2009-06-10 13:32     ` Vasanthakumar Thiagarajan
2009-06-10 14:38     ` Johannes Berg
2009-06-11  6:52       ` Vasanthakumar Thiagarajan
2009-06-11  9:57         ` Johannes Berg
2009-06-11  9:59           ` Vasanthakumar Thiagarajan
2009-06-11 10:10             ` Johannes Berg
2009-06-11 10:39               ` Vasanthakumar Thiagarajan
2009-06-11 10:40                 ` Vasanthakumar Thiagarajan
2009-06-02 11:10 ` [RFT 3/3] b43/legacy: " Johannes Berg
2009-06-02 14:41   ` Michael Buesch
2009-06-02 20:04     ` Johannes Berg
2009-06-02 20:08       ` Michael Buesch
2009-06-02 20:11         ` Johannes Berg
2009-06-02 20:59           ` Larry Finger
2009-06-02 21:01             ` Johannes Berg
2009-06-02 23:26               ` Larry Finger [this message]
2009-06-03  7:52             ` 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=4A25B53C.3040101@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --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 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).