From mboxrd@z Thu Jan 1 00:00:00 1970 From: Laurent Vivier Subject: Re: [PATCH] Paravirt framebuffer backend tools [2/5] Date: Thu, 07 Sep 2006 14:03:24 +0200 Message-ID: <45000A8C.90103@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> <44FFE702.7000609@bull.net> <20060907095529.GA3511@cam.ac.uk> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0166842847==" Return-path: In-Reply-To: <20060907095529.GA3511@cam.ac.uk> 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: Steven Smith Cc: Jeremy Katz , aliguori , xen-devel , sos22@srcf.ucam.org, Markus Armbruster List-Id: xen-devel@lists.xenproject.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --===============0166842847== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigFFF8710582C007655B4255F4" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigFFF8710582C007655B4255F4 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Steven Smith wrote: >>> 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._<--= - > Agreed. >=20 >>> Given that the backend knows exactly what each scancode is supposed t= o >>> 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. >=20 > 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. >=20 > You have to come up with some way of representing the keymap, but > at least for Linux that's already done for us. >=20 > Does this break anything? I think it's a good idea. But perhaps not really needed. Why ? Because generally people always uses same keyboard and you can set direct= ly in the logging environment to load a default keyboard mapping by account (li= ke a "loadkeys" in .bash_profile). For instance, french for my account, US for= your account or german for Gerd's account. If I have to connect to other one a= ccount (like "root", but the command "sudo" should allow to avoid that), I think= it is acceptable to have bad mapping. OK, it doesn't work for the logging screen (console login or xdm), but generally, on a site, all people uses same keyboard, so we can also set d= efault keyboard mapping at server level. An other solution is to force everyone on earth to use french keyboard ;-= ) (it's fine for me) 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 | --------------enigFFF8710582C007655B4255F4 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) iD8DBQFFAAqP9Kffa9pFVzwRAhKJAJ94McbqUy2W+xTp6zMnQJvo8cWOVACgrhE+ oZmhsNEBMIhPiIugBqjpv64= =nIFw -----END PGP SIGNATURE----- --------------enigFFF8710582C007655B4255F4-- --===============0166842847== 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 --===============0166842847==--