On Thu, Nov 25, 2010 at 8:12 AM, Nikolai Kondrashov <spbnick@xxxxxxxxx> wrote: > On 11/25/2010 05:05 PM, Henrik Rydberg wrote: >> >> __u32 phys_abs_width; /* physical width of surface (mm) >> */ >> __u32 phys_abs_height; /* physical height of surface (mm) >> */ > > This is better and is already covered by input_absinfo. > You could calculate it with (maximum - minimum) / resolution. On this topic. I'd like to start reporting resolution for a few wacom devices. When I looked at input_absinfo.resolution, I see only synaptics.c is using it right now and it is defined using units/mm. Currently, this makes it up to xf86-input-synaptics were X is fed this value after converting to units/meter. Thats my intended usage as well. I'm more used to values in inches (lpi) or at least something higher then mm. If I converted my lpi to mm for resolution I'd lose some accuracy. We could solve that a few ways. Provide units in input_absinfo, convert to units/inch, units/cm or even units/meter, or define physical size in mm. Any preferences? Chris -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
