On 19/09/11(Mon) 09:46, Martin Pieuchot wrote:
> On 15/09/11(Thu) 00:10, Alexandr Shadchin wrote:
> > [...]
> >
> > Using { 0x7326, ALPS_UNSUPPORTED } is not best idea.
> >
> > Instead
> > if (alps->model & ALPS_UNSUPPORTED)
> > use
> > if (alps->model == 0)
> > or even better
> > #d
On 15/09/11(Thu) 00:10, Alexandr Shadchin wrote:
> [...]
>
> Using { 0x7326, ALPS_UNSUPPORTED } is not best idea.
>
> Instead
> if (alps->model & ALPS_UNSUPPORTED)
> use
> if (alps->model == 0)
> or even better
> #define ALPS_UNSUPPORTED 0
> ...
> if (alps->model ==
On Tue, Sep 06, 2011 at 02:25:47PM +0200, Martin Pieuchot wrote:
> On 04/09/11(Sun) 21:36, Martin Pieuchot wrote:
> > The diff below adds support for ALPS touchpads to the pms(4) driver.
> >
> > I'm looking for testers with or without ALPS hardware, especially if you
On 04/09/11(Sun) 21:36, Martin Pieuchot wrote:
> The diff below adds support for ALPS touchpads to the pms(4) driver.
>
> I'm looking for testers with or without ALPS hardware, especially if you
> have a touchpad, to be sure it doesn't break anything.
>
> Currently,
The diff below adds support for ALPS touchpads to the pms(4) driver.
I'm looking for testers with or without ALPS hardware, especially if you
have a touchpad, to be sure it doesn't break anything.
Currently, ALPS DualPoint are untested and support for special buttons
(back, forwar
