linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Fox <pgf@laptop.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: keymap rule selection for non-DMI platforms
Date: Wed, 17 Aug 2011 03:32:02 +0000	[thread overview]
Message-ID: <22020.1313551922@foxharp.boston.ma.us> (raw)
In-Reply-To: <3483.1313087020@foxharp.boston.ma.us>

karl o. pinc wrote:
 > On 08/16/2011 05:54:04 PM, Daniel Drake wrote:
 > 
 > > However, to complicate things further with another item on our TODO
 > > list: OLPC offers the same identical laptop models with two alternate
 > > keyboards - membrane and mechanical. This is for both x86 and ARM
 > > models. At the moment, we use the same keymap for both even despite
 > > differences in the keys, but we plan to improve on this in future
 > > since it is a bug that keys do not behave according to the symbols
 > > printed on them!
 > > 
 > > There is no other difference in the laptop other than the keyboard, 
 > > so
 > > this information could not be captured in the bare-bones info
 > > presented in DMI or by the theoretical system mentioned above, unless
 > > we were to do something hacky like encode the keyboard model in the
 > > product_name.
 > 
 > I don't understand.
 > 
 > Why is it a hack to encode the keyboard model in the product name?
 > When the keyboard is part of the product and there's two different
 > keyboards (not just mechanically, but with different keymaps)
 > why isn't it 2 product models?

we have three laptop models, and something like 20 different
keyboards.  whether or not they all need different keymaps (they
don't), i think you can see why we might not necessarily encode any
of them as different models.

paul
=---------------------
 paul fox, pgf@laptop.org

      parent reply	other threads:[~2011-08-17  3:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-11 18:23 keymap rule selection for non-DMI platforms Paul Fox
2011-08-16 18:54 ` Paul Fox
2011-08-16 19:34 ` Kay Sievers
2011-08-16 20:09 ` Daniel Drake
2011-08-16 20:30 ` Kay Sievers
2011-08-16 20:39 ` Daniel Drake
2011-08-16 20:49 ` Paul Fox
2011-08-16 21:47 ` Greg KH
2011-08-16 22:27 ` Kay Sievers
2011-08-16 22:34 ` Kay Sievers
2011-08-16 22:37 ` Kay Sievers
2011-08-16 22:54 ` Daniel Drake
2011-08-16 23:35 ` Prarit Bhargava
2011-08-17  2:09 ` Karl O. Pinc
2011-08-17  3:32 ` Paul Fox [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=22020.1313551922@foxharp.boston.ma.us \
    --to=pgf@laptop.org \
    --cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).