Hello, I saw dell-wireless driver on platform-driver-x86 mailinglist [1] which using DELLABCE acpi device and I do not like some parts in this driver. First is that this driver export rfkill event as keypress which is also reported to userspace by keyboard controller. So then userspace receive two rfkill keypresses. Second is that DELLABCE acpi device can also control "soft" rfkill status and this driver does not enable it because it use input class instead rfkill. Anyway I have unfinished my version of DELLABCE acpi driver which will use rfkill interface and plus allow to use hw switch events in dell-laptop.ko driver. Currently dell-laptop.ko driver is using i8042 hook function for detecting hw switch key press event. It is needed to detect if rfkill state was changed or not. My prepared patches for dell-laptop.ko allows to use acpi event from DELLABCE driver, so i8042 hook function can be dropped. Really it is not good idea to pass every PS/2 data from both keyboard, touchpad and trackpoint to dell-laptop driver and if there is alternative (DELLABCE) it is better to use it. But now I would like to hear what do you think about it. Because only one kernel driver can attach to DELLABCE acpi device, I cannot use new dell-wireless driver. And I think only one driver can hit mainline kernel. [1] - http://thread.gmane.org/gmane.linux.drivers.platform.x86.devel/6036 -- Pali Rohár pali.rohar@xxxxxxxxx
Attachment:
signature.asc
Description: This is a digitally signed message part.
