All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikolai Kondrashov <spbnick@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Chris Bagwell <chris@cnpbagwell.com>,
	Henrik Rydberg <rydberg@euromail.se>,
	Ping Cheng <pinglinux@gmail.com>,
	linux-input <linux-input@vger.kernel.org>,
	Jiri Kosina <jkosina@suze.cz>
Subject: Re: [RFC] Adding BTN_TOOL_TOUCH to input.h
Date: Sat, 27 Nov 2010 12:46:03 +0300	[thread overview]
Message-ID: <4CF0D35B.4030807@gmail.com> (raw)
In-Reply-To: <20101127091533.GA27213@core.coreip.homeip.net>

On 11/27/2010 12:15 PM, Dmitry Torokhov wrote:
> 2000LPI == about 79 l/mm. How is it not useable?
TBH, I didn't make any real calculations.
The introduced error isn't very high, indeed. The vertical size of 4x3 inch
tablet becomes 75 mm instead of 76 mm. So maybe it's alright.

> In mainline synaptics is the only one that does this. We do not know how
> many drivers in vendor trees fill and use this data nor we do not know
> about userspace. The fact that we were not able to locate them does not
> mean they do not exist. The units/mm are part of input ABI now.
Well, I can't argue with you here.
I didn't think about 3rd party drivers, TBH.

> Right, standarize on existing UOM (which are per/mm) and then implement
> other UOM if theya re really needed.
Will this fix qualify for inclusion into 2.6.37?
Also, what do you think about units per radians for rotational axis?

Thanks :)

Sincerely,
Nick

  parent reply	other threads:[~2010-11-27  9:46 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-25 14:05 [RFC] Adding BTN_TOOL_TOUCH to input.h Henrik Rydberg
2010-11-25 14:12 ` Nikolai Kondrashov
2010-11-26 23:02   ` Chris Bagwell
2010-11-27  7:59     ` Dmitry Torokhov
2010-11-27  8:06     ` Nikolai Kondrashov
2010-11-27  8:32       ` Dmitry Torokhov
2010-11-27  8:51         ` Nikolai Kondrashov
     [not found]           ` <20101127091533.GA27213@core.coreip.homeip.net>
2010-11-27  9:46             ` Nikolai Kondrashov [this message]
2010-11-27 22:08               ` Chris Bagwell
2010-11-27 23:39               ` Dmitry Torokhov
2010-11-28  7:22                 ` Dmitry Torokhov
2010-11-28 14:57                   ` Nikolai Kondrashov
2010-11-28 21:47                     ` Dmitry Torokhov
2010-12-07 16:59                       ` Nikolai Kondrashov
2010-11-28  8:01                 ` Dmitry Torokhov
2010-11-28  8:28                   ` Henrik Rydberg
2010-11-28 10:14                   ` Nikolai Kondrashov
2010-11-27  8:15 ` Dmitry Torokhov
2010-11-27 17:04   ` Henrik Rydberg
2010-11-27 22:22     ` Chris Bagwell
  -- strict thread matches above, loose matches on Subject: below --
2010-11-23 20:48 Ping Cheng
2010-11-23 22:30 ` Dmitry Torokhov
2010-11-23 22:40   ` Ping Cheng
2010-11-24  2:52     ` Dmitry Torokhov
2010-11-24  4:55       ` Chris Bagwell
2010-11-24 20:26         ` Dmitry Torokhov
2010-11-24 22:55           ` Chris Bagwell
2010-11-25  1:31             ` Dmitry Torokhov
2010-11-26 22:48               ` Chris Bagwell
2010-11-27  8:06                 ` Dmitry Torokhov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4CF0D35B.4030807@gmail.com \
    --to=spbnick@gmail.com \
    --cc=chris@cnpbagwell.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jkosina@suze.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=pinglinux@gmail.com \
    --cc=rydberg@euromail.se \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.