On some Dell Latitudes we fail to identify presence of trackstick unless we
reset the device. The issue is quite benign as we do perform reset in
alps_init(), so the trackstick ends up working, but mouse name reported to
userspace is not accurate.
In order to fix the issue while avoiding the addit
On Wednesday 14 January 2015 23:55:53 Dmitry Torokhov wrote:
> + /*
> + * Reset the device to make sure it is fully operational:
> + * on some laptops, like certain Dell Latitudes, we may
> + * fail to properly detect presence of trackstick if device
> + * has not been reset
On Thu, Jan 15, 2015 at 09:21:34PM +0100, Pali Rohár wrote:
> On Wednesday 14 January 2015 23:55:53 Dmitry Torokhov wrote:
> > + /*
> > +* Reset the device to make sure it is fully operational:
> > +* on some laptops, like certain Dell Latitudes, we may
> > +* fail to properly detect
On Wednesday 14 January 2015 23:55:53 Dmitry Torokhov wrote:
> On some Dell Latitudes we fail to identify presence of
> trackstick unless we reset the device. The issue is quite
> benign as we do perform reset in alps_init(), so the
> trackstick ends up working, but mouse name reported to
> userspa
On Sat, Jan 17, 2015 at 11:26:50AM +0100, Pali Rohár wrote:
> On Wednesday 14 January 2015 23:55:53 Dmitry Torokhov wrote:
> > On some Dell Latitudes we fail to identify presence of
> > trackstick unless we reset the device. The issue is quite
> > benign as we do perform reset in alps_init(), so th
On Monday 02 February 2015 06:34:08 Dmitry Torokhov wrote:
> On Sat, Jan 17, 2015 at 11:26:50AM +0100, Pali Rohár wrote:
> > On Wednesday 14 January 2015 23:55:53 Dmitry Torokhov wrote:
> > > On some Dell Latitudes we fail to identify presence of
> > > trackstick unless we reset the device. The iss
