public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Henrik Persson <root@fulhack.info>
To: unlisted-recipients:; (no To-header on input)
Cc: dtor@mail.ru, linux-kernel@vger.kernel.org
Subject: Re: Touchpad "tapping" changes in 2.6.11?
Date: Mon, 07 Mar 2005 17:10:27 +0100	[thread overview]
Message-ID: <422C7CF3.9080609@fulhack.info> (raw)
In-Reply-To: <d120d500050307055522415fb3@mail.gmail.com>

Dmitry Torokhov wrote:
> On Mon, 07 Mar 2005 14:14:02 +0100, Henrik Persson <root@fulhack.info> wrote:
> 
>>Hi there.
>>
>>I noticed that the ALPS driver was added to 2.6.11, a thing that alot of
>>people probably like, but since my touchpad (Acer Aspire 1300XV) worked
>>perfectly before (like, 2.6.10) and now the ALPS driver disables
>>'hardware tapping', wich makes it hard to tap. I commented out the
>>disable-tapping bits in alps.c and now it's working like a charm again.
>>
> 
> 
> Hi,
> 
> Could you please try 2.6.11-mm1. It has bunch of Peter Osterlund's
> patches that shoudl improve the situation with tapping.

Well, -mm1 didn't quite agree with my savage gfx drivers. But I'm 
booting with psmouse.proto=exps now, and it's working the way I'm used 
to now.

The Aspire 1300-series is quite different from the 1350 ones.. The 
touchpad on the 1300 will work like a charm without the synaptics driver 
(but no fancy stuff is supported, I guess). Before you could boot and be 
happy without the synaptics driver, now you probably have to install the 
synaptics driver to be happy.. Maybe that's not so good. :)

Could this touchpad use the "exps" proto as default and then you could 
reconfigure if you want to use the ALPS driver..?

-- 
Henrik Persson

  reply	other threads:[~2005-03-07 16:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-07 13:14 Touchpad "tapping" changes in 2.6.11? Henrik Persson
2005-03-07 13:55 ` Dmitry Torokhov
2005-03-07 16:10   ` Henrik Persson [this message]
2005-03-07 16:36     ` Dmitry Torokhov
2005-03-07 21:29       ` Peter Osterlund
2005-03-07 21:36         ` Dmitry Torokhov

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=422C7CF3.9080609@fulhack.info \
    --to=root@fulhack.info \
    --cc=dtor@mail.ru \
    --cc=linux-kernel@vger.kernel.org \
    /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