Here have 4 patches, from first to third patches fixed bko#32862, bko#34142,
the 3 patches will check negative number before set initial devices state, make
sure 3G device exist before generate 3G rfkill and allow 64-bits return buffer
from 2 old wmi methods.
And, the fourth patch improve to set communication device state by evaluate new
WMID_GUID3 method, it's good to avoid potential problem if we still use old wmi
method on new Acer machines.
Changed after last posted:
+ Add negative number check in commandline_init() before set initial state.
bko#32862
+ Add check 3G device exist flag in WMID_set_capabilities(). bko#32862
+ Allow u64 result buffer in WMI_execute_u32(). bko#34142
+ Add wmid3_set_device_status() then access it in set_block.
Next step for acer-wmi:
+ Dig more old wmi event in DSDT, try to remove devices state polling on more
machines.
+ Already found some old wmi event, can be used by sync devices state.
+ Clear up acer-wmi driver base on different wmi interface on different time
frame.
Lee, Chun-Yi (4):
acer-wmi: does not allow negative number set to initial device state
acer-wmi: check the existence of internal 3G device when set
capability
acer-wmi: allow 64-bits return buffer from WMI methods
acer-wmi: support to set communication device state by new wmid
method
drivers/platform/x86/acer-wmi.c | 131 ++++++++++++++++++++++++++++++++++++---
1 files changed, 123 insertions(+), 8 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe platform-driver-x86"
in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
