public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Schubert <Jan.Schubert@GMX.li>
To: Georg Nikodym <georgn@somanetworks.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.0_test6: CONFIG_I8K produces wrong/no keycodes for special buttons
Date: Mon, 06 Oct 2003 19:56:05 +0200	[thread overview]
Message-ID: <3F81ACB5.2000309@GMX.li> (raw)
In-Reply-To: <20031006134215.7b857e06.georgn@somanetworks.com>

Georg Nikodym wrote:

>For the keys that show nothing, if you look at /var/log/messages, I
>think you'll see something like:
>
>>lay - <nothing>
>>    
>>
>
>Oct  6 13:39:24 keller kernel: atkbd.c: Unknown key pressed (translated set 2, code 0x176, data 0x1, on isa0060/serio0).
>Oct  6 13:39:24 keller kernel: atkbd.c: Unknown key released (translated set 2, code 0x176, data 0x81, on isa0060/serio0).
>  
>
>>back - <nothing>
>>    
>>
>
>Oct  6 13:39:29 keller kernel: atkbd.c: Unknown key pressed (translated set 2, code 0x11e, data 0x3, on isa0060/serio0).
>Oct  6 13:39:29 keller kernel: atkbd.c: Unknown key released (translated set 2, code 0x11e, data 0x83, on isa0060/serio0).
>
Indeed, this is exactly what i get :-).

>-g (who's been too lazy to attempt the atkbd.c patchery needed to fix this)
>
So, i assume you will fix this?

Thx,
Jan



  reply	other threads:[~2003-10-06 17:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-04 10:17 2.6.0_test6: CONFIG_I8K produces wrong/no keycodes for special buttons Jan Schubert
2003-10-06  2:37 ` Valdis.Kletnieks
2003-10-06  7:56   ` Jan Schubert
2003-10-06 10:34 ` Massimo Dal Zotto
2003-10-06 11:00   ` Jan Schubert
2003-10-06 17:42     ` Georg Nikodym
2003-10-06 17:56       ` Jan Schubert [this message]
2003-10-06 20:00         ` Georg Nikodym

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=3F81ACB5.2000309@GMX.li \
    --to=jan.schubert@gmx.li \
    --cc=georgn@somanetworks.com \
    --cc=linux-kernel@vger.kernel.org \
    /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