On Fri, 16 Jan 2009, Werner Almesberger wrote: > But then we're a few sysfs interfaces short. Is there any specific > reason why there is a control for setting the global default state > (/sys/module/rfkill/parameters) but there are no controls for: > > - setting the default state by type, > - setting the current state by type, and > - setting the current state ? Yeah, they are sitting in my queue, but I dislike them so much I always find a reason not to post them and do something else in thinkpad-acpi, instead... I will see if I can bring myself to post them during the weekend. Anyway, right now access to those is only possible through rfkill-input and input-events (for those types that HAVE an input event related to them...). > > But there are other questions: why? You *NEED* somewhere to attach the > > rfkill kobjects to, and that somewhere can't very well be a device that is > > getting hotunplugged, as it will disappear. So, you will need something > > like the platform device you used, anyway... > > In my scenario, a driver calling rfkill_detach would say "I might be > back". > > But I think I like the idea of making the per-type controls more > powerful. Then, it is best that we stick with what already is there (the per-type control). -- "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
