backlight, brightness and contrast.
- Add 9 command key symbols which make wskbd to call wsdisplay's
iocontrol.
- Add special key map variant KB_MACHDEP. This variant does not
have any real keymap but it's just a placeholder for machine dependent
maps which will be overwrite by machine dependent keyboard driver.
from devices connected to pckbc:
- Do actual sample collection in pckbc.
- Add rndsource_element_t to the slot data.
- Change pckbc_set_inputhandler() to take an additional argument,
the name of the device, which is (eventually) passed into
rnd_attach_source() to identify the source.
- Change callers of pckbc_set_inputhander() appropriately.
a call to hook up a bell-ringer (since the keyboard itself has no bell).
This eliminates the need for #ifdefs for the bell-ringer in the pckbd
driver.
- Add cnbell() support to pckbd.
- Wsmouse_input() get new argument 'flag', which indicates whether x/y/z are
relative or absolute.
- Wsmouse get new io controls, WSMOUSEIO_SCALIBCOORDS and
WSMOUSEIO_GCALIBCOORDS.
before the elimination of typematic events.
This fixes the case where the "extended" prefix was not ignored and
affected the next keystroke. (seen with the AltGr key)
and ignore the error. Scanset 2 should be the default after reset, so
this allows some broken keyboards to work. (Reset is needed because at
least 1 keyboard locks up if the "set scanset" is attempted.)
might be called without process context, leading to tsleep() panics
(This is a workaround. The timeout() driven wscons glue code
should go instead.)
Fixes tsleep() panics reported by Mark Brinicombe <mark@causality.com>
and Eric Haszlakiewicz <haszlaki@UAccess.NET>.
(Nonaka Kimihiro): grave accent and @ were the wrong way
-assign keysyms to the special japanese conversion keys (even if this
doesn't help wscons - but things must have names)
"keypad-delete". (This is not completely clean; for me these keys make
up perhaps a "function field", but no "keypad".)
This is the mapping expected by applications.
Proposed by Chris Jones via PR kern/6089 and Dave Sainty.
as with user-land programs, include files are installed by each directory
in the tree that has includes to install. (This allows more flexibility
as to what gets installed, makes 'partial installs' easier, and gives us
more options as to which machines' includes get installed at any given
time.) The old SYS_INCLUDES={symlinks,copies} behaviours are _both_
still supported, though at least one bug in the 'symlinks' case is
fixed by this change. Include files can't be build before installation,
so directories that have includes as targets (e.g. dev/pci) have to move
those targets into a different Makefile.
as console input. (Previously, it did always succeed.)
(closes PR kern/5372 by Jason R Thorpe)
Make error messages cleaner and add some "#ifdef DEBUG" to reduce noise.
aymeric