public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Miguelanxo Otero Salgueiro <miguelanxo@telefonica.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.11: touchpad unresponsive
Date: Wed, 2 Mar 2005 17:08:35 -0500	[thread overview]
Message-ID: <d120d50005030214086b6d568e@mail.gmail.com> (raw)
In-Reply-To: <42260B1D.3070304@telefonica.net>

On Wed, 02 Mar 2005 19:51:09 +0100, Miguelanxo Otero Salgueiro
<miguelanxo@telefonica.net> wrote:
> Dmitry Torokhov wrote:
> 
> >On Wed, 02 Mar 2005 16:55:59 +0100, MIGUELANXO@telefonica.net
> ><MIGUELANXO@telefonica.net> wrote:
> >
> >
> >>I just compiled 2.6.11 from 2.6.10 config using 'make oldconfig',
> >>activate new options to default values (i.e. set "main kernel lock
> >>preemtive" to YES).
> >>
> >>Booting X in new kernel makes my touchpad very unresponsive. I can't
> >>click any longer in the touchpad area, and the touchpad doesn't response
> >>when moving in small increments, so the whole experience is quite bad.
> >>
> >>
> >>
> >
> >If it is identified as an ALPS touchpad you can try installing Peter
> >Osterlund's Synaptics X driver:
> >
> >           http://web.telia.com/~u89404340/touchpad/
> >
> >Alternatively you can restore 2.6.10 behavior with psmouse.proto=exps
> >boot option (if psmouse is a module add "options psmouse proto=exps"
> >to your /etc/modprobe.conf).
> >
> >
> >
> Yes, it's an ALPS touchpad.
> 
> Ok, I compiled latest synaptics driver (synaptics-0.14.0) under the
> following conditions
>    - Enabled CONFIG_MOUSE_PS2 (already enabled)
>    - Enabled CONFIG_INPUT_EVDEV (this one on purpose)
> 
> I read README.alps so I tried patching the kernel with alps.patch as
> suggested. Looks like it didn't work because patch refused to patch
> already patched files. I gave a look at the patch and the kernel code,
> and they seem to be incompatible (maybe you need to release a newe patch).
> 
> So I proceded without the patched kernel, installing the synaptics
> driver using INSTALL and README.alps settings.
> 
> With plain INSTALL settings (no ALPS), the touchpad seemed responsible,
> but kind of slow. Simple or double click didn't work.
> 
> With README.alps settings, touchpad feels a lot like in 2.6.10, thought
> the "acceleration" seems to be non-linear.
> Simple click worked BUT double-click didn't work. Horizontal/Vertical
> scroll and Click-n-Drag worked too, so I'm almost there.
> 

There are more paches done by Peter in the input queue that should
improve ALPS tapping behaviour. Maybe Peter will add them to his
driver for time being.

> 
> By the way, I'm using a Toshiba laptop (Toshiba Satellite A10), maybe
> you would like to add that to your supported hardware list.
> 

Please let Peter (petero2@telia.com) know as he maintains the driver/site.

-- 
Dmitry

  reply	other threads:[~2005-03-02 22:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-02 15:55 2.6.11: touchpad unresponsive MIGUELANXO
2005-03-02 17:12 ` Dmitry Torokhov
2005-03-02 18:51   ` Miguelanxo Otero Salgueiro
2005-03-02 22:08     ` Dmitry Torokhov [this message]
     [not found] ` <mailman.1109784242.17244.linux-kernel2news@redhat.com>
2005-03-03  0:52   ` Pete Zaitcev

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=d120d50005030214086b6d568e@mail.gmail.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miguelanxo@telefonica.net \
    /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