public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: Vojtech Pavlik <vojtech@suse.cz>, linux-kernel@vger.kernel.org
Subject: Re: Map extra keys on compaq evo
Date: Wed, 10 Nov 2004 18:11:15 +0100	[thread overview]
Message-ID: <20041110171115.GA1071@elf.ucw.cz> (raw)
In-Reply-To: <200411012318.45690.dtor_core@ameritech.net>

Hi!

> > > > With accurate list "hotkeys" could run with no configuration, but I am
> > > > afraid maintaining accurate list of keys for each keyboard is way too
> > > > much work.
> > > 
> > > The lists need to be kept _somewhere_, so why not have a userspace
> > > database with a program that loads the description into the kernel at
> > > boot, possibly using DMI as a hint to what keyboard is connected?
> > 
> > Doing dmi blacklist from userspace is going to be pretty
> > painfull... Kernel already has all the infrastructure.
> > 
> > My preference is forget about providing list of keys (it never worked
> > anyway), and just fixup few notebooks we know...
> 
> What about all those "multimedia" and "Internet" keyboards out there?
> 
> Plus I don't think using DMI is a good idea. Many people use 2 keyboards
> with their laptops - built-in and external and DMI mapping will sure be
> wrong for external keyboard. Theoretically it should be possible to have
> several completely independent keyboards (at least as far as
> keycodes go).

Well, I only filled unused spots in mapping table. So it should not
cause any problem unless you attach non-standard keyboard to your evo,
and even in such case I cause no regression... 
								Pavel
-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!

      parent reply	other threads:[~2004-11-11 11:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-31 21:38 Map extra keys on compaq evo Pavel Machek
2004-10-31 22:45 ` Brice Goglin
2004-11-01  1:16 ` Dmitry Torokhov
2004-11-01  8:03   ` Pavel Machek
2004-11-01  9:38     ` Vojtech Pavlik
2004-11-01 13:32       ` Pavel Machek
2004-11-01 14:07         ` Vojtech Pavlik
2004-11-01 17:28           ` Pavel Machek
2004-11-02  4:18             ` Dmitry Torokhov
2004-11-02  9:31               ` Stelian Pop
2004-11-10 17:11               ` Pavel Machek [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=20041110171115.GA1071@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --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