From mboxrd@z Thu Jan 1 00:00:00 1970 From: Laurent Vivier Subject: Re: [PATCH] Paravirt framebuffer backend tools [2/5] Date: Fri, 08 Sep 2006 16:00:27 +0200 Message-ID: <4501777B.7050206@bull.net> References: <20060904090150.GC4812@cam.ac.uk> <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> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2023597560==" Return-path: In-Reply-To: <45016F8E.1030300@cs.utexas.edu> 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: Anthony Liguori Cc: Jeremy Katz , xen-devel , Markus Armbruster , sos22@srcf.ucam.org List-Id: xen-devel@lists.xenproject.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --===============2023597560== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig066C8CD966C8E5BCAE99CB6B" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig066C8CD966C8E5BCAE99CB6B Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Anthony Liguori wrote: > Steven Smith wrote: >> First: I now agree with you that scancodes are a better choice than >> keysyms, and that I was wrong initially. >=20 > The problem with scancodes is that you cannot always get scancodes from= > the viewer. You can get scancodes from SDL but you can only get keysym= s Right. > from VNC. We would have to map VNC keysyms (which are just Xk keysyms)= > to scancodes? It's what we already did: KEY_* are scancodes. It's why it should be better to get scancodes from the viewer, not keysym= s. Currently: we get keysyms from VNC and SDL and we translate to scancode for linux ke= rnel. What I propose: we get scancode from SDL and we translate to scancode for linux kernel. We must keep keysyms from VNC because we can't have scancode from VNC cli= ent. > I'm a bit surprised here. If we generate a KEY_Q event in Linux that > may show up as a KEY_A key? There are keysyms for all the extended key= s > I thought. I'm sorry but I think you didn't understand the issue: we must provide sc= ancode to frontend keyboard driver (KEY_*), and the current issue is in translat= ing keysyms to scancode. Please have look at all previous e-mails... Regards, Laurent --=20 Laurent.Vivier@bull.net Bull, Architect of an Open World (TM) +----- "Any sufficiently advanced technology is ----+ | indistinguishable from magic." - Arthur C. Clarke | --------------enig066C8CD966C8E5BCAE99CB6B Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.7 (GNU/Linux) iD8DBQFFAXeA9Kffa9pFVzwRAt9gAKCmdL6mvOcx8/oYDRBOoVm/qFf4cgCgh8q8 EgEjrVbVTb36C1/vjhRrlO0= =rJrL -----END PGP SIGNATURE----- --------------enig066C8CD966C8E5BCAE99CB6B-- --===============2023597560== 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 --===============2023597560==--