In message <200212260630.gBQ6Twk24766@guild.plethora.net>, Dave Sainty writes:
>If it's a HID device, it's correct for it to attach as a uhid device.

It's not, though.  It's a device which *can* probe as a HID, but which
doesn't support its full functionality in that mode.  (Silly, I know.)

>What is treating it as a mouse though?  Is it attaching as a ums(4)
>device?  Perhaps something should be done to prevent that?

That's the thing; if you don't attach to it with ugen, we ask it if maybe
it's a mouse, and it assumes we have no driver, and goes into dumb mouse
mode.

>Could you dump the HID report descriptor for your device?  Possibly
>the ums(4) matching code needs to check for one-dimensional "mice" and
>filter them out...

Hmm.  That might work, but I'm not sure it's very generalizable; indeed,
it may be better to do the one-dimensional mouse for anyone who doesn't
add the magic cookie to the kernel config file.

-s