On 2013-05-30 16:38, Mark Jenkins wrote:
1. cat /dev/input/<whatever> | hexdump
2. evtest (see http://cgit.freedesktop.org/evtest/ - doesn't seem to
be
provided in packages for many distros)
Wheezy's got it, so they're an apt away from having a good time with
this.
Which /dev/input/event* device it is should become obvious from dmesg
after running inputattach or by comparing the before and after.
This is going to be easy to get going if the actual /dev/input/event
stuff ends up looking coherent.
Well, as long as inputattach is doing its bit correctly, and the driver
is doing its bit correctly.
Do note that "cat /dev/ttyS3 | hexdump" will *not* likely work
correctly, since open'ing a ttyS(4) device resets the baud rate. Linux
does some weird things with that, but in general you need something more
along the line of "(stty 9600;cat|hexdump) </dev/ttyS3" to make it work
properly. Yes, GNU stty(1) has a -F option, but that doesn't
(necessarily) change the reset-on-open behaviour. Note that in testing,
a modern CentOS 6.4 system *does* preserve the baud rate, so I don't
know where/when that behaviour changed...
-aDam
_______________________________________________
SkullSpace Discuss Mailing List
Help: http://www.skullspace.ca/wiki/index.php/Mailing_List#Discuss
Archive: https://groups.google.com/group/skullspace-discuss-archive/
