From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Dmitry Torokhov" Subject: Re: [RFC] psmouse: add support for 4th button using the 4th bit Date: Tue, 3 Apr 2007 11:05:13 -0400 Message-ID: References: <20070402204810.GC14838@redhat.com> <20070403144243.GE14838@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20070403144243.GE14838@redhat.com> Content-Disposition: inline Sender: owner-linux-input@atrey.karlin.mff.cuni.cz List-Help: List-Owner: List-Post: List-Unsubscribe: To: Aristeu Rozanski Cc: linux-input@atrey.karlin.mff.cuni.cz List-Id: linux-input@vger.kernel.org On 4/3/07, Aristeu Rozanski wrote: > Hi Dmitry, > > Do you know if there is a way (like a magic knock) that would allow to > > identify Cortron's devices? I don't like the module option too much, > > given the fact that it will affect all devices. Maybe we should define > > Cortron protocol instead and activate it manually via sysfs? > there's no way to detect this Cortron device, it was my first try. That's unfortunate. BTW, is this your observation or did you ask Cortron and this was their response? > Hm, the > new protocol/sysfs idea seems to be much better, I didn't know that was > possible. I'll rework the patch and resubmit. You'd need to add something like this to psmouse_protocols[]: { .type = PSMOUSE_CORTRON, .name = "CortronPS/2", .alias = "cortps", .detect = cortron_detect, }, and then model cortron_detect after ps2bare_detect (where you don't actually detect anything, just force protocol). -- Dmitry