From: Keir Fraser <keir@xensource.com>
To: Kasai Takanori <kasai.takanori@jp.fujitsu.com>,
Keir Fraser <keir@xensource.com>,
"Daniel P. Berrange" <berrange@redhat.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] Enable uppercase letters to be entered in QEMU monitor terminal
Date: Wed, 20 Dec 2006 11:19:42 +0000 [thread overview]
Message-ID: <C1AECCCE.6A1F%keir@xensource.com> (raw)
In-Reply-To: <22c901c72428$1f8a2f30$dab2220a@VF03007L>
It's been checked in since November.
-- Keir
On 20/12/06 11:15, "Kasai Takanori" <kasai.takanori@jp.fujitsu.com> wrote:
> Hi Keir and Daniel,
>
> I also found the same problem and tested this patch.
> I confirmed it was solved by this patch.
> I hope for this patch to be applied.
>
> Thanks
>
> --
> Takanori Kasai
>
>
> ----- Original Message -----
> From: "Keir Fraser" <keir@xensource.com>
> To: "Daniel P. Berrange" <berrange@redhat.com>; "Keir Fraser"
> <keir@xensource.com>
> Cc: <xen-devel@lists.xensource.com>
> Sent: Thursday, November 30, 2006 1:09 AM
> Subject: Re: [Xen-devel] [PATCH] Enable uppercase letters to be entered inQEMU
> monitor terminal
>
>
>>
>>
>>
>> On 29/11/06 15:48, "Daniel P. Berrange" <berrange@redhat.com> wrote:
>>
>>>> Doesn't this eat the shift/caps key events even when not in qemu monitor
>>>> mode? What if the guest has shortcut key combos involving those keys, for
>>>> example?
>>>
>>> Re-checking the patch I believe its already doing the correct thing.
>>>
>>> The do_key_event method is broken into 2 halfs. In the first half, the
>>> keysyms are sent to either the guest OS, or the monitor. In the second
>>> half the shift/caps/ctrl/alt state is being tracked. So the code I added
>>> for tracking shift/caps does not interfere with the earlier code which
>>> actually sends the key press to the guest OS.
>>
>> Okay, I'll read the code more carefully. :-)
>>
>> -- keir
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2006-12-20 11:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-28 22:50 [PATCH] Enable uppercase letters to be entered in QEMU monitor terminal Daniel P. Berrange
2006-11-29 11:45 ` Keir Fraser
2006-11-29 12:04 ` Daniel P. Berrange
2006-11-29 12:19 ` Keir Fraser
2006-11-29 15:48 ` Daniel P. Berrange
2006-11-29 16:09 ` Keir Fraser
2006-12-20 11:15 ` Kasai Takanori
2006-12-20 11:19 ` Keir Fraser [this message]
2006-12-21 1:31 ` Kasai Takanori
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=C1AECCCE.6A1F%keir@xensource.com \
--to=keir@xensource.com \
--cc=berrange@redhat.com \
--cc=kasai.takanori@jp.fujitsu.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.