From: Anthony Liguori <anthony@codemonkey.ws>
To: Filip Navara <filip.navara@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Add support for multiple simultaneously used keyboard devices.
Date: Mon, 09 Nov 2009 08:35:20 -0600 [thread overview]
Message-ID: <4AF828A8.50904@codemonkey.ws> (raw)
In-Reply-To: <E1N1hIq-0004SO-Eo@lists.gnu.org>
Filip Navara wrote:
> The support for multiple keyboard devices is essential for emulating embedded boards where multiple input devices are present (eg. keypad and rotary encoder) which are implemented using separate QEMU devices.
>
> Signed-off-by: Filip Navara <filip.navara@gmail.com>
>
What boards would we actually expose multiple keyboards with?
Moreover, we're not doing anything useful here. We're just repeating a
single keypress to multiple keyboards which seems rather hackish.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-11-09 14:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-24 15:09 [Qemu-devel] [PATCH] Add support for multiple simultaneously used keyboard devices Filip Navara
2009-10-26 5:27 ` Juha.Riihimaki
2009-11-09 14:35 ` Anthony Liguori [this message]
2009-11-11 18:17 ` Filip Navara
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=4AF828A8.50904@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=filip.navara@gmail.com \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).