From owner-freebsd-current@FreeBSD.ORG Mon May 23 22:38:03 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D2EC16A41C for ; Mon, 23 May 2005 22:38:03 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC49343D1D for ; Mon, 23 May 2005 22:38:02 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from localhost (localhost.localdomain [127.0.0.1]) by mailgate1b.savvis.net (Postfix) with ESMTP id 44D5D3BE8E; Mon, 23 May 2005 17:38:02 -0500 (CDT) Received: from mailgate1b.savvis.net ([127.0.0.1]) by localhost (mailgate1b.savvis.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 05858-01-66; Mon, 23 May 2005 17:38:02 -0500 (CDT) Received: from out002.email.savvis.net (out002.apptix.savvis.net [216.91.32.45]) by mailgate1b.savvis.net (Postfix) with ESMTP id 17FF93BE88; Mon, 23 May 2005 17:38:02 -0500 (CDT) Received: from s228130hz1ew031.apptix-01.savvis.net ([10.146.4.28]) by out002.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Mon, 23 May 2005 17:37:43 -0500 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew031.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Mon, 23 May 2005 17:37:43 -0500 Message-ID: <42925B36.9090400@savvis.net> Date: Mon, 23 May 2005 15:37:42 -0700 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Alexandre \"Sunny\" Kovalenko" References: <4288EBEA.5030701@savvis.net> <428A5A58.6010601@savvis.net> <428B7B99.7080206@savvis.net> <428E7BAF.200@savvis.net> <1116788908.824.23.camel@RabbitsDen> <429211C9.4000903@savvis.net> <1116885956.3386.10.camel@RabbitsDen> In-Reply-To: <1116885956.3386.10.camel@RabbitsDen> Content-Type: text/plain; charset=ISO-8859-5; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 23 May 2005 22:37:43.0808 (UTC) FILETIME=[0901A000:01C55FE8] X-Virus-Scanned: amavisd-new at savvis.net Cc: freebsd-current@freebsd.org Subject: Re: keyboard mux driver (straw man proposal & code) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 23 May 2005 22:38:03 -0000 Alexandre, >>> -- "Caps lock" would capitalize main keyboard (there are no >>> letters on the keypad). >> >> "caps lock" on keypad or main keyboard? i'm not sure i understand >> the problem. > > Sorry for not being clear -- it was mere statement of fact, not > report of the problem. I guess, it should have said: ...despite LED > not being lit, "caps lock" did capitalize keys on the main keyboard. > Keypad does not have "caps lock" or "num lock". now i get it :) just like i explained in previous email keyboard lights will not work for now. kbdmux does not call SETLED ioctl on slave keyboards yet. >>> -- "Num lock" would switch keypad into numeric mode, but leave >>> main keyboard alone (as it is the case with laptop keyboards it >>> has sprinkling of numerals on the right side overlapping >>> letters). >> >> again "num lock" on keypad or main keyboard? > > "Num lock" on the main keyboard (keypad does not have one) switches > *keypad* into numeric mode leaving main keyboard in alpha -- main > keyboard does not really have a numeric part -- it overlaps some of > the alpha keys. this is actually correct (i think). because slave keyboards are set to K_RAW mode, kbdmux will get raw scancodes, not characters. the (good or bad?) side effect of this is that kbdmux will act as if it was one huge keyboard with lots of duplicated keys :) that is you should be able to press "ctrl" on one keyboard and "c" on another keyboard but it will still look like you pressed ctrl+c on the same keyboard :) the keypad is probably programmed to send the same scancodes as normal 101/102-keys keyboard would. that is for the group of keys on the right side (numeric keypad typically found under the keyboard lights). as in 101/102-keys keyboard case hitting numlock will only switch this group of keys between numbers/arrows. i guess this gives an answer to what to do with SETLED ioctl. kbdmux probably should send SETLED ioctl to all slave keyboards. that is hitting capslock on one keyboard should set capslock on all keyboards. >> thanks again for trying this and reporting the problems. i will try >> to get myself a couple of usb keyboards and reproduce/fix the >> problems. > > If you are in or somewhere near :) continental US, send me your > address in the private mail -- I'll ship you that keypad. actually Eric Anderson is going to send me a couple of usb keyboards. he said he has a pile of them :) is this the keypad you currently have? http://www.walmart.com/catalog/product.gsp?product_id=3380773&sourceid=11790802501271934686 thanks, max