All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor@insightbb.com>
To: linux-input@atrey.karlin.mff.cuni.cz
Cc: Bastien Nocera <hadess@hadess.net>
Subject: Re: Annoying keys on AT keyboards
Date: Tue, 29 May 2007 23:29:02 -0400	[thread overview]
Message-ID: <200705292329.03122.dtor@insightbb.com> (raw)
In-Reply-To: <1180477268.3030.111.camel@cookie.hadess.net>

Hi,

On Tuesday 29 May 2007 18:21, Bastien Nocera wrote:
> Heya,
> 
> My Dell laptop has a good bunch of keys that show this behaviour:
> Apr 25 11:23:10 snoogens kernel: atkbd.c: Unknown key pressed
> (translated set 2,
> code 0x87 on isa0060/serio0).
> Apr 25 11:23:10 snoogens kernel: atkbd.c: Use 'setkeycodes e007 <keycode>' to
> make it known.
> 
> Given that all Dell laptops generate this kind of behaviour, that all
> the keys match on all the models (I know about),

Hmm, mine does not generate e007...

> would it be 
> possible/sane to add some code to the AT keyboard driver to handle those
> keys when the DMI matches?

No, because it is not guaranteed that user will not plug external AT
keyboard with different keys assigned to the same keycodes. For drivers
like atkbd that may drive several devices at once DMI solution will
not work reliably (but it will work and is used for fixed hardware,
such as wistron_btns).

I just put:

setkeycodes e001 171
setkeycodes e002 172
setkeycodes e003 187
setkeycodes e004 189

in my rc.local several years ago and that is it. Distributions may do
that for users automatically during installation.

-- 
Dmitry

      reply	other threads:[~2007-05-30  3:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-29 22:21 Annoying keys on AT keyboards Bastien Nocera
2007-05-30  3:29 ` Dmitry Torokhov [this message]

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=200705292329.03122.dtor@insightbb.com \
    --to=dtor@insightbb.com \
    --cc=hadess@hadess.net \
    --cc=linux-input@atrey.karlin.mff.cuni.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.