Re: [RFC] [PATCH] Make ACPI button driver an input device

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Matthew Garrett wrote:
On Thu, Apr 20, 2006 at 01:45:27PM +0800, Yu, Luming wrote:

Do you plan to port the whole acpi event interface into input layer?
If so,  keycode is NOT a right way.

Not really, though it would be one possibility. However, the input layer doesn't really provide the flexibility needed for certain events. I'm not sure what the right answer is for other events, but I'm pretty sure the button driver maps onto the input layer sensibly.

Could it be more sensible to use kevent and dbus for sending all events from ACPI?
-
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

[Index of Archives]     [Linux IBM ACPI]     [Linux Power Management]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux