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

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

 



On Wed, Jul 18, 2007 at 05:44:19PM +0100, Richard Hughes wrote:
> 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.

I was thinking more of the ones that are just flagged as KEY_FN_F1 at 
the moment.

-- 
Matthew Garrett | mjg59@xxxxxxxxxxxxx
-
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