[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH] Paravirt framebuffer backend tools [2/5]
Gerd Hoffmann wrote: > Hi, > >> (2) Simply use the host's raw keys. >> >> The guest needs to understand the host's raw keys, and map them if >> they differ from its own idea of raw keys. At this time, the only >> idea of raw keys in town is Linux keycodes, so no mapping is >> necessary. >> >> Nice: simple & stupid. >> >> Unless I misunderstand Anthony, that's what rdesktop and qemu do. > > <unimportant side node> > Well, there are some corner cases where you can't easily get the hosts > raw keys. In that case qemu tries to translate the keysyms back to > raw keycodes using the maps in /usr/share/qemu/keymaps. See also qemu > manpage, "-k" switch. > </> > > But, yes, using linux keycodes as wire encoding IMHO is the way to go. > > cheers, > Gerd > So, perhaps the patch I post sometime ago on this subject should be useful ? Laurent -- Laurent.Vivier@xxxxxxxx +----- "Any sufficiently advanced technology is ----+ | indistinguishable from magic." - Arthur C. Clarke | Attachment:
signature.asc _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |