Message-ID: <4575D2E5.3000401@tmr.com>
Date: Tue, 05 Dec 2006 15:13:25 -0500
From: Bill Davidsen <davidsen@tmr.com>
Organization: TMR Associates Inc, Schenectady NY
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.8) Gecko/20061105 SeaMonkey/1.0.6
MIME-Version: 1.0
To: Florian Festi <florian@festi.info>,
       Linux Kernel mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Meaning of keycodes unclear
References: <45753BB1.6030102@festi.info>
In-Reply-To: <45753BB1.6030102@festi.info>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1060
Lines: 26

Florian Festi wrote:
> I am looking for the meaning of the following key codes as #defined in 
> include/linux/input.h. I need to know what hardware produces the keycode 
> and what happens/should happen when the corresponding key is pressed.

> KEY_MACRO

I presume this is the macro defining key, used on keyboards like the 
Gateway102. I thought it was handled internally and didn't send a 
keycode, but other keyboards had/have that feature as well.

Used G102 for application work, had the function keys both next-to and 
above the alpha keys, so you could bind up to 48 application functions 
and still have function keys as other things wanted them.

Hope that answers your question.

-- 
bill davidsen <davidsen@tmr.com>
   CTO TMR Associates, Inc
   Doing interesting things with small computers since 1979
-
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/