From: mdew <some.nzguy@gmail.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: linux-usb-devel@lists.sourceforge.net,
Vojtech Pavlik <vojtech@suse.cz>,
Dmitry Torokhov <dtor_core@ameritech.net>
Subject: Re: Fw: ati-remote strangeness from 2.6.12 onwards
Date: Tue, 2 Aug 2005 17:04:29 +1200 [thread overview]
Message-ID: <1c1c8636050801220442d8351c@mail.gmail.com> (raw)
In-Reply-To: <20050730173253.693484a2.akpm@osdl.org>
I discovered a minor change in 2.6.10-mm1, changing this value back
corrects the "ok" button issue.
diff -urN linux/drivers/usb/input/ati_remote.c
linux-2.6.11/drivers/usb/input/ati_remote.c
--- linux/drivers/usb/input/ati_remote.c 2005-08-02
17:56:26.000000000 +1200
+++ linux-2.6.11/drivers/usb/input/ati_remote.c 2005-08-02
17:54:34.000000000 +1200
@@ -263,7 +263,7 @@
{KIND_FILTERED, 0xe4, 0x1f, EV_KEY, KEY_RIGHT, 1}, /* right */
{KIND_FILTERED, 0xe7, 0x22, EV_KEY, KEY_DOWN, 1}, /* down */
{KIND_FILTERED, 0xdf, 0x1a, EV_KEY, KEY_UP, 1}, /* up */
- {KIND_FILTERED, 0xe3, 0x1e, EV_KEY, KEY_ENTER, 1}, /* "OK" */
+ {KIND_FILTERED, 0xe3, 0x1e, EV_KEY, KEY_OK, 1}, /* "OK" */
{KIND_FILTERED, 0xce, 0x09, EV_KEY, KEY_VOLUMEDOWN, 1}, /* VOL + */
{KIND_FILTERED, 0xcd, 0x08, EV_KEY, KEY_VOLUMEUP, 1}, /* VOL - */
{KIND_FILTERED, 0xcf, 0x0a, EV_KEY, KEY_MUTE, 1}, /* MUTE */
On 7/31/05, Andrew Morton <akpm@osdl.org> wrote:
>
>
> Begin forwarded message:
>
> Date: Sun, 31 Jul 2005 12:18:23 +1200
> From: mdew <some.nzguy@gmail.com>
> To: linux-kernel <linux-kernel@vger.kernel.org>
> Subject: ati-remote strangeness from 2.6.12 onwards
>
>
> using 2.6.11 everything works fine, Upgrading too 2.6.13-rc3 I noticed 2 errors,
>
> (1) When setting the HZ rating too 250 or 100 will cause the driver to
> excessfully repeat keys/accelerate when pressing a button, making it
> unusable :(
>
> (2) the "Ok" button no longer works in anything after and including
> 2.6.12-rc1 (I've tested upto 2.6.13-rc3), 2.6.11 works fine. xbindkeys
> doesnt register any "ok" key presses on 2.6.12-rc1 onwards.
>
> 2.6.11 xbindkeys responses (nothing shows up in -rc1)
>
> mediabawx2:~# xbindkeys -mk
> Press combination of keys or/and click under the window.
> You can use one of the two lines after "NoCommand"
> in $HOME/.xbindkeysrc to bind a key.
>
> --- Press "q" to stop. ---
> "NoCommand"
> m:0x0 + c:36
> Return
> "NoCommand"
> m:0x0 + c:36
> Return
>
>
> Thanks :)
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next parent reply other threads:[~2005-08-02 5:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050730173253.693484a2.akpm@osdl.org>
2005-08-02 5:04 ` mdew [this message]
2005-08-03 5:54 ` Fw: ati-remote strangeness from 2.6.12 onwards Pavel Machek
2005-08-03 10:11 ` mdew
2005-08-03 11:41 ` [linux-usb-devel] " Frank Loeffler
2005-08-04 1:15 ` Ryan Brown
2005-08-04 20:27 ` Pavel Machek
2005-08-04 17:15 ` Andrew Morton
2005-08-04 22:23 ` Ryan Brown
2005-08-04 22:44 ` Andrew Morton
2005-08-05 6:46 ` [linux-usb-devel] " Frank Loeffler
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=1c1c8636050801220442d8351c@mail.gmail.com \
--to=some.nzguy@gmail.com \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=vojtech@suse.cz \
/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