From: Till Crueger <T.Crueger@fh-trier.de>
To: linux-input <linux-input@vger.kernel.org>
Subject: Using an eGalax touchpad on ARM
Date: Thu, 02 Aug 2012 13:52:30 +0200 [thread overview]
Message-ID: <501A69FE.2050104@fh-trier.de> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I am currently trying to get an D-Wav/eGalax touchpad to work under
linux on an ARM board (pandaboard). I can use the touchpad just fine
from most laptops running gentoo or ubuntu.
To get the device to work I followed the guide I found at
https://wiki.archlinux.org/index.php/Multitouch_Displays. This means I
load the hid-multitouch driver and then issue
# echo 3 0eef 72f0 259 >
/sys/module/hid_multitouch/drivers/hid\:hid-multitouch/new_id
which activates the device on my laptop running gentoo.
The same procedure on the pandaboard does not activate the touchpad
however. I can see the touchpad just fine using lsusb, but somehow the
activation fails.
What could be the cause for the activation failure under a different
architecture?
One possible reason why this may not work, that I am currently
considering is the BUS-Number. When I first tried to activate the device
on the laptop I assumed this number was refering to the USB-Bus to which
the device was connected. However after re-reading the guide for
arch-linux, I figured out that this number is 3 for any USB-device.
However I could not figure out what this magic number is referring to.
Is it possible, that this number is different on the pandaboard? If so,
how could I find out the correct number to use for activation of the device?
If you need any additional information (output from dmesg, lsusb etc)
just let me know and I'll get the necessary information from the board.
Thank you for your help,
Till Crueger
- --
Dipl. Inform. Till Crueger
Department of Computer Science
Trier University of Applied Sciences
Postfach 1826
54208 Trier
GERMANY
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJQGmn+AAoJEMyqYnfSqLbVYMIIAI+GUSJI29e87OtWITCewebc
aE4STPUcl9StOREOGtMoOoLmG2n6YDOt1xNi6ynUih/H5MdHRPz4d7VNWaTdC5rs
hVp8gQ5c2DGvHTNVb88ezoDb2FudsxBDEpXoQU+TXgN0ke6PpVfvtwPsarvBFHv5
lvxLXTi0o3mHSWw/XTZw90UP7O49l1pCjISfvQdkRCcVrySEDNJAQFkJQAeARzim
cBqvjHBscUZJO/5ddE1v1QWY3QEPuMiXLptL0sKAMDK6X/R29XtAVVzX5z0W7E6f
Kj5u8qqvEvvHaMyMC2p+Tp/zlmnKVvQCKs1COlwcBRLvy3BTnUc9pzGP3wb4K2w=
=Ar2y
-----END PGP SIGNATURE-----
reply other threads:[~2012-08-02 12:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=501A69FE.2050104@fh-trier.de \
--to=t.crueger@fh-trier.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.