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 11:51:41 +0300	[thread overview]
Message-ID: <4CF0C69D.9080904@gmail.com> (raw)
In-Reply-To: <20101127083229.GA28745@core.coreip.homeip.net>

On 11/27/2010 11:32 AM, Dmitry Torokhov wrote:
> OUCH. We need to fix this _now_. We can not allow reporting resolutions
> in random units. Since we started with unit/mm we have to keep it and
> if it gives issues we can think about adding other units later on, but
> for everyone.
I understand your concerns, but this will make this feature useless for the
8 tablet models I was aiming it at. Most of them have 2000 LPI resolution.

The thing is, I suspect, there is basicly very little to none real devices
correctly specifying their resolution in the report descriptors. Plus almost
no one uses the resolution field in input_absinfo currently and especially
for generic processing (as opposed to working with a specific device). Even
more, I have failed to find any noticeable amount of device drivers filling
it in, but it could be my fault of course.

So, I think, now is the best time to standardize on this and do real
changes.

Sincerely,
Nick

  reply	other threads:[~2010-11-27  8:52 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 [this message]
     [not found]           ` <20101127091533.GA27213@core.coreip.homeip.net>
2010-11-27  9:46             ` Nikolai Kondrashov
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=4CF0C69D.9080904@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.