HILKBD(4) BSD Kernel Interfaces Manual HILKBD(4)NAME
hilkbd -- HIL keyboard device
SYNOPSIS
hilkbd* at hil?
wskbd* at hilkbd?
option HILKBD_LAYOUT=XXX
DESCRIPTION
This driver supports HIL keyboards within the wscons(4) framework. It doesn't provide direct device driver entry points, but makes its func-
tions available through the internal wskbd(4) interface.
The hilkbd driver supports a number of different key mappings. By default, the layout corresponding to the keyboard model as probed by the
hilkbd driver will be used. A different layout can be chosen either with the kernel option ``HILKBD_LAYOUT'' at compile time, or with the
wsconsctl(8) utility (variable: ``keyboard.encoding'') at runtime.
The supported key mappings are at this time:
KB_DE (de) German with ``dead accents''.
KB_FR (fr) French with ``dead accents''.
KB_SV (sv) Swedish.
KB_UK (uk) British.
KB_US (us) English/US keyboard mapping.
The KB_DE mapping can be used in the KB_NODEAD (.nodead) variant. This switches off the ``dead accents''.
EXAMPLES
To set a Swedish keyboard mapping, use wsconsctl keyboard.encoding=sv. To set it at kernel build time, regardless of what keyboard is
plugged, add the following to the kernel configuration file:
option HILKBD_LAYOUT="KB_SV"
SEE ALSO hil(4), intro(4), wskbd(4), wsconsctl(8)BUGS
The list of built-in mappings is incomplete and has grown as people submitted information about their particular layout.
The Swedish and British layout have been reconstructed from tables in the old HIL code present in the hp300 port, and have not been tested.
BSD February 9, 2011 BSD
Check Out this Related Man Page
WSMUX(4) BSD Kernel Interfaces Manual WSMUX(4)NAME
wsmux -- console keyboard/mouse multiplexor for wscons
SYNOPSIS
wskbd* at ... mux 1
wsmouse* at ... mux 0
pseudo-device wsmux
DESCRIPTION
The wsmux is a pseudo-device driver that allows several wscons(4) input devices to have their events multiplexed into one stream.
The typical usage for this device is to have two multiplexors, one for mouse events and one for keyboard events. All wsmouse(4) devices
should direct their events to the mouse mux (normally 0) and all keyboard devices, except the console, should direct their events to the key-
board mux (normally 1). A device will send its events to the mux indicated by the mux locator. If none is given the device will not use a
multiplexor. The keyboard multiplexor should be connected to the display, using the wsconscfg(8) command. It will then receive all key-
strokes from all keyboards and, furthermore, keyboards can be dynamically attached and detached without further user interaction. In a simi-
lar way, the window system will open the mouse multiplexor and receive all mouse events; mice can also be dynamically attached and detached.
If a wskbd(4) or wsmouse(4) device is opened despite having a mux it will be detached from the mux.
It is also possible to inject events into a multiplexor from a user program.
FILES
For each mux device, /dev/wsmuxN there is a control device /dev/wsmuxctlN. The control device has a minor number 128 greater than the regu-
lar mux device. It can be used to control the mux even when it is open, e.g., by wsmuxctl(8).
/dev/wsmouse a.k.a. /dev/wsmux0
/dev/wskbd a.k.a. /dev/wsmux1
/usr/include/dev/wscons/wsconsio.h
SEE ALSO wscons(4), wsdisplay(4), wskbd(4), wsmouse(4), moused(8), wsconscfg(8), wsconsctl(8), wsfontload(8), wsmoused(8), wsmuxctl(8)BSD July 26, 1999 BSD
I like to know how to print accent when use the command lp -d <file>.
This <file> contain the following accents (e.g. é, á, ê, ã, ç) and anothers accents, please i need to help.
thank´s (0 Replies)
Hi all can you please help me what is dead.letter file ?
when it is created ? for the first time i have seen this file getting created in my current directory?
I am using SunOs.
Any IDEA ?? (2 Replies)
I Need help !
We changed a WS HP 715/33 the new is a HP 715/100 ! The old one supports a HIL keyboard and mouse. The "new" one PS2 keyboard.
We changed only the hardware not the harddisk - now the Xserver didn´t start !
What have we to configure thatt the WS supports the PS2 keyboard under... (0 Replies)
Hi, I've got a bit of a ridiculous problem and wasn't sure where to post it.
I need to use the vertical bar for piping in Bash but, as per the title, am using a UK layout on a US (physical) keyboard which doesn't have a key for it in the place I'd expect. I've tried using xbindkeys and Unicode... (7 Replies)