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

On Thu, Apr 20, 2006 at 07:35:53PM +0400, Alexey Starikovskiy wrote:

> Could it be more sensible to use kevent and dbus for sending all events 
> from ACPI?

For most of the events, probably. I'm less convinced by the button 
driver - sleep and power buttons can also generate keycodes rather than 
ACPI events, and so getting the button driver to behave like an input 
device adds consistency.

-- 
Matthew Garrett | [email protected]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [RFC] [PATCH] Make ACPI button driver an input device
    • From: Alexey Starikovskiy <[email protected]>

• References:
  • RE: [RFC] [PATCH] Make ACPI button driver an input device
    • From: "Yu, Luming" <[email protected]>
  • Re: [RFC] [PATCH] Make ACPI button driver an input device
    • From: Matthew Garrett <[email protected]>
  • Re: [RFC] [PATCH] Make ACPI button driver an input device
    • From: Alexey Starikovskiy <[email protected]>

• Prev by Date: Re: new Areca driver in 2.6.16-rc6-mm2 appears to be broken
• Next by Date: Re: [RFC][PATCH 0/11] security: AppArmor - Overview
• Previous by thread: Re: [RFC] [PATCH] Make ACPI button driver an input device
• Next by thread: Re: [RFC] [PATCH] Make ACPI button driver an input device
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]