On Thu, 03 Jul 2008, Cezary Jackiewicz wrote: > Dnia 2008-07-02, o godz. 23:14:33 > Henrique de Moraes Holschuh <hmh@xxxxxxxxxx> napisa?(a): > > [...] > > That doesn't look like a new-style (i.e. what is in net-next-2.6) rfkill > > support. Could you take a look on the new (and I sure hope, vastly > > improved) Documentation/rfkill.txt in net-next-2.6, and switch the driver to > > RFKILL_STATE_UNBLOCKED, RFKILL_STATE_SOFT_BLOCKED, etc? After a quick look, > > it looks like Compal won't need RFKILL_STATE_HARD_BLOCKED (thinkpad-acpi > > does, because some thinkpads have a master wireless kill switch), but > > still... > > Compal has hardware wireless kill switch (without software it kill all radios > rf and disconnecting bluetooth from usb bus). Does he should generate > SW_RFKILL_ALL or something like this? Look at the thinkpad-acpi code. I don't know for sure if Compal's firmware/hardware acts like the thinkpad one, but if it does, you will find your answer on thinkpad-acpi since what you describe is pretty much what a thinkpad does. So, yes, usually master wireless switches like what you describe for Compal are input devices (see the new rfkill docs), and issue SW_RFKILL_ALL events. -- "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-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
