qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "andrzej zaborowski" <balrogg@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] PS/2 mouse support for FC4 guest broken in QEMU 0.9.1
Date: Sun, 3 Feb 2008 04:15:52 +0100	[thread overview]
Message-ID: <fb249edb0802021915h46a2e396pa85a6f8cffb7ccb@mail.gmail.com> (raw)
In-Reply-To: <200801212119.17652.even.rouault@mines-paris.org>

On 21/01/2008, Even Rouault <even.rouault@mines-paris.org> wrote:
> Thanks for the tutorial on how to use git bisection ;-)
> In fact, whatever version control system you use, I think you spend most of
> time recompiling and testing stuff...
>
> Anyway, on the core problem I'm pointing out, does someone have any clue on
> what should be done ? Should the revision 1.24 of
> hw/pckbd.c ("QEMU keyboard issue with Gujin-2.2") be reverted ? Is there a way
> to get FC4 to work again, and "Gujin" at the same time ? Is the patch of
> revision 1.24 the right fix for Gujin and another additionnal fix is required
> for the FC4 issue (presumably related to Linux kernel version 2.6.11) or
> should it be reverted and a better fix found for Gujin ?

I have no clue about ps2 but seeing as redirecting the command from
kbd to mouse (0 -> 1 in the kbd_queue call) fixes the keyboard issue
for Gujin, but breaks mouse, the obvious conclusion is that the
command should not be done for either kbd or mouse.  Can you try with
line 214 (previously line 207) simply removed?  If you can test also
how that affects Gujin that would be even better.

Cheers

  reply	other threads:[~2008-02-03  3:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-20 20:58 [Qemu-devel] PS/2 mouse support for FC4 guest broken in QEMU 0.9.1 Even Rouault
2008-01-20 22:27 ` Even Rouault
2008-01-20 23:54   ` Johannes Schindelin
2008-01-21 20:19     ` Even Rouault
2008-02-03  3:15       ` andrzej zaborowski [this message]
2008-02-03  9:56         ` Even Rouault

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