From owner-freebsd-current@freebsd.org Fri Jul 24 08:14:21 2015 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0DA019A8573 for ; Fri, 24 Jul 2015 08:14:21 +0000 (UTC) (envelope-from ljh8199@gmail.com) Received: from mail-pd0-x229.google.com (mail-pd0-x229.google.com [IPv6:2607:f8b0:400e:c02::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CA3351AA1 for ; Fri, 24 Jul 2015 08:14:20 +0000 (UTC) (envelope-from ljh8199@gmail.com) Received: by pdbnt7 with SMTP id nt7so10202729pdb.0 for ; Fri, 24 Jul 2015 01:14:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:user-agent:date:message-id:mime-version :content-type; bh=EmewAqnfgc37RKc1sxBoNyAW1JwH9tPkJoHilMS0tyA=; b=pIcnnOGtjYciEcwO1T8cGHrehPffgt8+v5gkUZ0F84g28J5zHsby/qZQV6pXRqKyBq OBCfPkDhhlWO46LPAaOeigXJC3LBfOAtwy6LnyXCG48V5sJUks2NK/SU3KKsdwIelpmp SCa3GATENs40WuAwCfQcQKZdQk+cmW66SAecWqAqZOEhQWa11lt4S87w8awjgI66Nk+F S3OkY7CLpVJhlnVqLyaTJPa5l7985DaxK0AFm2wcA1TlIwBwPRCob80USyLxlg1TgyP5 D6fC3gs4mT3J820HbOHyMOdQIckdnvITnGwwF1W/7tlikF9jvpDyKzL4HBzryAbn9BqK hldQ== X-Received: by 10.70.7.162 with SMTP id k2mr28184582pda.128.1437725659616; Fri, 24 Jul 2015 01:14:19 -0700 (PDT) Received: from m2r.lawsarang.net ([163.152.3.39]) by smtp.gmail.com with ESMTPSA id y2sm2946590pdi.80.2015.07.24.01.14.16 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 24 Jul 2015 01:14:18 -0700 (PDT) From: ljh8199@gmail.com (Lee, Jae Ho) To: freebsd-current@freebsd.org Subject: [Lee, Jae Ho] Re: Korean keyboard support User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (berkeley-unix) Date: Fri, 24 Jul 2015 17:14:04 +0900 Message-ID: <86mvymotv7.fsf@m2r.lawsarang.net> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 08:14:21 -0000 ( I redirect following post originally posted at freebsd-drivers to -current. ) > Lee, Jae Ho wrote this message on Fri, Jul 24, 2015 at 09:33 +0900: > > This is probably better suited for -current, so I have redirected > the question there... Dear John-Mark, thank you so much for your concern! I think I should send the original message to current. > It looks like FreeBSD may not have a keymap for Korean keyboards. > You can check by running kbdmap from the console... > > If you look at /usr/share/syscons/keymaps (older syscons), or > /usr/share/vt/keymaps (current vt, which supports UTF-8 fonts and > more), you can define your own keyboard map... > > It could be that I'm missing what you're trying to do... Hope > this helps! Well as far as the keymap, there has never been one for Korean keymap. I *think* the reason why for that is Korean keyboard shares exactly same keymap with us.kbd map and only uses xim applications such as korean/ko-uim to translate each alphabet input to Korean charactors. But only difference with Korean and us.kbd(US keymap) is those two toggle keys I mentioned in prior (original) message: Hangul(0xF2), Hanja(0xF1). The problem is, since those two keys have unique (but standard in Korean regulations or ISO ) key scancodes, default FreeBSD system/kernel may not detect those. I checked that by using misc/kbdscan program to see if those keys are detected by default system but did not print any keycodes. Also those keys could not even wake the system up when system screen is in powersave mode. So basically I think it's about driver problem rather about keymaps, and that is why I looked up sys/dev/atkbdc/atkbd.c. In short, those two unique keys in Korean keyborad are needed to be recognized by FreeBSD kernel first before we reorganize the keymaps file, to use Korean keyboard in FreeBSD. More detailed informations about scancodes , kernel patch info from linux and other features of those two keys are mentioned in original (prior) post, if anybody needs. Thank you very much again for your concern, and I hope you have a nice day. :~) (Below are original post at -drivers) ============================================================= Hello. I am Lee, Jaeho from South Korea. ( not North lol ) I am trying to ask you about the Korean keyboard support in FreeBSD. The Korean keyborad is featured as below. "The Korean keyboard has two keys, the Korean/Chinese and the Korean/English toggles, that generate scancodes f1 and f2 (respectively) when pressed, and nothing when released. They do not repeat. The keycaps are "hancha" and "han/yong" (written in Hangul). Hancha (hanja) means Chinese character, and Han/Yong is short for Hangul/Yongcha (Korean/English). They are located left and right of the space bar." ( From : http://www.win.tue.nl/~aeb/linux/kbd/scancodes-9.html ) Basically, on the Korean 103/106 (Korean Government Standard), there are two additional keys as Hangul(scancode of 0xf2) and Hanja(scancode of 0xf1) to the US 101/104 keyborad. and they don't have release signals if they are ps/2 type. USB keborad does have release signals. I tried look in src/sys/dev/atkbdc/atkbd.c and tried to make a patch on my own which I inspired by the patch from the linux kernel : https://bugzilla.kernel.org/show_bug.cgi?id=6642 , but since I am not well experienced yet in freebsd programing so I eventually came to ask for your help. I am ready to give you answers and informations to any kind of questions about Korean keybord specifications or other things related that you might want to know. :) As you can guess, the keyboard support is quite evident and will be really important and helpful to many Korean FreeBSD users. Thank you in advance. :) =========================================================