On Tue, Oct 16, 2007 at 12:11:53PM -0200, Henrique de Moraes Holschuh wrote:
> On Tue, 16 Oct 2007, Matthew Garrett wrote:
> > are sent via the keyboard controller, such as the wireless and touchpad
> > disable keys on my HP. There are Dells that do the same for brightness
>
> It is not clear to me if they are notifications or not. Does the firmware
> act on the keys by itself? If it does, then they are notifications. If it
> does not, then they are regular hot keys and there is no controversy whether
> they belong on the input layer or not (they do).
Yes, the firmware acts upon it.
> 2. I am against sending notification events through input **that look
> exactly the same as regular events**. That is not a wise design choice IMO,
> it is a very dirty hack.
Userspace is going to have to deal with this case anyway. Some vendors
simply don't let us distinguish.
> 3. We have a backlight class, a LED class, a rf-kill class and ALSA mixers.
> Is there a real reason to pester Dmitry about the issue, if we can use these
> alternate paths (that are indeed more generic and more suited for the job)?
It's not always going to be possible to tie notifications into a class
device - in the Dell case, for instance, interacting with the backlight
requires you to use a 200Kb library so has to be done in userspace.
--
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/
[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]
