public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "James H. Cloos Jr." <cloos@jhcloos.com>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Pavel Machek <pavel@ucw.cz>, "H. Peter Anvin" <hpa@zytor.com>,
	linux-kernel@vger.kernel.org
Subject: Re: PATCH: Four function buttons on DELL Latitude X200
Date: 12 Dec 2002 07:17:22 -0500	[thread overview]
Message-ID: <m3znrb4ejx.fsf@lugabout.jhcloos.org> (raw)
In-Reply-To: <20021212125114.A10134@ucw.cz>

>>>>> "Vojtech" == Vojtech Pavlik <vojtech@suse.cz> writes:

Vojtech> Do they by any chance produce a kernel warning when pressed?

Yes, the two keys that do not generate an event in X syslog these errors:

atkbd.c: Unknown key (set 2, scancode 0x176, on isa0060/serio0) pressed.
atkbd.c: Unknown key (set 2, scancode 0x176, on isa0060/serio0) released.
atkbd.c: Unknown key (set 2, scancode 0x11e, on isa0060/serio0) pressed.
atkbd.c: Unknown key (set 2, scancode 0x11e, on isa0060/serio0) released.

where 0x176 is the PLAY key and 0x11e is the PREV key.

Incidently, the FORWARD key is giving the same keycode as the main
kb's Pause key.

-JimC


  reply	other threads:[~2002-12-12 12:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-08 23:35 PATCH: Four function buttons on DELL Latitude X200 Pavel Janík
2002-12-09  0:19 ` Bernd Eckenfels
2002-12-09 19:33   ` H. Peter Anvin
2002-12-10 21:34     ` Pavel Machek
2002-12-11 22:41       ` H. Peter Anvin
2002-12-13 16:22         ` Jan-Benedict Glaw
2002-12-12  1:01       ` Andries Brouwer
2002-12-12  8:43       ` Vojtech Pavlik
2002-12-12 11:48         ` James H. Cloos Jr.
2002-12-12 11:51           ` Vojtech Pavlik
2002-12-12 12:17             ` James H. Cloos Jr. [this message]
2002-12-12 12:20               ` Vojtech Pavlik

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=m3znrb4ejx.fsf@lugabout.jhcloos.org \
    --to=cloos@jhcloos.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --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