commit | 9a24553461df7036755060423f90804011612249 | [log] [tgz] |
---|---|---|
author | Eric Shienbrood <ers@chromium.org> | Wed Mar 07 14:20:39 2012 -0500 |
committer | Gerrit <chrome-bot@google.com> | Thu Mar 22 14:09:34 2012 -0700 |
tree | 3a8f7bde58a900b740af0c3f0169783bd4f336fd | |
parent | 5e628a5c722c196ad240af0ff3c717e9613d3ef5 [diff] |
Make Enable/Disable work using new callbacks for async support. Use new-style callbacks to implement the Manager EnableTechnology and DisableTechnology operations asynchronously. This allows devices to be enabled and disabled from the UI ,and for the UI to display available networks once the device is enabled. Removed the behavior whereby setting the Device.Powered property had the side effect of enabling or disabling the device. To replace this, I added new Device.Enable and Device.Disable calls for enabling and disabling individual devices. Also separated the in-memory value of the Powered property from the persisted value. Whenever a client requests that a device be enabled or disabled, the desired power state is immediately saved in the profile, but the in-memory value isn't updated until the operation completes. On startup, shill now automatically starts any devices for which the persistent Powered property is set, and does not start devices for which it is not set. BUG=chromium-os:23319,chromium-os:27814 TEST=Manual testing on device + unit tests passing. Change-Id: Id676be3fc662cfd5efb730c67687edfd16b2dc6b Reviewed-on: https://gerrit.chromium.org/gerrit/18123 Commit-Ready: Eric Shienbrood <ers@chromium.org> Reviewed-by: Eric Shienbrood <ers@chromium.org> Tested-by: Eric Shienbrood <ers@chromium.org>