Date: Fri, 3 Mar 2006 14:52:33 -0500 (EST)
From: "Ian E. Morgan" <imorgan@webcon.ca>
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>
cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Setkeycodes w/ keycode >= 0x100 ?
In-Reply-To: <Pine.LNX.4.61.0603031418530.4130@chaos.analogic.com>
Message-ID: <Pine.LNX.4.64.0603031448170.26582@light.int.webcon.net>
References: <Pine.LNX.4.64.0603031241130.15776@light.int.webcon.net>
 <Pine.LNX.4.61.0603031322410.18198@chaos.analogic.com>
 <Pine.LNX.4.64.0603031343270.15776@light.int.webcon.net>
 <Pine.LNX.4.61.0603031418530.4130@chaos.analogic.com>
Organization: Webcon, Inc
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1140
Lines: 27

On Fri, 3 Mar 2006, linux-os (Dick Johnson) wrote:

> Well the input.h in the distribution I use, has the highest key-code
> as KEY_UNKNOWN and that is number 200. Perhaps you are trying to
> use BTN_0 through BTN_N as key codes? Or perhaps there is some
> unfinished business in your version of headers?

Irrespective of distro, recent kernel (2.6.15.5) headers have KEY_MAX as
0x1ff (511). Incidentally, my glibc headers have the same thing.

You must have very old headers, as here KEY_PLAYCD=200, KEY_UNKNOWN=240, and
KEY_MAX=0x1ff.

Regards,
Ian Morgan

-- 
-------------------------------------------------------------------
 Ian E. Morgan          Vice President & C.O.O.       Webcon, Inc.
 imorgan at webcon dot ca       PGP: #2DA40D07       www.webcon.ca
    *  Customized Linux Network Solutions for your Business  *
-------------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/