Hi!
I recently posted this to linux-kernel (with a different subject)
I had included a wrong ptch there, i think this one is ok.
As some people before I had the 'Dell trackpoint does not work' problem
after upgrading to 2.5.XX:
That was:
the trackpoint of your dell won't work until:
- hibernate and wake up the system again
- plug in an external mouse (you may remove it immediately)
it seems that dells hardware is disabling the trackpoint if you
probed for the touchpad.
A device reset after probing does help, but I've no idea how this
would affect other synaptics touchpad devices although I think
most devices will not complain about one extra reset.
Arne
diff -bruN linux-2.5.65-old/drivers/input/mouse/psmouse.c linux-2.5.65/drivers/input/mouse/psmouse.c
--- linux-2.5.65-old/drivers/input/mouse/psmouse.c 2003-03-05 04:29:03.000000000 +0100
+++ linux-2.5.65/drivers/input/mouse/psmouse.c 2003-03-26 09:11:10.000000000 +0100
@@ -345,6 +345,7 @@
thing up. */
psmouse->vendor = "Synaptics";
psmouse->name = "TouchPad";
+ psmouse_command(psmouse, param, PSMOUSE_CMD_RESET_BAT);
return PSMOUSE_PS2;
}
On Tue, Mar 25, 2003 at 08:25:47AM +0100, Arne Koewing wrote:
> Hi!
>
> I recently posted this to linux-kernel (with a different subject)
> I had included a wrong ptch there, i think this one is ok.
Do we really need RESET_BAT? Doesn't any other command help?
> As some people before I had the 'Dell trackpoint does not work' problem
> after upgrading to 2.5.XX:
> That was:
>
> the trackpoint of your dell won't work until:
> - hibernate and wake up the system again
> - plug in an external mouse (you may remove it immediately)
>
> it seems that dells hardware is disabling the trackpoint if you
> probed for the touchpad.
> A device reset after probing does help, but I've no idea how this
> would affect other synaptics touchpad devices although I think
> most devices will not complain about one extra reset.
>
>
> Arne
>
>
> diff -bruN linux-2.5.65-old/drivers/input/mouse/psmouse.c linux-2.5.65/drivers/input/mouse/psmouse.c
> --- linux-2.5.65-old/drivers/input/mouse/psmouse.c 2003-03-05 04:29:03.000000000 +0100
> +++ linux-2.5.65/drivers/input/mouse/psmouse.c 2003-03-26 09:11:10.000000000 +0100
> @@ -345,6 +345,7 @@
> thing up. */
> psmouse->vendor = "Synaptics";
> psmouse->name = "TouchPad";
> + psmouse_command(psmouse, param, PSMOUSE_CMD_RESET_BAT);
> return PSMOUSE_PS2;
> }
--
Vojtech Pavlik
SuSE Labs, SuSE CR
Vojtech Pavlik <[email protected]> writes:
> On Tue, Mar 25, 2003 at 08:25:47AM +0100, Arne Koewing wrote:
>> Hi!
>>
>> I recently posted this to linux-kernel (with a different subject)
>> I had included a wrong ptch there, i think this one is ok.
>
> Do we really need RESET_BAT? Doesn't any other command help?
>
I've used this because it is what tpconfig is using.
I've tried all I could think of
(except of Synaptics-specials that I might not know)
RESET_BAT is the only one that works...
I'll study the Synaptics TP Interfacing Guide again...
Arne
On Wed, Mar 26, 2003 at 10:22:47AM +0100, Arne Koewing wrote:
> Vojtech Pavlik <[email protected]> writes:
>
> > On Tue, Mar 25, 2003 at 08:25:47AM +0100, Arne Koewing wrote:
> >> Hi!
> >>
> >> I recently posted this to linux-kernel (with a different subject)
> >> I had included a wrong ptch there, i think this one is ok.
> >
> > Do we really need RESET_BAT? Doesn't any other command help?
> >
> I've used this because it is what tpconfig is using.
> I've tried all I could think of
> (except of Synaptics-specials that I might not know)
> RESET_BAT is the only one that works...
>
> I'll study the Synaptics TP Interfacing Guide again...
I mean - if we use RESET_BAT, I'd expect all config done before to be
lost ... maybe we want this, but won't this kill all the extra touchpad
functionality? We most likely won't be able to read absolute touchpad
values, etc. It might not be possible to use the touchpad with a
touchpoint together with touchpad extra functionality ...
--
Vojtech Pavlik
SuSE Labs, SuSE CR
Hi Arne,
On Tuesday, 25 March 2003, Arne Koewing wrote:
> I recently posted this to linux-kernel (with a different subject) I
> had included a wrong ptch there, i think this one is ok.
>
> As some people before I had the 'Dell trackpoint does not work'
> problem after upgrading to 2.5.XX:
> That was:
>
> the trackpoint of your dell won't work until:
> - hibernate and wake up the system again
> - plug in an external mouse (you may remove it immediately)
>
> it seems that dells hardware is disabling the trackpoint if you probed
> for the touchpad. A device reset after probing does help, but I've no
> idea how this would affect other synaptics touchpad devices although I
> think most devices will not complain about one extra reset.
Thanks for making this patch available! It works really great for me on
my Dell Latitude C400. After a fresh boot of the Linux kernel both the
trackpoint and the touchpad now both work.
Thanks,
Niels
Hi Arne,
On Wednesday, 26 March 2003, Niels den Otter wrote:
> On Tuesday, 25 March 2003, Arne Koewing wrote:
> > I recently posted this to linux-kernel (with a different subject) I
> > had included a wrong ptch there, i think this one is ok.
> >
> > As some people before I had the 'Dell trackpoint does not work'
> > problem after upgrading to 2.5.XX:
> > That was:
> >
> > the trackpoint of your dell won't work until:
> > - hibernate and wake up the system again
> > - plug in an external mouse (you may remove it immediately)
> >
> > it seems that dells hardware is disabling the trackpoint if you probed
> > for the touchpad. A device reset after probing does help, but I've no
> > idea how this would affect other synaptics touchpad devices although I
> > think most devices will not complain about one extra reset.
>
> Thanks for making this patch available! It works really great for me
> on my Dell Latitude C400. After a fresh boot of the Linux kernel both
> the trackpoint and the touchpad now both work.
I found that your patch has not found it's way to the 2.5 tree yet. Do
you know the status of this? I still patch all my new kernels with your
patch.
Kind regards,
Niels