On Fri, Apr 25, 2008 at 09:10:26PM +0200, Sebastian Siewior wrote: > * Dmitry Torokhov | 2008-04-25 14:56:24 [-0400]: > > >> The code: > >> | /* Post events > >> | * BTN_TOUCH has to be first as mousedev relies on it when doing > >> | * absolute -> relative conversion > >> | */ > >> | if (hw.z > 30) input_report_key(dev, BTN_TOUCH, 1); > >> | if (hw.z < 25) input_report_key(dev, BTN_TOUCH, 0); > >> > >> Nothing happens if z is lets say 27. > > > >Right, you want to have hysteresis to avoid jitter. > Aha, good to know. > > >> How do I do fine tunning with > >> evdev? This looks like nothing has any influence on 30 & 25. > > > >Synaptics native driver ignores BTN_TOUCH and goes strictly by > >ABS_PRESSURE. The same would be valid for evdev/tslib combo on > >UCB1400. BTN_TOUCH is for mousedev (and similar dumb consumers) > >benefit only. > Oh okey. Now I have the picture. I was going to try mice interface with > qtopia once everything is working (what could take few days). It looked > on the first shot like I could use the bare mice interface without tslib > once I get calibration working (right now I thing that it could be > easily solved with proper max/min x & y values). If this is not is not > working than I would have get tslib working what would make the > BTN_TOUCH thing useless. Yeah, mousedev may work to a degree but if you want precise operation of your toucscreen interfacing through tslib is way to go. So do you think we should still apply your patch? -- Dmitry -- 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