Re: Protocol wskbd vs. Protocol standard

[Matthieu Herrb <matthieu.herrb%laas.fr@localhost>]

On Sun, Jul 28, 2013 at 05:24:07PM +0200, Martin Husemann wrote:
> On Sun, Jul 28, 2013 at 11:40:40PM +0900, Izumi Tsutsui wrote:
> > Because all OpenBSD MD kernel keyboard drivers provide "rawmap"s
> > which return PC XT scancodes for X servers?
> 
> We seriously need to sit down and (1) spec and (2) implement finaly a
> real solution, e.g. based on USB scan codes or some superset of it and
> feed those to wsmux directly from the hardware driver, and also create
> a X keyboard driver to receive them in the same format from wsmux, and
> then not go through the horrifying levels of indirection inside X.
> 
> I want to run a sun kbd and a usb one through the same mux with a single
> X server!

Yes, OpenBSD implements a WSDISPLAY_COMPAT_RAWKBD option in most of
the platform specific keyboard drivers, to emulate raw PC-AT scan
codes for the X driver. 

However we are considering to change that because the choice
of PC-AT scan codes as the common ground (directed by how XFree86 did
the keyboard driver 15 years ago or so) was a poor idea. Those
scancodes are limited and their extensions for more multimedia keys
and is terrible hack.

I've not had enough time and energy to seriously start anything yet,
but other OpenBSD developpers have looked at it, without producing any
code so far. 

One point that always comes up is that we also need a way to handle
multiple keyboards connected to a mux with different layouts.
-- 
Matthieu Herrb