public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Domen Puncer <domen@coderock.org>
Cc: Rene Herman <rene.herman@keyaccess.nl>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	akpm@osdl.org
Subject: Re: 2.6.12-rc2: Compose key doesn't work
Date: Thu, 26 May 2005 14:27:24 +0200	[thread overview]
Message-ID: <20050526122724.GA3396@ucw.cz> (raw)
In-Reply-To: <20050526122315.GA3880@nd47.coderock.org>

[-- Attachment #1: Type: text/plain, Size: 1096 bytes --]

On Thu, May 26, 2005 at 02:23:15PM +0200, Domen Puncer wrote:

> Still true for 2.6.12-rc5. Should probably be fixed before final.

Caused by a bug in the atkbd-scroll feature. The attached patch
fixes it.

> On 14/04/05 12:04 +0200, Domen Puncer wrote:
> > On 10/04/05 11:52 +0200, Rene Herman wrote:
> > > Hi Vojtech.
> > > 
> > > I have mapped my right windows key to "Compose" in X:
> > ...
> > > 
> > > This worked fine upto  2.6.11.7, but doesn't under 2.6.12-rc2. The key 
> > > doesn't seem to be doing anything anymore: "Compose-'-e" just gets me 
> > > "'e" and so on.
> > 
> > I can confirm this, right windows key works as scroll up, so it might
> > be related to recent scroll patches.
> > 
> > A quick workaround is to:
> > echo -n "0" > /sys/bus/serio/devices/serio1/scroll
> > 
> > serio1 being the keyboard here.
> > 
> > Btw. is that "-n" really necessary? Had too look at the code to figure
> > out why it's not working :-)
> > 
> > > 
> > > X is X.org 6.8.1, keyboard is regular PS/2 keyboard, directly connected.
> > 
> > Same here.
> 

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

[-- Attachment #2: atkbd-fix-scroll --]
[-- Type: text/plain, Size: 809 bytes --]

ChangeSet@1.2229.1.9, 2005-04-04 15:37:45+02:00, vojtech@suse.cz
  input: Fix fast scrolling scancodes in atkbd.c
    
  Signed-off-by: Vojtech Pavlik <vojtech@suse.cz>


 atkbd.c |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)


diff -Nru a/drivers/input/keyboard/atkbd.c b/drivers/input/keyboard/atkbd.c
--- a/drivers/input/keyboard/atkbd.c	2005-05-03 15:23:34 +02:00
+++ b/drivers/input/keyboard/atkbd.c	2005-05-03 15:23:34 +02:00
@@ -171,9 +171,9 @@
 	unsigned char set2;
 } atkbd_scroll_keys[] = {
 	{ ATKBD_SCR_1,     0xc5 },
-	{ ATKBD_SCR_2,     0xa9 },
-	{ ATKBD_SCR_4,     0xb6 },
-	{ ATKBD_SCR_8,     0xa7 },
+	{ ATKBD_SCR_2,     0x9d },
+	{ ATKBD_SCR_4,     0xa4 },
+	{ ATKBD_SCR_8,     0x9b },
 	{ ATKBD_SCR_CLICK, 0xe0 },
 	{ ATKBD_SCR_LEFT,  0xcb },
 	{ ATKBD_SCR_RIGHT, 0xd2 },

  reply	other threads:[~2005-05-26 12:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-10  9:52 2.6.12-rc2: Compose key doesn't work Rene Herman
2005-04-14 10:04 ` Domen Puncer
2005-05-26 12:23   ` Domen Puncer
2005-05-26 12:27     ` Vojtech Pavlik [this message]
2005-06-03 21:16       ` Wakko Warner
2005-06-03 21:37         ` Dmitry Torokhov
2005-05-26 15:45     ` Wakko Warner
2005-05-26 15:53       ` Vojtech Pavlik
2005-05-26 16:09         ` Wakko Warner
2005-05-30 14:25         ` Wakko Warner
2005-05-30 14:39           ` Vojtech Pavlik
2005-05-30 23:03         ` Rene Herman
2005-04-14 11:18 ` Kees Bakker

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=20050526122724.GA3396@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=akpm@osdl.org \
    --cc=domen@coderock.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rene.herman@keyaccess.nl \
    /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