On Tue, Mar 04, 2008 at 09:42:22PM +0100, Jiri Kosina wrote:

On Tue, 4 Mar 2008, Ville Syrjälä wrote:

quoted

quoted

Actually, this is the very same issue we discussed with respect to 
ati_remote2 changes ... this device has Keyboard usages as well as 
Mouse/Pointer. As we set the EV_REP (because of the Keyboard usage), 
this inputdevice-wide flag applies also to the mouse button events and 
they get repeated.

Except this device does actually register two input devices since the
endpoints for the keyboard and mouse are separate, and here it even
makes sense since they are physically separate devices.

Yes, but unfortunately both interfaces contain Keyboard usage in their 
report descriptor -- please see the debug output you sent me. The first 
interface's descriptor states to send Keyboard usages in Field(1) of INPUT 
report, the second one presents it in Field(1) of INPUT[1] report.

I guess that one of the report descriptors contains redundant information, 
not both interfaces are actually sending Keyboard/Consumer/etc events, 
right?

I suppose not. HID is more or less gibberish to me but at least I haven't
seen any extra keyboard events from the mouse or anything like that. The
mouse has just two buttons and a vertical wheel. The keyboard has the normal
keys, volume and playback control keys and some 10 extra keys like sleep,
mail, web etc. It also has an f-lock key which I suppose has something to
do with the fact that they've re-labeled the function keys with some
web/email/whatever texts and the F<number> is printed on the side
of the key.

I've used the device so little that I honestly didn't even notice that
the mouse claims to support pretty much every kind of event there is.
Maybe they were just lazy when making this device and didn't want to think
about the actual features of the device and instead just added every
possible thing to the descriptors.

-- 
Ville Syrjälä
syrjala@sci.fi
http://www.sci.fi/~syrjala/
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html