Newsgroups: comp.os.minix
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!spool.mu.edu!howland.reston.ans.net!tank.news.pipex.net!pipex!peer-news.britain.eu.net!uknet!pcl!ncfee
From: ncfee@westminster.ac.uk (Chris Ebenezer)
Subject: Re: changing NR_SCAN_CODES
Message-ID: <DKv4In.BpH@westminster.ac.uk>
Sender: news@westminster.ac.uk
Nntp-Posting-Host: leopard
Organization: University of Westminster
X-Newsreader: TIN [version 1.2 PL2]
References: <4cg8r5$9si@super.win.or.jp>
Date: Mon, 8 Jan 1996 12:39:58 GMT
Lines: 46

rrobins@waun.tdsnet.com wrote:
: Hello.

: I'm a Japanese Minix fan who are using Minix 1.7.1 on
: AT compatible with Japanese keyboard.

: I would like to request to the current Minix maintainer
: to change the value of NR_SCAN_CODES in minix/keymap.h

: NR_SCAN_CODES is defined as 0x69 in minix/keymap.h now.
: It means that Minix can handle the keyboard scan code
: from 0x00 to 0x68.

: On the other hand, Japanese keyboard (we call it Japanese
: 106 keyboard) has additional five keys compared to US
: standard 101 keyboards.

: The scan codes of additional five keys are:

: 	code  meanings
: 	----------------
: 	0x70  KANA
: 	0x73  BackSlash
: 	0x79  HENKAN
: 	0x7B  MU-HENKAN
: 	0x7D  YEN

: So, if we want to handle all keys in Japanese keyboard,
: we need more large value of NR_SCAN_CODES. We need at least
: 0x7E.

Presumably you could recompile your own kernel with these changes implemented
seeing as the kernel source is available ? Especially as you then wouldn't
have to count on someone else's understanding of what the problem actually
is ?

Chris.
--
    "You mean there are no traffic laws ?"
    "Of course there are, and occasionally one is enforced, to the 
     amazement of all."                  - Eto Demerezel.
============ncfee@wmin.ac.uk=======|=http://www.wmin.ac.uk/~ncfee=========
 

     

