linux-kernel - Re: [PATCH] input: A few new KEY

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <d120d5000609200622g333f2767y27e529d81333e7b7@mail.gmail.com>
Date:	Wed, 20 Sep 2006 09:22:39 -0400
From:	"Dmitry Torokhov" <dmitry.torokhov@...il.com>
To:	"Lennart Poettering" <mzxreary@...inter.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] input: A few new KEY_xxx definitions

On 8/8/06, Lennart Poettering <mzxreary@...inter.de> wrote:
> On Mon, 07.08.06 22:19, Dmitry Torokhov (dtor@...ightbb.com) wrote:
>
> > > KEY_POWERPLUG, KEY_POWERUNPLUG:
> > >
> > >     Some laptops generate a fake key event when the power cord is
> > >     plugged or unplugged. (Notably MSI laptops, such as S270)
> > >
> >
> > How do these events get delivered? Are you saying that atkbd reports
> > key presses when pulling out AC cord?
>
> Yes, exactly.
>

Lennart,

I applied part of the patch defining KEY_BLUETOOTH and KEY_WLAN, but I
did not apply KEY_POWER[UN]PLUG. I feel that these should not be
defined as KEY_* events but (if we decide that they should be reported
through input layer) as EV_PWR events.

-- 
Dmitry
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/