All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Haxby <john.haxby@oracle.com>
To: Pat Campbell <plc@novell.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 0 of 2] Fix keymap handling for vnc console
Date: Mon, 01 Dec 2008 14:42:40 +0000	[thread overview]
Message-ID: <4933F7E0.2040309@oracle.com> (raw)
In-Reply-To: <4922E5B6.5010308@novell.com>

Pat Campbell wrote:
> Are the keymap files and vnc_keysym.h changes independent of the code
> changes?   Not sure what others think but if they are independent then
> there should be two distinct patch sets.  One for keysmaps and
> vnc_keysym.h and another for the keysym/scancode handling. 
>
>   
Yes, the changes are reasonably independent although one shouldn't use 
the updated keymaps without the corresponding keymap/scancode handling 
because duplicate keysyms cause problems with the current code.

> Although not as inclusive, I see some vnc_keysym.h changes have been
> recently sent upstream to qemu-devel. Are you going to send a derivative
> of this patch set upstream to qemu-devel? 
>   [Qemu-devel] AltGr and dead keys with VNC                 
>   
Those keysyms are indeed present in my patch; the iso-level3-switch 
change is already part of the xen code.

> (vnc_keysym.h patch)
>   [Qemu-devel] Wrong keyboard mapping for Belgian keyboard  (bug report)
>
>   
That's a familiar looking bug report.   The problem described there is 
the problem with duplicate keysyms in the keymap which the original code 
completely failed to address.

I'll try to assemble a similar patch to this one and send it up to 
qemu-devel.
> I would be interested in your two programs.
>
>   
I'll post those shortly as well.

jch

      reply	other threads:[~2008-12-01 14:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-14 17:31 [PATCH 0 of 2] Fix keymap handling for vnc console John Haxby
2008-11-18 15:56 ` Pat Campbell
2008-12-01 14:42   ` John Haxby [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4933F7E0.2040309@oracle.com \
    --to=john.haxby@oracle.com \
    --cc=plc@novell.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.