From: "Søren Hauberg" <hauberg@gmail.com>
To: "Oliver Neukum" <oliver@neukum.org>
Cc: "Ondrej Zary" <linux@rainbow-software.org>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH] usbtouchscreen, 2.6.25
Date: Wed, 24 Sep 2008 09:04:55 +0200 [thread overview]
Message-ID: <ed7dcf450809240004r1d3c7b3ds619cd7441ae0365e@mail.gmail.com> (raw)
In-Reply-To: <200809231613.41905.oliver@neukum.org>
2008/9/23 Oliver Neukum <oliver@neukum.org>:
> Am Dienstag 23 September 2008 11:36:06 schrieb Søren Hauberg:
>> 2008/9/23 Ondrej Zary <linux@rainbow-software.org>:
>> > Calibration is a per-device thing. You can have more than one touchscreen (the
>> > swap_xy feature is also wrong, but better than nothing).
>>
>> Yes, this is true. I'm going to claim (and I have no factual evidence
>> to back this claim, I'm just making it up) that almost all touchscreen
>> users only have one touchscreen. So, I'd rather have something that
>> works for most users, then the current situation. Is it optimal? No!
>> Is it practical? I believe so. Using your words, it's "better than
>> nothing".
>
> But is it better than the X driver?
Obviously that depends on how you define "better" :-) The problem I'm
facing is that with the X driver there is no way to change calibration
without restarting X several times, which isn't acceptable for the
application we're developing. Sure, I could fix the X driver to allow
run-time changes to the calibration parameters, but that's a very
large task. On the other hand, solving the problem in the kernel was
dead-easy. So, I agree that solving the problem in-kernel might not be
the best possible solution, it's just the only one I actually have the
time to implement (and it'll work for most users).
> How do other touchscreens do it?
They seem to do nothing, i.e. let the problem be solved in user space.
Søren
next prev parent reply other threads:[~2008-09-24 7:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-23 8:42 Søren Hauberg
2008-09-23 8:51 ` Ondrej Zary
2008-09-23 9:36 ` Søren Hauberg
2008-09-23 14:13 ` Oliver Neukum
2008-09-24 7:04 ` Søren Hauberg [this message]
2008-09-24 10:30 ` Matthew Garrett
2008-09-24 12:48 ` Søren Hauberg
2008-09-23 8:55 ` Oliver Neukum
2008-09-23 8:59 ` Søren Hauberg
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=ed7dcf450809240004r1d3c7b3ds619cd7441ae0365e@mail.gmail.com \
--to=hauberg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@rainbow-software.org \
--cc=oliver@neukum.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®