From: "Ville Syrjälä" <syrjala@sci.fi>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Peter Stokes <linux@dadeos.co.uk>,
linux-input@vger.kernel.org, dmitry.torokhov@gmail.com
Subject: Re: [PATCH] ati_remote2 autorepeat and loadable keymap support
Date: Tue, 4 Mar 2008 23:21:05 +0200 [thread overview]
Message-ID: <20080304212105.GG531@sci.fi> (raw)
In-Reply-To: <Pine.LNX.4.64.0803042138050.15209@jikos.suse.cz>
On Tue, Mar 04, 2008 at 09:42:22PM +0100, Jiri Kosina wrote:
> On Tue, 4 Mar 2008, Ville Syrjälä wrote:
>
> > > 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
next prev parent reply other threads:[~2008-03-04 21:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-16 16:22 [PATCH] ati_remote2 autorepeat and loadable keymap support Peter Stokes
2008-03-03 22:53 ` Jiri Kosina
2008-03-04 12:47 ` Ville Syrjälä
2008-03-04 13:20 ` Jiri Kosina
2008-03-04 13:47 ` Ville Syrjälä
2008-03-04 14:01 ` Jiri Kosina
2008-03-04 14:07 ` Ville Syrjälä
2008-03-04 18:40 ` Ville Syrjälä
2008-03-04 18:50 ` Jiri Kosina
2008-03-04 19:53 ` Ville Syrjälä
2008-03-04 20:28 ` Jiri Kosina
2008-03-04 20:32 ` Ville Syrjälä
2008-03-04 20:42 ` Jiri Kosina
2008-03-04 21:21 ` Ville Syrjälä [this message]
2008-03-04 22:02 ` Jiri Kosina
2008-03-04 18:55 ` Peter Stokes
2008-03-04 20:38 ` Ville Syrjälä
2008-03-04 21:34 ` Peter Stokes
2008-03-04 22:17 ` Ville Syrjälä
2008-03-04 22:25 ` Jiri Kosina
2008-03-25 8:23 ` Jiri Kosina
2008-04-07 20:39 ` Dmitry Torokhov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080304212105.GG531@sci.fi \
--to=syrjala@sci.fi \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux@dadeos.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).