Hi,
[...]
> > Hm. Why not touching pixel (0,0) on the touch is always pixel (0,0)
> > on the screen and touching pixel (639,479) is always (639,479)?
>
> Important is that there is no 1:1 mapping between input evdev device
> and drm/fb output device. These are two independent devices. There is
>
Hi,
[...]
> > Hm. Why not touching pixel (0,0) on the touch is always pixel (0,0)
> > on the screen and touching pixel (639,479) is always (639,479)?
>
> Important is that there is no 1:1 mapping between input evdev device
> and drm/fb output device. These are two independent devices. There is
>
Hi!
> > They are "pixels" or the touch controller, i.e. native unites in which
> > device reports coordinates, as opposed to points per inch, or
> > millimeters, or whatever. These "pixels" do not have to have 1:1
> > relation to the LCD pixels; in fact they rarely do.
>
> I wouldn't call this
Hi!
> > They are "pixels" or the touch controller, i.e. native unites in which
> > device reports coordinates, as opposed to points per inch, or
> > millimeters, or whatever. These "pixels" do not have to have 1:1
> > relation to the LCD pixels; in fact they rarely do.
>
> I wouldn't call this
On Tuesday 21 February 2017 07:36:17 H. Nikolaus Schaller wrote:
> Hi,
>
> > Am 20.02.2017 um 22:50 schrieb Dmitry Torokhov :
> >
> > On Mon, Feb 20, 2017 at 1:27 PM, H. Nikolaus Schaller
> > wrote:
> >>
> >>> Am 20.02.2017 um 22:08 schrieb Pali
On Tuesday 21 February 2017 07:36:17 H. Nikolaus Schaller wrote:
> Hi,
>
> > Am 20.02.2017 um 22:50 schrieb Dmitry Torokhov :
> >
> > On Mon, Feb 20, 2017 at 1:27 PM, H. Nikolaus Schaller
> > wrote:
> >>
> >>> Am 20.02.2017 um 22:08 schrieb Pali Rohár :
> >>>
> >>> On Monday 20 February 2017
Hi all,
On Tue, Feb 21, 2017 at 9:47 AM, Pali Rohár wrote:
> But it really make sense to set input_abs_set_res() from DT.
And _not_ add the 1 or two lines of code that checks some DT variable,
and then fixes _everybody's_ userland?
That means those lines of code need to
Hi all,
On Tue, Feb 21, 2017 at 9:47 AM, Pali Rohár wrote:
> But it really make sense to set input_abs_set_res() from DT.
And _not_ add the 1 or two lines of code that checks some DT variable,
and then fixes _everybody's_ userland?
That means those lines of code need to go into _every_
On Tuesday 21 February 2017 07:42:17 H. Nikolaus Schaller wrote:
> Hi Pali,
>
> > Am 20.02.2017 um 22:54 schrieb Pali Rohár :
> >
> > On Monday 20 February 2017 22:24:31 H. Nikolaus Schaller wrote:
> >> Hi Pali,
> >>
> >>> Am 20.02.2017 um 22:07 schrieb Pali Rohár
On Tuesday 21 February 2017 07:42:17 H. Nikolaus Schaller wrote:
> Hi Pali,
>
> > Am 20.02.2017 um 22:54 schrieb Pali Rohár :
> >
> > On Monday 20 February 2017 22:24:31 H. Nikolaus Schaller wrote:
> >> Hi Pali,
> >>
> >>> Am 20.02.2017 um 22:07 schrieb Pali Rohár :
> >>>
> >>> On Monday 20
Hi!
On Tuesday 21 February 2017 08:14:09 H. Nikolaus Schaller wrote:
> Hi Pali,
>
> > Am 20.02.2017 um 20:42 schrieb Pali Rohár :
> >
> > Hi Nikolaus!
> >
> > On Monday 20 February 2017 17:50:04 H. Nikolaus Schaller wrote:
> >> Hi Dmitry,
> >>
> >>> Input driver may set
Hi!
On Tuesday 21 February 2017 08:14:09 H. Nikolaus Schaller wrote:
> Hi Pali,
>
> > Am 20.02.2017 um 20:42 schrieb Pali Rohár :
> >
> > Hi Nikolaus!
> >
> > On Monday 20 February 2017 17:50:04 H. Nikolaus Schaller wrote:
> >> Hi Dmitry,
> >>
> >>> Input driver may set resolution for given
Hi Petr and all,
> Am 20.02.2017 um 23:26 schrieb Petr Cvek :
>
> Hi
>
> Dne 20.2.2017 v 17:50 H. Nikolaus Schaller napsal(a):
>> Hi Pavel,
>>
>>> Am 19.02.2017 um 23:19 schrieb Pavel Machek :
>>>
>>> hi!
>>>
>> But as said I don't think we need float or
Hi Petr and all,
> Am 20.02.2017 um 23:26 schrieb Petr Cvek :
>
> Hi
>
> Dne 20.2.2017 v 17:50 H. Nikolaus Schaller napsal(a):
>> Hi Pavel,
>>
>>> Am 19.02.2017 um 23:19 schrieb Pavel Machek :
>>>
>>> hi!
>>>
>> But as said I don't think we need float or fixed point for practical
>>
Hi Pali,
> Am 20.02.2017 um 20:42 schrieb Pali Rohár :
>
> Hi Nikolaus!
>
> On Monday 20 February 2017 17:50:04 H. Nikolaus Schaller wrote:
>> Hi Dmitry,
>>
>>> Input driver may set resolution for given axis in units per mm (or
>>> units per radian for rotational axis
Hi Pali,
> Am 20.02.2017 um 20:42 schrieb Pali Rohár :
>
> Hi Nikolaus!
>
> On Monday 20 February 2017 17:50:04 H. Nikolaus Schaller wrote:
>> Hi Dmitry,
>>
>>> Input driver may set resolution for given axis in units per mm (or
>>> units per radian for rotational axis ABS_RX, ABS_RY, ABS_RZ),
Hi Dmitry,
> Am 20.02.2017 um 23:24 schrieb Dmitry Torokhov :
>
> On Mon, Feb 20, 2017 at 2:21 PM, Petr Cvek wrote:
>> Hi,
>>
>> Dne 20.2.2017 v 22:50 Dmitry Torokhov napsal(a):
>>> On Mon, Feb 20, 2017 at 1:27 PM, H. Nikolaus Schaller
Hi Dmitry,
> Am 20.02.2017 um 23:24 schrieb Dmitry Torokhov :
>
> On Mon, Feb 20, 2017 at 2:21 PM, Petr Cvek wrote:
>> Hi,
>>
>> Dne 20.2.2017 v 22:50 Dmitry Torokhov napsal(a):
>>> On Mon, Feb 20, 2017 at 1:27 PM, H. Nikolaus Schaller
>>> wrote:
> Am 20.02.2017 um 22:08 schrieb
Hi Pali,
> Am 20.02.2017 um 23:04 schrieb Pali Rohár :
>
> On Monday 20 February 2017 22:27:39 H. Nikolaus Schaller wrote:
>>> Am 20.02.2017 um 22:08 schrieb Pali Rohár :
>>>
>>> On Monday 20 February 2017 20:42:15 Pali Rohár wrote:
While I'm
Hi Pali,
> Am 20.02.2017 um 23:04 schrieb Pali Rohár :
>
> On Monday 20 February 2017 22:27:39 H. Nikolaus Schaller wrote:
>>> Am 20.02.2017 um 22:08 schrieb Pali Rohár :
>>>
>>> On Monday 20 February 2017 20:42:15 Pali Rohár wrote:
While I'm watching this discussion... in my opinion
Hi Pali,
> Am 20.02.2017 um 22:54 schrieb Pali Rohár :
>
> On Monday 20 February 2017 22:24:31 H. Nikolaus Schaller wrote:
>> Hi Pali,
>>
>>> Am 20.02.2017 um 22:07 schrieb Pali Rohár :
>>>
>>> On Monday 20 February 2017 21:35:18 H. Nikolaus Schaller
Hi Pali,
> Am 20.02.2017 um 22:54 schrieb Pali Rohár :
>
> On Monday 20 February 2017 22:24:31 H. Nikolaus Schaller wrote:
>> Hi Pali,
>>
>>> Am 20.02.2017 um 22:07 schrieb Pali Rohár :
>>>
>>> On Monday 20 February 2017 21:35:18 H. Nikolaus Schaller wrote:
Hi Pali,
> Am
Hi,
> Am 20.02.2017 um 22:50 schrieb Dmitry Torokhov :
>
> On Mon, Feb 20, 2017 at 1:27 PM, H. Nikolaus Schaller
> wrote:
>>
>>> Am 20.02.2017 um 22:08 schrieb Pali Rohár :
>>>
>>> On Monday 20 February 2017 20:42:15 Pali
Hi,
> Am 20.02.2017 um 22:50 schrieb Dmitry Torokhov :
>
> On Mon, Feb 20, 2017 at 1:27 PM, H. Nikolaus Schaller
> wrote:
>>
>>> Am 20.02.2017 um 22:08 schrieb Pali Rohár :
>>>
>>> On Monday 20 February 2017 20:42:15 Pali Rohár wrote:
Hi Nikolaus!
On Monday 20 February 2017
On Monday 20 February 2017 23:21:37 Petr Cvek wrote:
> Hi,
>
> Dne 20.2.2017 v 22:50 Dmitry Torokhov napsal(a):
> > On Mon, Feb 20, 2017 at 1:27 PM, H. Nikolaus Schaller
> > wrote:
> >>> Am 20.02.2017 um 22:08 schrieb Pali Rohár :
> >>>
> >>> On Monday
On Monday 20 February 2017 23:21:37 Petr Cvek wrote:
> Hi,
>
> Dne 20.2.2017 v 22:50 Dmitry Torokhov napsal(a):
> > On Mon, Feb 20, 2017 at 1:27 PM, H. Nikolaus Schaller
> > wrote:
> >>> Am 20.02.2017 um 22:08 schrieb Pali Rohár :
> >>>
> >>> On Monday 20 February 2017 20:42:15 Pali Rohár
Hi,
Dne 20.2.2017 v 22:50 Dmitry Torokhov napsal(a):
> On Mon, Feb 20, 2017 at 1:27 PM, H. Nikolaus Schaller
> wrote:
>>
>>> Am 20.02.2017 um 22:08 schrieb Pali Rohár :
>>>
>>> On Monday 20 February 2017 20:42:15 Pali Rohár wrote:
Hi Nikolaus!
Hi,
Dne 20.2.2017 v 22:50 Dmitry Torokhov napsal(a):
> On Mon, Feb 20, 2017 at 1:27 PM, H. Nikolaus Schaller
> wrote:
>>
>>> Am 20.02.2017 um 22:08 schrieb Pali Rohár :
>>>
>>> On Monday 20 February 2017 20:42:15 Pali Rohár wrote:
Hi Nikolaus!
On Monday 20 February 2017 17:50:04
Hi
Dne 20.2.2017 v 17:50 H. Nikolaus Schaller napsal(a):
> Hi Pavel,
>
>> Am 19.02.2017 um 23:19 schrieb Pavel Machek :
>>
>> hi!
>>
> But as said I don't think we need float or fixed point for practical
> systems
> at all.
So you are going to loose
Hi
Dne 20.2.2017 v 17:50 H. Nikolaus Schaller napsal(a):
> Hi Pavel,
>
>> Am 19.02.2017 um 23:19 schrieb Pavel Machek :
>>
>> hi!
>>
> But as said I don't think we need float or fixed point for practical
> systems
> at all.
So you are going to loose precision. And if
On Mon, Feb 20, 2017 at 2:21 PM, Petr Cvek wrote:
> Hi,
>
> Dne 20.2.2017 v 22:50 Dmitry Torokhov napsal(a):
>> On Mon, Feb 20, 2017 at 1:27 PM, H. Nikolaus Schaller
>> wrote:
>>>
Am 20.02.2017 um 22:08 schrieb Pali Rohár :
On Mon, Feb 20, 2017 at 2:21 PM, Petr Cvek wrote:
> Hi,
>
> Dne 20.2.2017 v 22:50 Dmitry Torokhov napsal(a):
>> On Mon, Feb 20, 2017 at 1:27 PM, H. Nikolaus Schaller
>> wrote:
>>>
Am 20.02.2017 um 22:08 schrieb Pali Rohár :
On Monday 20 February 2017 20:42:15 Pali Rohár wrote:
On Monday 20 February 2017 22:27:39 H. Nikolaus Schaller wrote:
> > Am 20.02.2017 um 22:08 schrieb Pali Rohár :
> >
> > On Monday 20 February 2017 20:42:15 Pali Rohár wrote:
> >> While I'm watching this discussion... in my opinion kernel should
> >> just invert input axes
On Monday 20 February 2017 22:27:39 H. Nikolaus Schaller wrote:
> > Am 20.02.2017 um 22:08 schrieb Pali Rohár :
> >
> > On Monday 20 February 2017 20:42:15 Pali Rohár wrote:
> >> While I'm watching this discussion... in my opinion kernel should
> >> just invert input axes (when needed)
>
> It is
On Monday 20 February 2017 22:24:31 H. Nikolaus Schaller wrote:
> Hi Pali,
>
> > Am 20.02.2017 um 22:07 schrieb Pali Rohár :
> >
> > On Monday 20 February 2017 21:35:18 H. Nikolaus Schaller wrote:
> >> Hi Pali,
> >>
> >>> Am 20.02.2017 um 20:42 schrieb Pali Rohár
On Monday 20 February 2017 22:24:31 H. Nikolaus Schaller wrote:
> Hi Pali,
>
> > Am 20.02.2017 um 22:07 schrieb Pali Rohár :
> >
> > On Monday 20 February 2017 21:35:18 H. Nikolaus Schaller wrote:
> >> Hi Pali,
> >>
> >>> Am 20.02.2017 um 20:42 schrieb Pali Rohár :
> >>>
> >>> Hi Nikolaus!
>
On Mon, Feb 20, 2017 at 1:27 PM, H. Nikolaus Schaller
wrote:
>
>> Am 20.02.2017 um 22:08 schrieb Pali Rohár :
>>
>> On Monday 20 February 2017 20:42:15 Pali Rohár wrote:
>>> Hi Nikolaus!
>>>
>>> On Monday 20 February 2017 17:50:04 H. Nikolaus Schaller
On Mon, Feb 20, 2017 at 1:27 PM, H. Nikolaus Schaller
wrote:
>
>> Am 20.02.2017 um 22:08 schrieb Pali Rohár :
>>
>> On Monday 20 February 2017 20:42:15 Pali Rohár wrote:
>>> Hi Nikolaus!
>>>
>>> On Monday 20 February 2017 17:50:04 H. Nikolaus Schaller wrote:
Hi Dmitry,
> Input
> Am 20.02.2017 um 22:08 schrieb Pali Rohár :
>
> On Monday 20 February 2017 20:42:15 Pali Rohár wrote:
>> Hi Nikolaus!
>>
>> On Monday 20 February 2017 17:50:04 H. Nikolaus Schaller wrote:
>>> Hi Dmitry,
>>>
Input driver may set resolution for given axis in units
> Am 20.02.2017 um 22:08 schrieb Pali Rohár :
>
> On Monday 20 February 2017 20:42:15 Pali Rohár wrote:
>> Hi Nikolaus!
>>
>> On Monday 20 February 2017 17:50:04 H. Nikolaus Schaller wrote:
>>> Hi Dmitry,
>>>
Input driver may set resolution for given axis in units per mm
(or units
Hi Pali,
> Am 20.02.2017 um 22:07 schrieb Pali Rohár :
>
> On Monday 20 February 2017 21:35:18 H. Nikolaus Schaller wrote:
>> Hi Pali,
>>
>>> Am 20.02.2017 um 20:42 schrieb Pali Rohár :
>>>
>>> Hi Nikolaus!
>>>
>>> On Monday 20 February 2017
Hi Pali,
> Am 20.02.2017 um 22:07 schrieb Pali Rohár :
>
> On Monday 20 February 2017 21:35:18 H. Nikolaus Schaller wrote:
>> Hi Pali,
>>
>>> Am 20.02.2017 um 20:42 schrieb Pali Rohár :
>>>
>>> Hi Nikolaus!
>>>
>>> On Monday 20 February 2017 17:50:04 H. Nikolaus Schaller wrote:
Hi
On Monday 20 February 2017 20:42:15 Pali Rohár wrote:
> Hi Nikolaus!
>
> On Monday 20 February 2017 17:50:04 H. Nikolaus Schaller wrote:
> > Hi Dmitry,
> >
> > > Input driver may set resolution for given axis in units per mm
> > > (or units per radian for rotational axis ABS_RX, ABS_RY,
> > >
On Monday 20 February 2017 20:42:15 Pali Rohár wrote:
> Hi Nikolaus!
>
> On Monday 20 February 2017 17:50:04 H. Nikolaus Schaller wrote:
> > Hi Dmitry,
> >
> > > Input driver may set resolution for given axis in units per mm
> > > (or units per radian for rotational axis ABS_RX, ABS_RY,
> > >
On Monday 20 February 2017 21:35:18 H. Nikolaus Schaller wrote:
> Hi Pali,
>
> > Am 20.02.2017 um 20:42 schrieb Pali Rohár :
> >
> > Hi Nikolaus!
> >
> > On Monday 20 February 2017 17:50:04 H. Nikolaus Schaller wrote:
> >> Hi Dmitry,
> >>
> >>> Input driver may set
On Monday 20 February 2017 21:35:18 H. Nikolaus Schaller wrote:
> Hi Pali,
>
> > Am 20.02.2017 um 20:42 schrieb Pali Rohár :
> >
> > Hi Nikolaus!
> >
> > On Monday 20 February 2017 17:50:04 H. Nikolaus Schaller wrote:
> >> Hi Dmitry,
> >>
> >>> Input driver may set resolution for given axis in
> Am 20.02.2017 um 21:22 schrieb H. Nikolaus Schaller :
>
> Hi,
>
>> Am 20.02.2017 um 20:32 schrieb Pavel Machek :
>>
>> Hi!
>>
But if you have userspace that depends on touchscreen to be
calibrated... that _is_ wrong.
>>>
>>> User-space people and
> Am 20.02.2017 um 21:22 schrieb H. Nikolaus Schaller :
>
> Hi,
>
>> Am 20.02.2017 um 20:32 schrieb Pavel Machek :
>>
>> Hi!
>>
But if you have userspace that depends on touchscreen to be
calibrated... that _is_ wrong.
>>>
>>> User-space people and real users have the opposite
Hi Pali,
> Am 20.02.2017 um 20:42 schrieb Pali Rohár :
>
> Hi Nikolaus!
>
> On Monday 20 February 2017 17:50:04 H. Nikolaus Schaller wrote:
>> Hi Dmitry,
>>
>>> Input driver may set resolution for given axis in units per mm (or
>>> units per radian for rotational axis
Hi Pali,
> Am 20.02.2017 um 20:42 schrieb Pali Rohár :
>
> Hi Nikolaus!
>
> On Monday 20 February 2017 17:50:04 H. Nikolaus Schaller wrote:
>> Hi Dmitry,
>>
>>> Input driver may set resolution for given axis in units per mm (or
>>> units per radian for rotational axis ABS_RX, ABS_RY, ABS_RZ),
Hi,
> Am 20.02.2017 um 20:32 schrieb Pavel Machek :
>
> Hi!
>
>>> But if you have userspace that depends on touchscreen to be
>>> calibrated... that _is_ wrong.
>>
>> User-space people and real users have the opposite opinion. They
>> prefer if a touch is plug I.e. without need
Hi,
> Am 20.02.2017 um 20:32 schrieb Pavel Machek :
>
> Hi!
>
>>> But if you have userspace that depends on touchscreen to be
>>> calibrated... that _is_ wrong.
>>
>> User-space people and real users have the opposite opinion. They
>> prefer if a touch is plug I.e. without need for
HI Pavel,
> Am 20.02.2017 um 20:29 schrieb Pavel Machek :
>
> Hi!
>
>> As long as it is small (I expect <1.01 = 1% error in scale) it is
>> barely noticeable.
>>
>> Therefore, I asked before: how big in pixels is your finger or stylus?
>> Does this effect matter?
>
> If I draw a
HI Pavel,
> Am 20.02.2017 um 20:29 schrieb Pavel Machek :
>
> Hi!
>
>> As long as it is small (I expect <1.01 = 1% error in scale) it is
>> barely noticeable.
>>
>> Therefore, I asked before: how big in pixels is your finger or stylus?
>> Does this effect matter?
>
> If I draw a line in gimp,
Hi Nikolaus!
On Monday 20 February 2017 17:50:04 H. Nikolaus Schaller wrote:
> Hi Dmitry,
>
> > Input driver may set resolution for given axis in units per mm (or
> > units per radian for rotational axis ABS_RX, ABS_RY, ABS_RZ), and
> > if you check the binding, you can use "touchscreen-x-mm"
Hi Nikolaus!
On Monday 20 February 2017 17:50:04 H. Nikolaus Schaller wrote:
> Hi Dmitry,
>
> > Input driver may set resolution for given axis in units per mm (or
> > units per radian for rotational axis ABS_RX, ABS_RY, ABS_RZ), and
> > if you check the binding, you can use "touchscreen-x-mm"
Hi!
> > But if you have userspace that depends on touchscreen to be
> > calibrated... that _is_ wrong.
>
> User-space people and real users have the opposite opinion. They
> prefer if a touch is plug I.e. without need for calibration.
Some people prefer to calibrate their touchscreens; because
Hi!
> > But if you have userspace that depends on touchscreen to be
> > calibrated... that _is_ wrong.
>
> User-space people and real users have the opposite opinion. They
> prefer if a touch is plug I.e. without need for calibration.
Some people prefer to calibrate their touchscreens; because
Hi!
> As long as it is small (I expect <1.01 = 1% error in scale) it is
> barely noticeable.
>
> Therefore, I asked before: how big in pixels is your finger or stylus?
> Does this effect matter?
If I draw a line in gimp, I don't expect it to have steps because of
"barely noticeable" errors.
>
Hi!
> As long as it is small (I expect <1.01 = 1% error in scale) it is
> barely noticeable.
>
> Therefore, I asked before: how big in pixels is your finger or stylus?
> Does this effect matter?
If I draw a line in gimp, I don't expect it to have steps because of
"barely noticeable" errors.
>
Hi Dmitry,
> Am 20.02.2017 um 02:07 schrieb Dmitry Torokhov :
>
> Hi Nikolaus,
>
> On Sat, Feb 18, 2017 at 12:32:48PM +0100, H. Nikolaus Schaller wrote:
>> Hi Dmitry,
>>
>>> Am 17.02.2017 um 21:40 schrieb Dmitry Torokhov :
>>>
>>> Hi
Hi Dmitry,
> Am 20.02.2017 um 02:07 schrieb Dmitry Torokhov :
>
> Hi Nikolaus,
>
> On Sat, Feb 18, 2017 at 12:32:48PM +0100, H. Nikolaus Schaller wrote:
>> Hi Dmitry,
>>
>>> Am 17.02.2017 um 21:40 schrieb Dmitry Torokhov :
>>>
>>> Hi Nikolaus,
>>>
>>> On Sat, Jan 28, 2017 at 10:44:35PM
Hi Sebastian,
> Am 19.02.2017 um 21:15 schrieb Sebastian Reichel :
>
> Hi,
>
> On Sun, Feb 19, 2017 at 01:07:26PM +0100, H. Nikolaus Schaller wrote:
>> I don't really remember when we noticed it first. Maybe it was
>> back in tslib times some years ago where setting the
Hi Sebastian,
> Am 19.02.2017 um 21:15 schrieb Sebastian Reichel :
>
> Hi,
>
> On Sun, Feb 19, 2017 at 01:07:26PM +0100, H. Nikolaus Schaller wrote:
>> I don't really remember when we noticed it first. Maybe it was
>> back in tslib times some years ago where setting the sensitivity
>> threshold
Hi Pavel,
> Am 19.02.2017 um 23:39 schrieb Pavel Machek :
>
> Hi!
>
And note that I am not making things different from others in tree,
I am making the tsc2007 right (incl. following the touchscreen
bindings which define the touchscreen size in "Pixels").
>>>
>>>
Hi Pavel,
> Am 19.02.2017 um 23:19 schrieb Pavel Machek :
>
> hi!
>
But as said I don't think we need float or fixed point for practical
systems
at all.
>>>
>>> So you are going to loose precision. And if userspace decides to
>>> calibrate it slightly differently
Hi Pavel,
> Am 19.02.2017 um 23:39 schrieb Pavel Machek :
>
> Hi!
>
And note that I am not making things different from others in tree,
I am making the tsc2007 right (incl. following the touchscreen
bindings which define the touchscreen size in "Pixels").
>>>
>>> Your touch
Hi Pavel,
> Am 19.02.2017 um 23:19 schrieb Pavel Machek :
>
> hi!
>
But as said I don't think we need float or fixed point for practical
systems
at all.
>>>
>>> So you are going to loose precision. And if userspace decides to
>>> calibrate it slightly differently from kernel,
Hi Nikolaus,
On Sat, Feb 18, 2017 at 12:32:48PM +0100, H. Nikolaus Schaller wrote:
> Hi Dmitry,
>
> > Am 17.02.2017 um 21:40 schrieb Dmitry Torokhov :
> >
> > Hi Nikolaus,
> >
> > On Sat, Jan 28, 2017 at 10:44:35PM +0100, H. Nikolaus Schaller wrote:
> >> Hi Dmitry,
>
Hi Nikolaus,
On Sat, Feb 18, 2017 at 12:32:48PM +0100, H. Nikolaus Schaller wrote:
> Hi Dmitry,
>
> > Am 17.02.2017 um 21:40 schrieb Dmitry Torokhov :
> >
> > Hi Nikolaus,
> >
> > On Sat, Jan 28, 2017 at 10:44:35PM +0100, H. Nikolaus Schaller wrote:
> >> Hi Dmitry,
> >>
> >>> Am 28.01.2017 um
Hi!
> > > And note that I am not making things different from others in tree,
> > > I am making the tsc2007 right (incl. following the touchscreen
> > > bindings which define the touchscreen size in "Pixels").
> >
> > Your touch screen is not in any way special, so it has to behave in
> > the
Hi!
> > > And note that I am not making things different from others in tree,
> > > I am making the tsc2007 right (incl. following the touchscreen
> > > bindings which define the touchscreen size in "Pixels").
> >
> > Your touch screen is not in any way special, so it has to behave in
> > the
Hi,
On Sun, 19 Feb 2017 21:57:08 +0100
Pavel Machek wrote:
> Hi!
>
>
> > But as said I don't think we need float or fixed point for
> > practical systems at all.
>
> So you are going to loose precision. And if userspace decides to
> calibrate it slightly differently from
Hi,
On Sun, 19 Feb 2017 21:57:08 +0100
Pavel Machek wrote:
> Hi!
>
>
> > But as said I don't think we need float or fixed point for
> > practical systems at all.
>
> So you are going to loose precision. And if userspace decides to
> calibrate it slightly differently from kernel, lost
hi!
> >> But as said I don't think we need float or fixed point for practical
> >> systems
> >> at all.
> >
> > So you are going to loose precision. And if userspace decides to
> > calibrate it slightly differently from kernel, lost precision will
> > matter.
>
> Really?
Really.
> Example:
>
hi!
> >> But as said I don't think we need float or fixed point for practical
> >> systems
> >> at all.
> >
> > So you are going to loose precision. And if userspace decides to
> > calibrate it slightly differently from kernel, lost precision will
> > matter.
>
> Really?
Really.
> Example:
>
Hi Pavel,
> Am 19.02.2017 um 21:57 schrieb Pavel Machek :
>
> Hi!
>
>
>> But as said I don't think we need float or fixed point for practical systems
>> at all.
>
> So you are going to loose precision. And if userspace decides to
> calibrate it slightly differently from kernel,
Hi Pavel,
> Am 19.02.2017 um 21:57 schrieb Pavel Machek :
>
> Hi!
>
>
>> But as said I don't think we need float or fixed point for practical systems
>> at all.
>
> So you are going to loose precision. And if userspace decides to
> calibrate it slightly differently from kernel, lost precision
Hi!
> But as said I don't think we need float or fixed point for practical systems
> at all.
So you are going to loose precision. And if userspace decides to
calibrate it slightly differently from kernel, lost precision will
matter.
> >>> and floating point in kernel is hard. Also
> >>> you'd
Hi!
> But as said I don't think we need float or fixed point for practical systems
> at all.
So you are going to loose precision. And if userspace decides to
calibrate it slightly differently from kernel, lost precision will
matter.
> >>> and floating point in kernel is hard. Also
> >>> you'd
Hi,
On Sun, Feb 19, 2017 at 01:07:26PM +0100, H. Nikolaus Schaller wrote:
> I don't really remember when we noticed it first. Maybe it was
> back in tslib times some years ago where setting the sensitivity
> threshold made problems. We then carried along our patch for a
> long time in our local
Hi,
On Sun, Feb 19, 2017 at 01:07:26PM +0100, H. Nikolaus Schaller wrote:
> I don't really remember when we noticed it first. Maybe it was
> back in tslib times some years ago where setting the sensitivity
> threshold made problems. We then carried along our patch for a
> long time in our local
Hi Pavel,
> Am 19.02.2017 um 20:05 schrieb Pavel Machek :
>
> Hi!
>
>> Hi Pavel,
>> I love discussions with you :)
>
> Unfortunately I can't say the same.
>
>>> Am 19.02.2017 um 18:15 schrieb Pavel Machek :
>>>
>>>
> Solve it properly. That means passing
Hi Pavel,
> Am 19.02.2017 um 20:05 schrieb Pavel Machek :
>
> Hi!
>
>> Hi Pavel,
>> I love discussions with you :)
>
> Unfortunately I can't say the same.
>
>>> Am 19.02.2017 um 18:15 schrieb Pavel Machek :
>>>
>>>
> Solve it properly. That means passing calibration
> data from
Hi!
> Hi Pavel,
> I love discussions with you :)
Unfortunately I can't say the same.
> > Am 19.02.2017 um 18:15 schrieb Pavel Machek :
> >
> >
> >>> Solve it properly. That means passing calibration
> >>> data from kernel to userland.
> >>
> >> As written before, the really
Hi!
> Hi Pavel,
> I love discussions with you :)
Unfortunately I can't say the same.
> > Am 19.02.2017 um 18:15 schrieb Pavel Machek :
> >
> >
> >>> Solve it properly. That means passing calibration
> >>> data from kernel to userland.
> >>
> >> As written before, the really proper solution
Hi Pavel,
I love discussions with you :)
> Am 19.02.2017 um 18:15 schrieb Pavel Machek :
>
>
>>> Solve it properly. That means passing calibration
>>> data from kernel to userland.
>>
>> As written before, the really proper solution would be to provide floating
>> or fixed point
Hi Pavel,
I love discussions with you :)
> Am 19.02.2017 um 18:15 schrieb Pavel Machek :
>
>
>>> Solve it properly. That means passing calibration
>>> data from kernel to userland.
>>
>> As written before, the really proper solution would be to provide floating
>> or fixed point subpixel input
> > Solve it properly. That means passing calibration
> > data from kernel to userland.
>
> As written before, the really proper solution would be to provide floating
> or fixed point subpixel input events. Not arbitrarily scaling up in kernel
> and leaving downscaling to user space (where
> > Solve it properly. That means passing calibration
> > data from kernel to userland.
>
> As written before, the really proper solution would be to provide floating
> or fixed point subpixel input events. Not arbitrarily scaling up in kernel
> and leaving downscaling to user space (where
HI Pavel,
> Am 19.02.2017 um 15:17 schrieb Pavel Machek :
>
> Hi!
>
>> About loosing precision: there is already noise (jitter) in
>> real-world devices so that you can't achieve subpixel precision
>> anyways (unless your panel has a very low resolution). Please see my
>> answer
HI Pavel,
> Am 19.02.2017 um 15:17 schrieb Pavel Machek :
>
> Hi!
>
>> About loosing precision: there is already noise (jitter) in
>> real-world devices so that you can't achieve subpixel precision
>> anyways (unless your panel has a very low resolution). Please see my
>> answer to Dmitry some
Hi!
> About loosing precision: there is already noise (jitter) in
> real-world devices so that you can't achieve subpixel precision
> anyways (unless your panel has a very low resolution). Please see my
> answer to Dmitry some mails ago.
Maybe you can achieve better precision with averaging.
Hi!
> About loosing precision: there is already noise (jitter) in
> real-world devices so that you can't achieve subpixel precision
> anyways (unless your panel has a very low resolution). Please see my
> answer to Dmitry some mails ago.
Maybe you can achieve better precision with averaging.
Hi Sebastian,
> Am 19.02.2017 um 00:44 schrieb Sebastian Reichel :
>
> Hi,
>
> On Sat, Feb 18, 2017 at 12:33:34PM +0100, H. Nikolaus Schaller wrote:
>> Hi Sebastian,
>>
>>> Am 18.02.2017 um 04:22 schrieb Sebastian Reichel :
>>>
>>> Hi,
>>>
>>> On Fri, Feb
Hi Sebastian,
> Am 19.02.2017 um 00:44 schrieb Sebastian Reichel :
>
> Hi,
>
> On Sat, Feb 18, 2017 at 12:33:34PM +0100, H. Nikolaus Schaller wrote:
>> Hi Sebastian,
>>
>>> Am 18.02.2017 um 04:22 schrieb Sebastian Reichel :
>>>
>>> Hi,
>>>
>>> On Fri, Feb 17, 2017 at 12:40:41PM -0800, Dmitry
Hi Pavel,
> Am 18.02.2017 um 23:54 schrieb Pavel Machek :
>
> On Sat 2017-02-18 20:17:09, H. Nikolaus Schaller wrote:
>>
>>> Am 18.02.2017 um 19:08 schrieb Pavel Machek :
>>>
> And I agree that kernel should _not_ attempt rescaling itself, as it
> would lose
Hi Pavel,
> Am 18.02.2017 um 23:54 schrieb Pavel Machek :
>
> On Sat 2017-02-18 20:17:09, H. Nikolaus Schaller wrote:
>>
>>> Am 18.02.2017 um 19:08 schrieb Pavel Machek :
>>>
> And I agree that kernel should _not_ attempt rescaling itself, as it
> would lose precision.
With
Hi,
On Sat, Feb 18, 2017 at 12:33:34PM +0100, H. Nikolaus Schaller wrote:
> Hi Sebastian,
>
> > Am 18.02.2017 um 04:22 schrieb Sebastian Reichel :
> >
> > Hi,
> >
> > On Fri, Feb 17, 2017 at 12:40:41PM -0800, Dmitry Torokhov wrote:
> >>> AFAIK there is no mainline board using
Hi,
On Sat, Feb 18, 2017 at 12:33:34PM +0100, H. Nikolaus Schaller wrote:
> Hi Sebastian,
>
> > Am 18.02.2017 um 04:22 schrieb Sebastian Reichel :
> >
> > Hi,
> >
> > On Fri, Feb 17, 2017 at 12:40:41PM -0800, Dmitry Torokhov wrote:
> >>> AFAIK there is no mainline board using the DT except
1 - 100 of 128 matches
Mail list logo