On Mon, Nov 11, 2002 at 12:03:34AM -0500, Zephaniah E. Hull wrote: > On Mon, Nov 11, 2002 at 03:12:49PM +1100, Brad Hards wrote: > <snip> > > > Hmm, obviously this makes my current identification method rather > > > suboptimial. > > Depends on the problem we need to solve. If the machine only has one of each > > device, then it doesn't matter where it is plugged in, and we can use > > EVIOCGNAME or EVIOCGID. > > > > If the machine is multi-headed, then perhaps the physical path will be better. > > > > > What about using the bus, vendor, product, and version tags? (Returned > > > by EVIOCGID) > > That isn't different to using the strings on USB, except for the odd case > > where the string just says "mouse" or something silly. > > > > > The main catch is that I don't have a clue what those would be set to > > > for ADB or PS2 mice for 2.5.x. > > They will exist, but may not be unique (same as if you have two > > identical mice). There is an ioctl() for a unique identifier > > (EVIOCGUNIQ), but on most devices, it'll return NULL. > > Hmm, this is really starting to tell me that we need the ability to > specify any of these, not too hard, I think.
Argh, more interesting problem.
EVIOCGUNIQ does not even exist in the 2.4.x headers, and EVIOCGBUS
happily returns 0 0 0 0, instead of useful data.
This means that, at least with 2.4.x, it is impossible to tell the
difference between two identical mice.
I guess this means that my next step is seeing what is available for
2.5.x drivers.
Zephaniah E. Hull.
--
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.
Perl == Being
-- Descartes (paraphrased).
msg10727/pgp00000.pgp
Description: PGP signature
