| Age | Commit message (Collapse) | Author |
|---|
|
interrupt context.
|
|
|
|
change.
|
|
X11R5 server, untested.
|
|
|
|
On hp300, hil would claim console against dnkbd if no dnkbd was found at
the time the loop is probed, even if the loop is empty. Because of this,
plugging dnkbd later would not select it as console keyboard, which is
really annoying on kernels without wsmux, such as hp300 RAMDISK.
Now the first keyboard plugged will become the console keyboard, whatever
its type.
No functional change on hppa, since the console path gives a definite console
device setting.
|
|
is marked as busy.
|
|
|
|
hilkbd will still match both, but will neither do the auto-layout dance nor
attach as console for button boxens.
|
|
until the loop has reconfigured into a stable state. This can save up
unnecessary detach/attach cycles for the low ids in the loop.
|
|
|
|
international flavours, so provide two sets of mappings.
|
|
|
|
|
|
keyboard sv map error spotted by Jan Johansson.
|
|
|
|
we can react on post-boot device plugs.
|
|
- Let the loop initialize completely before attempting to probe its devices.
Fixes the "no answer from device 1" problem.
- Handle ``loop unplugged'' events and force detach of all children in this
case.
|
|
applicable.
During device probe, if a device does not answer commands, display a warning
message. This apparently happens on hp300 when the console is configured
as remote (i.e. serial console). Unplugging and replugging the device works
fine afterwards...
|
|
|
|
|
|
layout.
Based upon an old diff from paul@, tests and feedback otto@ paul@
|
|
behave correctly for some reason.
|
|
|
|
|
|
rescinded 22 July 1999. Proofed by myself and Theo.
|
|
and ok
|
|
but XFree did.
|
|
|
|
|
|
pad and a few extra keys).
|
|
at runtime.
Handle reconfiguration notices from the loop, and do the necessary
detach/attach work so that our vision of the loop is in sync with reality.
Adapt all hil child devices to the above changes.
"This is not as plug'n'play as usb, but you get the same feeling anyways..."
|
|
glitch.
|
|
|
|
Still a minor issue left for tomorrow.
|
|
Also, better probe for leds on keyboard.
|
|
devices.
The ID module only purpose is to provide a small, unique, bitstring, which
was used for some copy-protection or licensing scheme under HP-UX.
Right now this driver is useless, as it provides no way to communicate
this information to userland, and only displays it while attaching, as such:
hilid0 at hil0 code 2: ID module
hilid0: security code 10 04 b4 41 ac 77 14 0f 41 00 00 00 00 00 00 00
hilid1 at hil0 code 3: ID module
hilid1: security code 10 04 b4 41 e3 b8 13 0f 41 00 00 00 00 00 00 00
Too bad it's not even good enough to feed the kernel random generator...
|
|
kernels to attach hilkbd0 (console keyboard) or hilms0 (main mouse) to
a specific device in the loop, by using UKC or compiling a new kernel.
Using this and the previous console changes, it is now possible on a loop
with multiple keyboards, to choose which keyboard will be the console
keyboard.
|
|
- only attach a keyboard as a console if it matches the PDC keyboard path
- on hil, as there can be multiple keyboards on the loop, attach only the
first hilkbd device configured as console keyboard. Right now this means
the one with the lowest hil code, which was the existing behaviour so far.
- do not try to switch to the wscons consdev structure early at all in
wscons_machdep, but rather wait for the console to be completely
configured (i.e. both wskbd and wsdisplay are attached) to switch.
With feedback and help from mickey@
|
|
do not stick to u_int8_t when native word size can do the job better.
- Allow send_hildev_cmd() to return the command response buffer to its
caller, rather than forcing it to look at the guts of its parent device
softc... this will be needed shortly.
|
|
|
|
done by the loop, this is mostly an HIL packet decoding routine.
|
|
names.
|
|
Nobody will want to use such a keyboard anyways, as there is no ~ (tilde)
key on it.
|
|
|
|
|
|
Derived from the hp300 HIL code, and some information found in XFree86
HP-UX specific parts.
However, this code does not provide an HP-UX compatible /dev/hil* interface,
but will rather attach real BSD drivers to the hil driver glue.
Currently, only a driver for the HP-HIL keyboards is provided. More to come
as resources permit.
The international layout tables for hilkbd are derived from the ite tables
found in the hp300 code, but only the US layout could be tested.
Sample dmesg output on a heavily charged hil loop:
hil0 at gsc0 offset 21000 irq 1
hilkbd0 at hil0 code 1: 109-key keyboard, layout 1b
wskbd0 at hilkbd0: console keyboard
hilkbd1 at hil0 code 2: 109-key keyboard, layout 1f
wskbd1 at hilkbd1
"ID module" at hil0 id 34 code 3 not configured
"ID module" at hil0 id 34 code 4 not configured
"Tablet" at hil0 id 94 code 5 not configured
"Mouse" at hil0 id 68 code 6 not configured
Some feedback from and ok mickey@
|
