On Mon, 01 Jun 2009, Johannes Berg wrote: > On Mon, 2009-06-01 at 12:36 -0300, Henrique de Moraes Holschuh wrote: > > > > On a related note, Johannes, would you be opposed to exporting something I > > > > could call from thinkpad-acpi to request a radio state change on a rfkill > > > > struct? This would allow me to remove some of the mess in thinkpad-acpi. > > > > > > I don't think I understand what you want? What do you mean by "request a > > > radio state change"? > > > > As in "please try to block this _specific_ radio", and "please try to > > unblock this _specific_ radio". > > > > I.e. what one would do by a write to the "state" attribute of the _old_ > > rfkill sysfs (and which would get overriden the next time someone changed > > the global state, etc). > > Ok, but where would you want that exported to? It's available > on /dev/rfkill, why would you want that for the driver, it can just call > itself, no? Yes, it "calls itself" right now... so I can certainly do that :) However, the in-driver shortcut means I give rfkill a kick and say "the soft state has changed, deal with it", instead of "please change the state" which it might deny due to EPO, etc. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- 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
