From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Igor Zhbanov <izh1979@gmail.com>
Cc: linux-input@vger.kernel.org
Subject: Re: No standard touchscreen driver for Samwell Ruggedbook Tablet PC 800. Which to use?
Date: Thu, 17 Jul 2008 12:36:09 -0400 [thread overview]
Message-ID: <20080717123041.ZZRA012@mailhub.coreip.homeip.net> (raw)
In-Reply-To: <f44001920807160954tb492bcdpadc66b91ff532367@mail.gmail.com>
Hi Igor,
On Wed, Jul 16, 2008 at 08:54:23PM +0400, Igor Zhbanov wrote:
> Hello!
>
> I have Samwell Ruggedbook Tablet PC 800:
> http://www.ruggedbook.com.tw/product_view.asp?ID=50
>
> It has 4-wire resistive touchscreen controlled by PIC16F819. Microcontroller
> has 10-bit ADC and it seems to be connected to PS/2. (I have no idea what
> is inside PIC's ROM.) Under Windows device works well with Wacom Tablet PC
> and PanJit TouchSet drivers (the later is not proprietary for this device).
>
> Under Linux I can capture events from /dev/input/event2 device. So I
> have written
> simple program that dumps data in hexadecimal view.
>
[ skip reverse-engineering effort of Linux event protocol, see
include/linux/input.h and struct input_event in particular ]
>
> Now is the main question. Is there a driver suitable for this protocol
> or it should be written? Have you seen this protocol in another touchscreen
> controllers already?
>
It looks that the device works in PS/2 compatibility mode. There seems
to be a driver on PanJit web site with some crude support, have you
tried it?
--
Dmitry
prev parent reply other threads:[~2008-07-17 16:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f44001920807160849p679857dbn7bf0fec419229cd6@mail.gmail.com>
2008-07-16 16:54 ` No standard touchscreen driver for Samwell Ruggedbook Tablet PC 800. Which to use? Igor Zhbanov
2008-07-17 16:36 ` Dmitry Torokhov [this message]
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=20080717123041.ZZRA012@mailhub.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=izh1979@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).