From: Pavel Revak <palo@bielyvlk.sk>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org
Subject: Re: ucb1400 and mouse emulation
Date: Tue, 6 Oct 2009 15:41:17 +0200 [thread overview]
Message-ID: <b0ba3e300910060641x47c9d24as97d1b7e3c293a6d8@mail.gmail.com> (raw)
In-Reply-To: <20091006050624.GE27881@core.coreip.homeip.net>
On Tue, Oct 6, 2009 at 7:06 AM, Dmitry Torokhov
<dmitry.torokhov@gmail.com> wrote:
> Hi Pavel
>
> On Mon, Oct 05, 2009 at 02:34:09PM +0200, Pavel Revak wrote:
>> Hello, I upgraded to new kernel 2.6.31 (from 2.6.29) and I use
>> touchscreen with ucb1400 through library "tslib" which has own
>> calibration. from 2.6.30+ kernels this touchscreen emulate a mouse
>> (with out tslib) but is uncalibrated.
>
> This should not have changed, mousedev emulation was there for ages.
ah yes, but after this patch:
http://article.gmane.org/gmane.linux.kernel.commits.head/191681
mouse emulation works in my application.
>> My application use SDL with
>> framebuffer (no X server) and read mouse and touchscreen
>> simultaneously. But now it is unusable whne I use touchscreen, because
>> I read now touch screen as generic mouse (uncalibrated) and as tslib
>> (calibrated) at same time . Exist any way to calibrate touchscreen
>> without X server or tslib for sdl applications (this is preferred to
>> me) ? or can I disable mouse emulation from touchscreen and use only
>> tslib for sdl apps ?
>>
>
> The application has to decide what interface it wishes to use (mousedev
> or evdev) and read from that interface only.
OK, thanks
Palo.
next prev parent reply other threads:[~2009-10-06 13:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 12:34 ucb1400 and mouse emulation Pavel Revak
2009-10-06 5:06 ` Dmitry Torokhov
2009-10-06 13:41 ` Pavel Revak [this message]
2009-10-07 4:35 ` 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=b0ba3e300910060641x47c9d24as97d1b7e3c293a6d8@mail.gmail.com \
--to=palo@bielyvlk.sk \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).