On Wed, Sep 14, 2011 at 2:35 PM, Chris Bagwell <[email protected]> wrote:
> So I propose this long term definitions for ABS_DISTANCE:
>
> Protocol 5 - Any tool reporting ABS_DISTANCE is in distance from
> tablet (same as today).
> Protocol 4 - Only puck reports ABS_DISTANCE today and it can stay
> distance from out-of-proximity.
> Protocol Generic (Bamboo, Waltop, etc) - Right now, I only know PEN
> tool that reports it.  We should standardize on distance from tablet
> or a rough approximation of that.

I just looked and I could find only 1 other driver that is reporting
ABS_DISTANCE with real distance values and that happens to be
hid-wacom.c.

It looks to me that its probably inverting the value as well to
simulate distance from tablet.

                case 3: /* Mouse without wheel */
                        rw = 44 - (data[6] >> 2);
                        if (rw < 0)
                                rw = 0;
                        else if (rw > 31)
                                rw = 31;
                        input_report_abs(input, ABS_DISTANCE, rw);


The good news is that since its not reporting ABS_MISC it is
classified as Protocol Generic and aligns with above nicely.  The bad
news is that xf86-input-wacom will be confused with this driver today.
 We need to modify xf86-input-wacom to say:

  if (PROTOCOL_4)
    distance is inverted logic
  else /* protocol 5 and generic here */
    distance is not inverted logic.

Chris

------------------------------------------------------------------------------
BlackBerry&reg; DevCon Americas, Oct. 18-20, San Francisco, CA
Learn about the latest advances in developing for the 
BlackBerry&reg; mobile platform with sessions, labs & more.
See new tools and technologies. Register for BlackBerry&reg; DevCon today!
http://p.sf.net/sfu/rim-devcon-copy1 
_______________________________________________
Linuxwacom-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Reply via email to