From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: sopwith@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Driver for Casio Cassiopia Fiva touchscreen, help with conversion
Date: Wed, 14 Feb 2001 12:04:41 +0000 (GMT) [thread overview]
Message-ID: <E14T0fr-0004iq-00@the-village.bc.nu> (raw)
In-Reply-To: <Pine.LNX.4.32.0102132034540.20720-100000@devserv.devel.redhat.com> from "Elliot Lee" at Feb 13, 2001 08:57:43 PM
> is a rather Bad Hack (seeing as it was built rather blindly to mimic the
> behaviour of the Windows driver, and has IRQ/port hardcoded in), but it
> works for me with the 2.2.16 kernel.
Thats pretty much how we did the pc110 pad driver too.
> The device outputs 5 byte packets - 1 status byte, 2 bytes each for X & Y
> coordinates. The devel branch of GTK+ has support for /dev/fidmour in the
That also sounds suprisingly familiar. I wonder, I wonder 8)
> I'm wondering if anyone has a resource that would provide information on
> porting this driver to the 2.4 kernel.
Two approaches. #1 You leave it as its own misc device and XInput device as
the pc110 pad does (the pc110pad reports ps/2 codes and does drag/tap in
the driver - might be worth a look to steal that)
> I would welcome comments on this driver, or on the MPC-501 and Linux in
> general. Bonus points to anyone who actually understands why the driver
> works and how the hardware works. :)
You might want to let the guys at www.amherst.co.uk know about it so they can
add it to their resources on the fiva
next prev parent reply other threads:[~2001-02-14 12:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-14 1:57 Driver for Casio Cassiopia Fiva touchscreen, help with conversion to 2.4 Elliot Lee
2001-02-14 12:04 ` Alan Cox [this message]
2001-02-14 12:56 ` Driver for Casio Cassiopia Fiva touchscreen, help with conversion Bruce Harada
2001-02-14 13:07 ` Alan Cox
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=E14T0fr-0004iq-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=sopwith@redhat.com \
/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
all inboxes | Powered by JetHome®