Date: Wed, 22 Jun 2005 17:26:20 -0700 From: Maksim Yevmenkin <maksim.yevmenkin@savvis.net> To: Norbert Koch <NKoch@demig.de> Cc: "Freebsd-Hackers@Freebsd.Org" <freebsd-hackers@freebsd.org> Subject: Re: using vkbd device Message-ID: <42BA01AC.3030806@savvis.net> In-Reply-To: <000001c57727$43c5e600$4801a8c0@ws-ew-3.W2KDEMIG> References: <000001c57727$43c5e600$4801a8c0@ws-ew-3.W2KDEMIG>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello Norbert, > I did some more testing with kbdmux. > > 1. I wait for the screen saver becoming active. > 2. I press the control key. > 3. All keys, I press after that, > come as control keys, e.g. > I press 'j' or 'J' and see a > linefeed, I press 'I' and see a tab. > 4. I wait a second time for the screen saver. > 5. I press control. > 6. The keys are ok now. > > Does syscons eat up the key but > sets the state in kbdmux? hmmm... i can not reproduce it here (on -current). could you please try the latest code. i have included some of your patches and did a compile only test on 4.x system (freefall.freebsd.org). http://www.geocities.com/m_evmenkin/kbdmux-3.tar.gz it also fixes (hopefully) issues with state synchronization (lights, etc.). thanks, max
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42BA01AC.3030806>