> > It'd be nice if, from both machines, pressing the key labelled 'w' on
> > the keyboard resulted in a 'w' being sent to whatever application is
> > reading from the keyboard at the time.
> --->_I think it's better to have bad mapping than missing symbols._<---
> > Given that the backend knows exactly what each scancode is supposed to
> > map to, we should in principle be able to avoid this sort of problem.
> > It's just a matter of connecting everything up correctly. :)
> No, I'm sorry, I don't think so.
Okay, dumbest possible solution: the backend queries the local X
server for its keymap, and publishes that in xenbus. You then have
some userspace application running in the guest domain which looks at
that and does xmodmap or loadkeys as appropriate.
This is really rather distasteful, but I think it allows every key
which can be typed on the backend keyboard to be transmitted to the
frontend and rendered correctly there.
You have to come up with some way of representing the keymap, but
at least for Linux that's already done for us.
Does this break anything?
> Except, perhaps, if you send UTF-8 directly from backend to frontend
> without translating it. But it supposes that frontend keyboard
> driver is able to manage UTF-8 instead of linux scancode. But it
> will work with console not with X11. I think X11 is working with
> scancode too. It will be very messy...
Yeah, we don't want to go down that path.
Description: Digital signature
Xen-devel mailing list