The current state of affairs as far as being able to use /dev/input/event<n> directly is, exceedingly suboptimal.
To be blunt, under 2.4.x kernels the interface lacks ANY way to
determine which device you have if you have two identical devices.
To make matters worse, while there /are/ ioctls to get the bus location
for 2.5.x kernels the #defines do not even exist for the 2.4.x headers.
This for a supposedly identical evdev protocol version.
Until this can be sorted out it is going to be /very/ problematic to
actually use the evdev interface for even mildly complex setups.
Zephaniah E. Hull.
(Back to trying to figure out how to get X to turn input drivers on and
off from outside signals.)
--
1024D/E65A7801 Zephaniah E. Hull <[EMAIL PROTECTED]>
92ED 94E4 B1E6 3624 226D 5727 4453 008B E65A 7801
CCs of replies from mailing lists are requested.
<Mercury> Knghtbrd: Eww, find a better name, the movie sucked.. <G>
<Knghtbrd> Mercury: The engine is better than the movie
msg10731/pgp00000.pgp
Description: PGP signature
