Return-path: Received: from charlotte.tuxdriver.com ([70.61.120.58]:48704 "EHLO smtp.tuxdriver.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752589AbYIQOaS (ORCPT ); Wed, 17 Sep 2008 10:30:18 -0400 Date: Wed, 17 Sep 2008 10:29:31 -0400 From: "John W. Linville" To: Michael Buesch Cc: Henrique de Moraes Holschuh , Adel Gadllah , wireless , LKML , bcm43xx-dev@lists.berlios.de, Larry Finger Subject: Re: Regression in 2.6.27-rcX caused by commit bc19d6e0b74ef03a3baf035412c95192b54dfc6f Message-ID: <20080917142931.GF5407@tuxdriver.com> (sfid-20080917_163023_117818_57A60589) References: <48CFC03A.8020708@lwfinger.net> <200809162125.18978.mb@bu3sch.de> <20080916223729.GC26035@khazad-dum.debian.net> <200809171626.28782.mb@bu3sch.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <200809171626.28782.mb@bu3sch.de> Sender: linux-wireless-owner@vger.kernel.org List-ID: On Wed, Sep 17, 2008 at 04:26:28PM +0200, Michael Buesch wrote: > On Wednesday 17 September 2008 00:37:29 Henrique de Moraes Holschuh wrote: > > On Tue, 16 Sep 2008, Michael Buesch wrote: > > > But I don't know how to tell the rfkill subsystem about the states and > > > > rfkill_force_state(). Must NOT be called from within atomic contextes, > > something I haven't got around to find a proper way of fixing, and nobody > > else seems to be on a rfkill coding frenzy right now. > > That's a showstopper for us, as we have to change the state from > within an interrupt tasklet. Workqueue? -- John W. Linville linville@tuxdriver.com