Re: Handling special keys in platform drivers

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

 



On Fri, Jan 13, 2012 at 11:42 PM, Matthew Garrett <mjg@xxxxxxxxxx> wrote:
> On Mon, Jan 09, 2012 at 07:24:14AM +0100, Corentin Chary wrote:
>
>> The real problem is that for keyboard backlight to work, it needs DE
>> cooperation, and only gnome as implemented that right now, and other
>> (except KDE) will probably neither have the resources to handle all
>> the possible keys correctly. And of course, who should handle the keys
>> when there is no DE running at all ?
>
> The problem with handling this in kernel is that there isn't an
> obviously correct policy. ACPI will typically only expose 16 or so
> backlight levels so the behaviour is easy enough, but (depending on how
> the hardware is wired up) i915 may expose around 20,000. Further, one
> machine may expose different backlight controls for different displays,
> and in that situation you need to know which one the input event is
> expected to correspond to.
>
> Doing backlight control properly involves a lot of policy work, and I'm
> reluctant to argue that that ought to be in the kernel.

But in the case of asus-wmi, that handle both the keys and the
keyboard_backlight, could such handling be done in the kernel ?

-- 
Corentin Chary
http://xf.iksaif.net
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Media Devel]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Linux Wireless Networking]     [Linux Omap]

  Powered by Linux