linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 15:47:51 +0200	[thread overview]
Message-ID: <20080304134751.GA531@sci.fi> (raw)
In-Reply-To: <Pine.LNX.4.64.0803041412240.18589@twin.jikos.cz>

On Tue, Mar 04, 2008 at 02:20:19PM +0100, Jiri Kosina wrote:
> On Tue, 4 Mar 2008, Ville Syrjälä wrote:
> 
> > > The attached patch reconfigures the ati_remote2 driver to use soft-autorepeat 
> > > functionality and adds support for loadable key maps.
> > Why was this submitted (and even accepted) without cc:ing me?
> 
> I don't seem to see you in MAINTAINERS entry, so that's probably why you 
> didn't receive confirmation when Andrew has put this patch into -mm.

I guess MODULE_AUTHOR() isn't enough then. I'll send a patch for
MAINTAINERS.

> Merging into -mm doesn't mean that the patch is accepted at all, it just 
> exposes it for wider audience for feedback and testing.
> 
> 
> With respect to autorepeat -- I think that the easiest solution would be 
> registering two separate input devices, one for keyboard and one for 
> mouse, and perform the switching in the driver, depending on the type of 
> received events.

Hmm. IIRC I had one USB mouse which also sent repeat events and the
driver didn't seem to filter them out which is why I added checks to
DirectFB's input driver to filter them in user space. Was that a bug
in the usbhid driver or does it depend on the actual hardware? I still
have that mouse so I can re-test the behavior if needed. I guess the
only issue with registering two input devices whould be that user space
might need some way to tell that they are really part of the same
remote.

-- 
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

  reply	other threads:[~2008-03-04 13:47 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ä [this message]
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ä
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=20080304134751.GA531@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).