r more fingers having non-zero f->origin.
Signed-off-by: Matt Whitlock
---
What follows is sample (abridged) output from evtest and xev when the errant
behavior is triggered by beginning a two-finger scrolling gesture (placing the
right finger on the touchpad slightly before the left fing
On Wednesday, 3 June 2015, at 2:24 pm, Henrik Rydberg wrote:
> > This patch changes the report_synaptics_data() function so that it reports
> > the highest touch_major and highest tool_major of any touching finger as
> > ABS_PRESSURE and ABS_TOOL_WIDTH, respectively.
>
> I appreciate the problem,
input_mt_report_pointer_emulation() rescale
values from each MT axis range to the respective emulated axis range to
allow touchpad drivers to redefine the emulated axis ranges after calling
input_mt_init_slots(). (The X and Y axes presently are not rescaled.)
Signed-off-by: Matt Whitlock
---
drivers
the
emulation code to synthesize ABS_PRESSURE.
Signed-off-by: Matt Whitlock
---
== Test case #1: Single-finger touch ==
Old behavior:
Event: time 1433421663.308600, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID),
value 0
Event: time 1433421663.308600, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR),
va
It's been four weeks, and I haven't heard back on this patch. I believe I've
implemented what was requested. Is there a problem with it?
On Monday, 8 June 2015, at 9:07 pm, Matt Whitlock wrote:
> Now that input_mt_report_pointer_emulation() can synthesize ABS
On Monday, 6 July 2015, at 9:11 pm, Henrik Rydberg wrote:
> > It's been four weeks, and I haven't heard back on this patch. I believe I've
> > implemented what was requested. Is there a problem with it?
>
> I thought you did get response on this patch set, concerning the fabrication
> of
> force
On Monday, 6 July 2015, at 9:44 pm, Henrik Rydberg wrote:
> >> I think your patch is a good reduction, all in accord with what we talked
> >> about,
> >> but I have doubts that it will not create regressions. From what I have
> >> seen so
> >> far, patch-wise, the best solution is to leave the co
