From mint-bounce@lists.fishpool.fi  Sun Aug 30 13:56:22 2009
Message-ID: <4A9ABC95.2050007@online.no>
Date: Sun, 30 Aug 2009 19:53:25 +0200
From: Jo Even Skarstein <joska@online.no>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: mint@lists.fishpool.fi
Subject: Re: [MiNT] Alt keymap (Ozk: Read this if you're here!)
References: <4A9A8DDE.1000300@freesbee.fr> <4A9A9733.3090209@online.no> <4A9A99D0.1080407@freesbee.fr> <4A9AB741.4000604@online.no>
In-Reply-To: <4A9AB741.4000604@online.no>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ecartis-version: Ecartis v1.0.0
Sender: mint-bounce@lists.fishpool.fi
Errors-to: mint-bounce@lists.fishpool.fi
X-original-sender: joska@online.no
Precedence: bulk
List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
List-Id: <mint.lists.fishpool.fi>
X-List-ID: <mint.lists.fishpool.fi>
List-subscribe: <mailto:mint-request@lists.fishpool.fi?Subject=subscribe>
List-owner: <mailto:tjhukkan@fishpool.fi>
List-post: <mailto:mint@lists.fishpool.fi>

Jo Even Skarstein skreiv:

> Just tried this on my Milan, and the samme happens here. It applies to 
> the scancodes 0x02 -> 0x0d. I assume this is a MiNT-problem, I will take 
> a look in keyboard.c.

Ok, found this:

/* Ozk:
  * Scan codes between 0x02 -> 0x0d are modified by 0x76
  */
if (scan >= 0x02 && scan <= 0x0d)
	scan += 0x76;

This is done in the IKBD-handler in keyboard.c when ALT is pressed. Why? 
  I could easily modify KeyEdit to add 0x76 to the scancode to these 
keys in the ALT-tables, but I really would like to know why the scancode 
is altered in the first place. I have never seen this documented anywhere.

Jo Even