Hi, i know, what it is not a proper solution, but it work for me at the moment. Pleas tell me, if i can help. I think it is better not to let switch the rfkill on button in the driver itself. It is more flexible when button send only event and userspace-tool handle it. Userspace-tool can choose the right rfkill (or may be multiple rfkills) (it can be runned, after wlan-driver was loaded). As i can see, other platform-drivers provide only rfkill device and do not bind it to keys. Regards, Andrej Corentin Chary writes:
Hi, Making hotplug optional won't fix the problem, because this mean you need to ship a specific module for each Eeepc. We need a more generic solution, and we need to implement a driver for the new wmi interface. I'll start to work on that as soon as I can get the hardware... Thanks, -- Corentin Chary http://xf.iksaif.net
-- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
