linux-kernel - Re: [PATCH] usbtouchscreen, 2.6.25

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <ed7dcf450809240004r1d3c7b3ds619cd7441ae0365e@mail.gmail.com>
Date:	Wed, 24 Sep 2008 09:04:55 +0200
From:	"Søren Hauberg" <hauberg@...il.com>
To:	"Oliver Neukum" <oliver@...kum.org>
Cc:	"Ondrej Zary" <linux@...nbow-software.org>,
	linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org
Subject: Re: [PATCH] usbtouchscreen, 2.6.25

2008/9/23 Oliver Neukum <oliver@...kum.org>:
> Am Dienstag 23 September 2008 11:36:06 schrieb Søren Hauberg:
>> 2008/9/23 Ondrej Zary <linux@...nbow-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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/