I refactored the previous patchset so it proposes first the hash table fix, and
the
proper hard rfkill handling (without DBus exposure change), as well as the
rfkill cascading
issue.
Then the 2 last patches propose a fix for API 1.0: if a technology is hw
rfkilled, it won't
be exposed through DBus.
Tomasz Bursztyka (5):
technology: Handle rfkill hash table in a saner way
technology: Handle rfkill hardblock relevantly
technology: Handle harblock if only all are identical for the same
rfkill type
technology: Add helpers for (un)registering a technology in dbus
technology: Do not expose a technology which is hard rfkilled
src/technology.c | 122 +++++++++++++++++++++++++++++++++++++++++--------------
1 file changed, 92 insertions(+), 30 deletions(-)
--
1.7.12
_______________________________________________
connman mailing list
[email protected]
http://lists.connman.net/listinfo/connman
