From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3] Input: keyboard - add device tree bindings for simple key matrixes
Date: Tue, 3 Jan 2012 17:06:15 +0000 [thread overview]
Message-ID: <20120103170615.GZ2914@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20120103164431.GA31647@core.coreip.homeip.net>
On Tue, Jan 03, 2012 at 08:44:32AM -0800, Dmitry Torokhov wrote:
> On Tue, Jan 03, 2012 at 04:29:30PM +0000, Russell King - ARM Linux wrote:
> > On Tue, Jan 03, 2012 at 08:22:21AM -0800, Simon Glass wrote:
> > > Can the Linux key codes fit in 8 bits?
> >
> > That depends on your point of view.
> >
> > If you hack on X, then the answer is yes and you ignore the squeels of
> > your users when certain key presses get misinterpreted. (The Psion LX
> > platform, otherwise known as the Netbook Pro, suffered with this problem.)
> >
> > If you are a kernel hacker, the answer is no, because key codes currently
> > go all the way to 0x300.
>
> For bootloader environment 0-255 range is probably sufficient though,
> the upper keys are somewhat recent additions to the maps...
I assume you deem 'recent' to mean 8 years ago - they've been there since
at least 2.6.9, which is where the problem I refer to above was first
noticed.
next prev parent reply other threads:[~2012-01-03 17:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1325184146-3527-1-git-send-email-olof@lixom.net>
[not found] ` <1325484557-27695-1-git-send-email-olof@lixom.net>
2012-01-02 18:39 ` [U-Boot] [PATCH v3] Input: keyboard - add device tree bindings for simple key matrixes Simon Glass
2012-01-03 15:43 ` Olof Johansson
2012-01-03 16:22 ` Simon Glass
2012-01-03 16:29 ` Russell King - ARM Linux
2012-01-03 16:44 ` Dmitry Torokhov
2012-01-03 16:48 ` Olof Johansson
2012-01-03 17:06 ` Russell King - ARM Linux [this message]
2012-01-03 17:57 ` Dmitry Torokhov
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=20120103170615.GZ2914@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=u-boot@lists.denx.de \
/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