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 for Android: free password hash cracker in your pocket

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

Message-ID: <ed7dcf450809240548v1946068chf60dc42ff1f901d4@mail.gmail.com>
Date:	Wed, 24 Sep 2008 14:48:39 +0200
From:	"Søren Hauberg" <hauberg@...il.com>
To:	"Matthew Garrett" <mjg59@...f.ucam.org>
Cc:	"Oliver Neukum" <oliver@...kum.org>,
	"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/24 Matthew Garrett <mjg59@...f.ucam.org>:
> On Wed, Sep 24, 2008 at 09:04:55AM +0200, Søren Hauberg wrote:
>> 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.
>
> This is the sort of thing that input device properties were added for.
> If you're able to use 1.5 of the X server, it's not a huge body of work
> to add this functionality.

Well, 1.5 isn't an option for me. But this does remove the main
problem with handling calibration in X. So, I guess that means my
patch shouldn't be applied. I'll continue to use it in-house for a
while, but it won't be a long term solution.

Thanks,
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/