qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Hervé Poussineau" <hpoussin@reactos.org>
To: qemu-devel@nongnu.org
Cc: Geoffrey McRae <geoff@hostfission.com>, qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] ps2kbd: default to scan enabled after reset
Date: Sat, 10 Nov 2018 21:53:18 +0100	[thread overview]
Message-ID: <0b492470-2146-c75a-6be6-0a2c5d0ebf5c@reactos.org> (raw)
In-Reply-To: <20181021190721.2148-1-hpoussin@reactos.org>

Ping.

Le 21/10/2018 à 21:07, Hervé Poussineau a écrit :
> A check for scan_enabled has been added to ps2_keyboard_event in commit
> 143c04c7e0639e53086519592ead15d2556bfbf2 to prevent stream corruption.
> This works well as long as operating system is resetting keyboard, or enabling it.
> 
> This fixes IBM 40p firmware, which doesn't bother sending KBD_CMD_RESET,
> KBD_CMD_ENABLE or KBD_CMD_RESET_ENABLE before trying to use the keyboard.
> 
> Signed-off-by: Hervé Poussineau <hpoussin@reactos.org>
> ---
>   hw/input/ps2.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/hw/input/ps2.c b/hw/input/ps2.c
> index fdfcadf9a1..eded4f0f8d 100644
> --- a/hw/input/ps2.c
> +++ b/hw/input/ps2.c
> @@ -938,7 +938,7 @@ static void ps2_kbd_reset(void *opaque)
>   
>       trace_ps2_kbd_reset(opaque);
>       ps2_common_reset(&s->common);
> -    s->scan_enabled = 0;
> +    s->scan_enabled = 1;
>       s->translate = 0;
>       s->scancode_set = 2;
>       s->modifiers = 0;
> 

  reply	other threads:[~2018-11-10 21:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-21 19:07 [Qemu-devel] [PATCH] ps2kbd: default to scan enabled after reset Hervé Poussineau
2018-11-10 20:53 ` Hervé Poussineau [this message]
2018-11-18 10:09   ` [Qemu-devel] [PATCH-for-3.1] " Hervé Poussineau
2018-11-22 18:30     ` [Qemu-devel] [PATCH-for-3.1] [REGRESSION FIX] " Hervé Poussineau
2018-11-23  6:25       ` Gerd Hoffmann
2018-11-10 21:25 ` [Qemu-devel] [PATCH] " Philippe Mathieu-Daudé

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=0b492470-2146-c75a-6be6-0a2c5d0ebf5c@reactos.org \
    --to=hpoussin@reactos.org \
    --cc=geoff@hostfission.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@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).