This is how I view the requirements/state of rfkill system. Not trying
to come with any design yet or mapping it to what we currently have in
rfkill. Just clearing the table for myself and maybe others.
1. radio state is inclusive disjunction or conjunction of all rfkill
switches (depends on what 0,1 means)
* user space and kernel components (e.g. mac80211) must be notified
about change in radio state
2. rfkill switches types
a. sw - can be switched by software means
b. hw - must be manually toggled..
c. devices switch - switch has direct connection to device (hw switches only)
device provides the input to the radio state
c. input switch - device is requested to change radio state (hw and
sw switches)
3. state of each rfkill switch has to be visible to user space, also
sw and hw attributes of switch must be known to user space.
4. switch state must be preserved across reboot and suspend/resume,
hw switch of course might be changed even when computer is powered off
5. There must be at least one sw input switch.
Tomas
--
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
