public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Osterlund <petero2@telia.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, Vojtech Pavlik <vojtech@suse.cz>,
	hgfelger@hgfelger.de
Subject: Re: 2.6.0-test3-mm2
Date: 17 Aug 2003 22:37:50 +0200	[thread overview]
Message-ID: <m2n0e858bl.fsf@p4.localdomain> (raw)
In-Reply-To: <20030813013156.49200358.akpm@osdl.org>

(I'm resending this because I previously had sendmail configuration
problems. Sorry if you receive this message twice.)

Andrew Morton <akpm@osdl.org> writes:

> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test3/2.6.0-test3-mm2/

Here is a fix for synaptics touchpads with "multi buttons". The patch
comes from Hartwig Felger, who wrote the original multi button support
patch (p00003_synaptics-multi-button.patch). The same bug fix has been
included in the XFree86 driver for a few weeks, and seems to work
fine. (That part of the X driver is only used for 2.4 kernels.)


 linux-petero/drivers/input/mouse/synaptics.c |    3 ++-
 1 files changed, 2 insertions(+), 1 deletion(-)

diff -puN drivers/input/mouse/synaptics.c~syn-multi-btn-fix drivers/input/mouse/synaptics.c
--- linux/drivers/input/mouse/synaptics.c~syn-multi-btn-fix	2003-08-13 22:48:49.000000000 +0200
+++ linux-petero/drivers/input/mouse/synaptics.c	2003-08-13 22:48:49.000000000 +0200
@@ -433,7 +433,8 @@ static void synaptics_parse_hw_state(uns
 			if (hw->right)
 				hw->down = !hw->down;
 		}
-		if (buf[3] == 0xC2 && SYN_CAP_MULTI_BUTTON_NO(priv->ext_cap)) {
+		if (SYN_CAP_MULTI_BUTTON_NO(priv->ext_cap) &&
+		    ((buf[3] & 2) ? !hw->right : hw->right)) {
 			switch (SYN_CAP_MULTI_BUTTON_NO(priv->ext_cap) & ~0x01) {
 			default:
 				; /* we did comment while initialising... */

_

-- 
Peter Osterlund - petero2@telia.com
http://w1.894.telia.com/~u89404340

  parent reply	other threads:[~2003-08-17 20:38 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-13  8:31 2.6.0-test3-mm2 Andrew Morton
2003-08-13  9:11 ` How to use hugetlb for the text of a program ? dada1
2003-08-13  9:26   ` Andrew Morton
2003-08-13 12:42     ` dada1
2003-08-13  9:22 ` 2.6.0-test3-mm2 hugang
2003-08-13 10:48   ` 2.6.0-test3-mm2 Andrew Morton
2003-08-13 13:02 ` 2.6.0-test3-mm2 Con Kolivas
2003-08-13 13:35   ` 2.6.0-test3-mm2 Luiz Capitulino
2003-08-13 13:36   ` 2.6.0-test3-mm2 Luiz Capitulino
2003-08-13 14:32   ` 2.6.0-test3-mm2 Hugh Dickins
2003-08-13 16:16     ` 2.6.0-test3-mm2 Martin J. Bligh
2003-08-13 16:18     ` 2.6.0-test3-mm2 Luiz Capitulino
2003-08-15 19:38 ` Compile problem with CONFIG_X86_CYCLONE_TIMER 2.6.0-test3-mm2 Mike Fedyk
2003-08-15 20:23   ` Mike Fedyk
2003-08-15 20:36     ` Mike Fedyk
2003-08-16 20:32       ` Dave Hansen
2003-08-27  1:08         ` Compile problem with CONFIG_X86_CYCLONE_TIMER Re: 2.6.0-test4-mm1 Mike Fedyk
2003-08-27  4:41           ` Dave Hansen
2003-08-27 16:00             ` Mike Fedyk
2003-08-27 16:15               ` Dave Hansen
2003-08-17 20:37 ` Peter Osterlund [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-08-13 13:45 2.6.0-test3-mm2 Andreas Mikkelborg
2003-08-14  2:23 ` 2.6.0-test3-mm2 G. Chris Hofmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2n0e858bl.fsf@p4.localdomain \
    --to=petero2@telia.com \
    --cc=akpm@osdl.org \
    --cc=hgfelger@hgfelger.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@suse.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox