Messages in this thread | | | Date | Wed, 13 Aug 2008 23:58:40 -0700 | From | Philip Langdale <> | Subject | Re: [PATCH 1/1] toshiba_acpi: Add support for bluetooth toggling through rfkill (v2) |
| |
Henrique de Moraes Holschuh wrote: > > Looks like either rfkill-input is inactive, or something is binding to the > toshiba_acpi input device and setting it to exclusive mode (X evdev does > this).
Almost. Turns out there were two problems:
1) I was setting SW_RFKILL_ALL as a keybit instead of an swbit - so no events reported. Whoops. :-)
2) Maybe this shouldn't surprise me, but the expected switch semantics are that '1' means radios are on and 0 means they are killed - I thought it was the other way round.
Now, when I release the kill switch, rfkill-input does indeed turn the radio on. Great. The remaining problem is that rfkill-input is setting it to soft-blocked when the switch is registered. I'm not sure why it's deciding to do that. Anyway, I'm almost there. Thanks.
--phil
| |