From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: 3.0.3 without X Date: Thu, 04 Jan 2007 15:17:02 -0600 Message-ID: <459D6ECE.2040809@codemonkey.ws> References: <13426df10701040658x642246e7y555377ff7499d381@mail.gmail.com> <20070104153202.GB9172@leeni.uk.xensource.com> <459D5661.6020004@codemonkey.ws> <20070104194829.GA15265@leeni.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20070104194829.GA15265@leeni.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ewan Mellor Cc: ron minnich , xen-devel , jason List-Id: xen-devel@lists.xenproject.org Ewan Mellor wrote: > On Thu, Jan 04, 2007 at 01:32:49PM -0600, Anthony Liguori wrote: > >> Ewan Mellor wrote: >>> On Thu, Jan 04, 2007 at 03:01:08PM +0000, Keir Fraser wrote: >>> >>>> On 4/1/07 14:58, "ron minnich" wrote: >>>> >>>>> note that we're distributing an x11-free xen for plan 9 support, so I >>>>> sure hope that x11 dependencies are not about to start appearing in >>>>> xen. >>>> The dependencies are only in HVM-specific bits of the tools/ directory. >>>> Those are easily disabled, albeit with a smidgen of Makefile changes. >>> They also aren't really X11 dependencies. That code includes >>> , because VNC uses the same keysyms as X, but there's no >>> dependency upon X client libraries. >> This dependency is actually a bug that was introduced in the Xen tree >> (it isn't present in qemu CVS). >> >> The VNC spec makes it pretty clear that you cannot rely on the symbolic >> names of X keycodes to develop a portable VNC client. Apparently they >> change slightly across different X implementations. > >>>From www.realvnc.com/docs/rfbproto.pdf: > > "The key itself is specified using the "keysym" values defined by the X Window > System. > > For most ordinary keys, the "keysym" is the same as the corresponding > ASCII value. For full details, see The Xlib Reference Manual, published by > O'Reilly & Associates, or see the header file from any X > Window System installation." And then shortly following it goes on to describe how a number of keys are not universally represented like a backwards tab. > > How do we choose which X keysyms to use, if they vary across X > implementations? By choosing keysyms that are known to work and not relying on buggy X implementations. Regards, Anthony Liguori > Ewan.