From owner-freebsd-bugs Mon Feb 10 22:16:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA01491 for bugs-outgoing; Mon, 10 Feb 1997 22:16:56 -0800 (PST) Received: from bugs.us.dell.com (bugs.us.dell.com [143.166.169.147]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id WAA01485 for ; Mon, 10 Feb 1997 22:16:50 -0800 (PST) Received: from moth.us.dell.com (moth.us.dell.com [143.166.169.152]) by bugs.us.dell.com (8.6.12/8.6.12) with SMTP id AAA09757; Tue, 11 Feb 1997 00:15:31 -0600 Message-Id: <3.0.1.32.19970211001523.006a17b8@bugs.us.dell.com> X-Sender: tony@bugs.us.dell.com X-Mailer: Windows Eudora Light Version 3.0.1 beta 12 (32) Date: Tue, 11 Feb 1997 00:15:23 -0600 To: Kazutaka YOKOTA From: Tony Overfield Subject: Re: psm and kbdio driver (was Re: Stuck! 2.2 Gamma won't go.) Cc: bugs@freebsd.org In-Reply-To: <199702110559.OAA05547@zodiac.mech.utsunomiya-u.ac.jp> References: Your message of "Mon, 10 Feb 1997 05:15:54 CST." <3.0.1.32.19970210051554.006a2350@bugs.us.dell.com> <3.0.1.32.19970210022848.00691d20@bugs.us.dell.com> <3.0.1.32.19970210051554.006a2350@bugs.us.dell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >If I ask some qustions regarding the keyboard controller, would you be >kind enough to answer them and assist me to improve the psm and kbdio >drivers? > >I really want several points clarified about the keyboard/mouse/i8042. Go ahead, I'll help with anything I can. My experience has been primarily focused on moving the data to and from the keyboard and mouse devices through the keyboard controller, not so much on what the data within those packets actually is. Should we find a more appropriate mailing list or should we go to direct e-mail? >PS. as for XF86Setup problems you are experiencing, I reproduced the >problem on my system I'm glad to hear this. It seems as though there could be a shift or other meta state (someone suggested a mouse button down state) that could be stuck, causing the keyboard keys to be "shifted" in such a way that they didn't map to their ordinary functions. - Tony