[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d120d5000611061448p73bcfec5xb91bb4f454312eb9@mail.gmail.com>
Date: Mon, 6 Nov 2006 17:48:20 -0500
From: "Dmitry Torokhov" <dtor@...ightbb.com>
To: "Németh Márton" <nm127@...email.hu>
Cc: linux-input@...ey.karlin.mff.cuni.cz, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] input: map BTN_FORWARD to button 2 in mousedev
On 11/5/06, Németh Márton <nm127@...email.hu> wrote:
> From: Márton Németh <nm127@...email.hu>
>
> In mousedev the BTN_LEFT and BTN_FORWARD were mapped to mouse button 0, causing
> that the user space program cannot distinguish between them through /dev/input/mice.
> The BTN_FORWARD is currently used in the synaptics.c, logips2pp.c and in alps.c. All
> mice have BTN_LEFT, but not all have BTN_MIDDLE (e.g. Clevo D410J laptop). Mapping
> BTN_FORWARD to mouse button 2 makes the BTN_FORWARD button useful on the mentioned
> laptop.
>
I'd rather not touch mappings in legacy mousedev driver. I believe
both synaptics and evdev X drivers will correctly recognize
BTN_FORWARD, is there any reason you are not using them?
--
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/
Powered by blists - more mailing lists