mirror of
https://github.com/adulau/aha.git
synced 2025-01-04 23:23:18 +00:00
fbc97e4c5c
When an rfkill device is registered, the rfkill core will change its state to the system default. So we need to prepare for state changes *before* we register it. That means installing the eeepc-specific ACPI callback which handles the hotplug of the wireless network adaptor. This problem doesn't occur during normal operation. You have to 1) Boot with wireless enabled. eeepc-laptop should load automatically. 2) modprobe -r eeepc-laptop 3) modprobe eeepc-laptop On boot, the default rfkill state will be set to enabled. With the current core code, step 2) will disable the wireless. Therefore in step 3), the wireless will change state during registration, from disabled to enabled. But without this fix, the PCI device for the wireless adaptor will not appear. Signed-off-by: Alan Jenkins <alan-jenkins@tuffmail.co.uk> Acked-by: Matthew Garrett <mjg@redhat.com> Signed-off-by: Corentin Chary <corentincj@iksaif.net> Signed-off-by: Len Brown <len.brown@intel.com> |
||
|---|---|---|
| .. | ||
| acer-wmi.c | ||
| asus-laptop.c | ||
| asus_acpi.c | ||
| compal-laptop.c | ||
| dell-laptop.c | ||
| dell-wmi.c | ||
| eeepc-laptop.c | ||
| fujitsu-laptop.c | ||
| hp-wmi.c | ||
| intel_menlow.c | ||
| Kconfig | ||
| Makefile | ||
| msi-laptop.c | ||
| panasonic-laptop.c | ||
| sony-laptop.c | ||
| tc1100-wmi.c | ||
| thinkpad_acpi.c | ||
| toshiba_acpi.c | ||
| wmi.c | ||