On Wed, 2009-05-27 at 10:07 +0200, John W. Linville wrote: > On Tue, May 26, 2009 at 11:55:16PM -0300, Henrique de Moraes Holschuh wrote: > > On Tue, 26 May 2009, John W. Linville wrote: > > > On Tue, May 26, 2009 at 08:19:29AM -0400, Will Keaney wrote: > > > > Johannes Berg wrote: > > > > > This patch completely rewrites the rfkill core to address > > > > > the following deficiencies: > > > > > > > > > I applied this to a fresh pull of wireless-testing this morning, and > > > > haven't had any problems from it. It looks like the soft lockup I > > > > reported earlier has been fixed. > > > > > > Cool, thanks for the report. > > > > > > I'm leaning towards merging this in time for the 2.6.31 merge > > > window...who wants to complain? :-) > > > > As long as the missing userspace control functionality (the lack of which is > > a _serious_ regression for platform drivers) is added before 2.6.31 ships, I > > have no complains. > > > > Userspace must be able to change the (soft) state using sysfs. This is > > not an optional part of rfkill :-) > > Are there any apps that actually use this feature? It seems like > that even if there are apps, they need to handle drivers that don't > support it. I'd use it NM for the "Enable Wireless" checkbox. The alternative is SIOCSIWTXPOW -> off I guess, though it would be nicer to just talk to one thing in sysfs instead of listen to one and SIWTXPOW to set. Dan -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
