From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steven Smith Subject: Re: [PATCH] Paravirt framebuffer backend tools [2/5] Date: Tue, 10 Oct 2006 19:48:02 +0100 Message-ID: <20061010184802.GA5338@cam.ac.uk> References: <44FC224D.3090300@bull.net> <20060906091505.GD3257@cam.ac.uk> <44FEB3DE.5070502@bull.net> <20060906171006.GA5306@cam.ac.uk> <44FFCAC0.6060809@bull.net> <20060907083848.GA3078@cam.ac.uk> <45016F8E.1030300@cs.utexas.edu> <20060908141248.GA6845@cam.ac.uk> <45017CCF.9050707@cs.utexas.edu> <87psd4ul5c.fsf@pike.pond.sub.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1113727003==" Return-path: In-Reply-To: <87psd4ul5c.fsf@pike.pond.sub.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Mime-version: 1.0 Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Markus Armbruster Cc: Laurent Vivier , xen-devel , Anthony Liguori , sos22@srcf.ucam.org, Jeremy Katz List-Id: xen-devel@lists.xenproject.org --===============1113727003== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0F1p//8PRICkK4MW" Content-Disposition: inline --0F1p//8PRICkK4MW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable > The backend gets keys in an encoding that depends on the software used > to access the keyboard: =2E.. > The frontend needs to stuff Linux keycodes into the input layer. >=20 > Our job is to translate from frontend keysyms to Linux keycodes, and > the question is to find out how and where. I think you mean backend keysyms, but, yes, that's the basic issue. > Translating SDL_keysym.scancode into Linux keycode should be > straightforward, but translating X11 keysyms isn't. Steven mentioned > code in rdesktop that does that, and Anthony pointed to QEMU. >=20 > It would be nice to encapsulate all knowledge about frontend keysyms > in the frontends, i.e. to translate to a common wire encoding there. > Any reason why that's not the way to go? Any reason why the wire > encoding can't (or shouldn't) be simply Linux keycodes? The main objection to sending Linux keycodes over the wire is that their meaning depends on the keymap currently loaded. This could cause some problems if the machine running VNC viewer is using a different keymap to the one loaded in the frontend. However, every other solution that's been suggested has lead to some keys being unrepresentable, which is even worse. Steven. --0F1p//8PRICkK4MW Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFK+riO4S8/gLNrjcRAh1pAKDK1BdIR8GMpqR1L7iqgd2iOy0sfgCgsOds AKaxD2aAegYvxDkbZxyzaIY= =vIiT -----END PGP SIGNATURE----- --0F1p//8PRICkK4MW-- --===============1113727003== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============1113727003==--