qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Blue Swirl <blauwirbel@gmail.com>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [PATCH 0/2] pckbd improvements
Date: Sat, 15 May 2010 12:49:45 +0300	[thread overview]
Message-ID: <AANLkTik5GD44bufgvJsMWklVrAS8sz2JT3mzVQGGjVdo@mail.gmail.com> (raw)

In 2/2, A20 logic changes a bit but I doubt any guest would be broken
if A20 line written through I/O port 92 couldn't be read via i8042.
The reverse (write using i8042 and read port 92) will work.

Blue Swirl (2):
  pc: improve onboard I/O port debugging
  Compile pckbd only once

 Makefile.objs                        |    1 +
 Makefile.target                      |    8 ++--
 default-configs/i386-softmmu.mak     |    1 +
 default-configs/mips-softmmu.mak     |    1 +
 default-configs/mips64-softmmu.mak   |    1 +
 default-configs/mips64el-softmmu.mak |    1 +
 default-configs/mipsel-softmmu.mak   |    1 +
 default-configs/ppc-softmmu.mak      |    1 +
 default-configs/ppc64-softmmu.mak    |    1 +
 default-configs/ppcemb-softmmu.mak   |    1 +
 default-configs/sparc64-softmmu.mak  |    1 +
 default-configs/x86_64-softmmu.mak   |    1 +
 hw/pc.c                              |   38 ++++++++++++++++----
 hw/pc.h                              |    6 ++--
 hw/pckbd.c                           |   64 +++++++++++++++++++++-------------
 hw/vmmouse.c                         |    2 +-
 16 files changed, 90 insertions(+), 39 deletions(-)

             reply	other threads:[~2010-05-15  9:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-15  9:49 Blue Swirl [this message]
2010-05-16  9:42 ` [Qemu-devel] Re: [PATCH 0/2] pckbd improvements Paolo Bonzini
2010-05-16 10:28   ` Blue Swirl
2010-05-16 17:57     ` Jamie Lokier
2010-05-16 20:06       ` Blue Swirl
2010-05-17 20:02         ` [Qemu-devel] A20 line control (was Re: [PATCH 0/2] pckbd improvements) Jamie Lokier
2010-05-17 11:16     ` [Qemu-devel] Re: [PATCH 0/2] pckbd improvements Paolo Bonzini
2010-05-17 16:34       ` Blue Swirl

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=AANLkTik5GD44bufgvJsMWklVrAS8sz2JT3mzVQGGjVdo@mail.gmail.com \
    --to=blauwirbel@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).