Martin Lucina <mato@kotelna.sk> writes:

> dnkbd at frodo0 offset 0x0 not configured

It's not the keyboard but UART #0 of the Apollo Utility Chip which
is `found' here.  Not that it would matter ...

> and no amount of coaxing will get anything else out of it. So, is there a
> working version of the Domain Keyboard driver around (possibly in
> -current?)

A driver for the Domain/OS keyboard, derived from work contributed by
Michael Smith, currently exists in the SYS_INST code only.  The reason
for it still missing in the kernel source is that the structure of the
hp300's console interface code does not permit a clean integration of
this.

The way to resolve this is to convert the hp300 port to use the
reworked MI wscons facility: convert the framebuffer drivers into
devices which provide wsdisplay attachments, and abstract the current
HIL interface a bus interface which devices on the loop attach to and
provide interfaces to wscons keyboards and mice.  The latter is
currently being addressed by a third party that needs the restructured
interface, and they have indicated their wish to contribute their code
back to TNF; the former means mostly restructuring of existing code
and implementing display emulations.