Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 03 Jun 2005 09:45:19 -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:  <42A0891F.8080800@savvis.net>
In-Reply-To: <000001c5681f$9a5eb4e0$4801a8c0@ws-ew-3.W2KDEMIG>
References:  <000001c5681f$9a5eb4e0$4801a8c0@ws-ew-3.W2KDEMIG>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
Norbert,

> I am trying to use vkbd to multiplex
> an at keyboard and an usb keyboard
> into syscons.

ok

> Vkbd's control device's write routine
> expects ints to queue to the slave device.

correct

> As I understand, those ints map 1:1
> to the chars I read from a keyboard device, right?

yes, the ints should represent AT keyboard scancodes.

> So I open, for example, /dev/kbd0, set it to K_RAW,
> read chars from it and write them as ints to
> vkbd's control device, right?

yes, it should work. keep in mind that vkbd(4) emulates only one 
keyboard and keeps only one state. that is if you feed scancodes from 
multiple sources into the same vkbd(4) then it will look like one huge 
keyboard with lots of duplicated keys. so you can press shift/ctrl/alt 
on one keyboard and actual key on another, but it still will look like 
you have presses the keys on the same keyboard.

you also might want to look at experimental keyboard mux drivers. it is 
based on vkbd(4) and uses the idea of one super-keyboard that consumes 
scancodes from other keyboards. there are still a few issues i need to 
fix, but, in general, it works.

http://www.geocities.com/m_evmenkin/kbdmux-2.tar.gz

thanks,
max



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?42A0891F.8080800>