Re: [PATCH 5/7] Make the driver use MSC_SCAN and a setkeycode and getkeycode key table.

[Richard Hughes <hughsient@gmail.com>]

On Wed, 2007-07-18 at 17:25 +0100, Matthew Garrett wrote:
> This isn't an either/or situation. If you have a hal keymap then the 
> system will still work. The question is what to do in the absence of 
> hal. The kernel can either provide sane defaults (that might be wrong
> in a couple of cases) or it can provide keys that are pretty much 
> guaranteed to do nothing. I think doing our best to make things work 
> even if hal isn't there is sensible - if hal /is/ there, we've lost 
> nothing. 

The only reason we set the keys to KEY_UNKNOWN is so we still emit acpi
events (and not change the interface) if we are using an old HAL to not
break stuff like acpid and tpd.

We could just do:

* emit acpi event _and_ input event if we probably know the button
* just emit input events (for known keys) and just don't emit any acpi
events at all

Richard.