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. > I won't go on the rfkill-allocate/-free stuff, messing with that API means > you need to fix a lot of other people's drivers. But you have the > rfkill-hw-state-changed now, it is called rfkill_force_state(). The only > crap is that it cannot be called from atomic contexts. Yeah well. I didn't know. I lost interest in rfkill pretty much when it stopped blowing up (until it started again when somebody merged a patch recently). -- Greetings Michael. -- 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
