From: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Elo touchpad 10 bytes emulator
Date: Mon, 29 Mar 2010 20:51:11 +0200 [thread overview]
Message-ID: <aa76a2be1003291151n5c36c5e9gec32e8fd373b19f8@mail.gmail.com> (raw)
In-Reply-To: <201003291657.37961.paul@codesourcery.com>
Hello Paul
Hmmm, you are right, it should be part of the calibration (userland).
As Dmtry says, the output from the chip should be from 96-4000. I have
fixed the max values to that.
The previous code was done to emulate an old privative app that uses
an elo touchscreen. I managed to reverse engineer the code and found
the 10 bytes protocol it was using. It also uses a privative library
to talk with the touchscreen.
Digging in the kernel, I found more of the protocol specification, and
digging a little bit more in the internet I have found even more
information.
Please take a look to the last patch and tell me what do you think
Best regards and thanks for your comments.
On Mon, Mar 29, 2010 at 17:57, Paul Brook <paul@codesourcery.com> wrote:
>> New char device emulating an Elo serial touchpad.
>>
>> TODO: The output of the touchpad should be in the range of the
>> resolution. But I don't know a clean way to get the screen resolution.
>> Any help will be very wellcomed
>
> Are you sure? I don't see how real hardware would be able to do that.
>
> Paul
>
--
Ricardo Ribalda
http://www.eps.uam.es/~rribalda/
next prev parent reply other threads:[~2010-03-29 18:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 15:32 [Qemu-devel] [PATCH] Elo touchpad 10 bytes emulator Ricardo Ribalda Delgado
2010-03-29 15:57 ` Paul Brook
2010-03-29 18:51 ` Ricardo Ribalda Delgado [this message]
2010-03-29 17:59 ` Dmitry Zhurikhin
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=aa76a2be1003291151n5c36c5e9gec32e8fd373b19f8@mail.gmail.com \
--to=ricardo.ribalda@gmail.com \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.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).