From: Peter Maydell <peter.maydell@linaro.org>
To: Arwed Meyer <arwed.meyer@gmx.de>
Cc: qemu-devel@nongnu.org, qemu-stable@nongnu.org,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [PATCH v2 1/5] msmouse: Handle mouse reset
Date: Thu, 8 Sep 2022 22:11:49 +0100 [thread overview]
Message-ID: <CAFEAcA_F+ETYHT-HSs3wHwjqP4CEe2LtdfCf8B_P2Ted4xvk+w@mail.gmail.com> (raw)
In-Reply-To: <20220908173120.16779-2-arwed.meyer@gmx.de>
On Thu, 8 Sept 2022 at 18:43, Arwed Meyer <arwed.meyer@gmx.de> wrote:
>
> Detect mouse reset via RTS or DTR line:
> Don't send or process anything while in reset.
> When coming out of reset, send ID sequence first thing.
> This allows msmouse to be detected by common mouse drivers.
>
> Resolves: https://gitlab.com/qemu-project/qemu/-/issues/77
> Signed-off-by: Arwed Meyer <arwed.meyer@gmx.de>
How does this work across migration? There doesn't seem
to be anything that handles migration of the existing
state inside the MouseChardev either, though...
-- PMM
next prev parent reply other threads:[~2022-09-08 21:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 17:31 [PATCH v2 0/5] Make serial msmouse work Arwed Meyer
2022-09-08 17:31 ` [PATCH v2 1/5] msmouse: Handle mouse reset Arwed Meyer
2022-09-08 21:11 ` Peter Maydell [this message]
2022-09-11 17:14 ` Arwed Meyer
2022-09-11 18:27 ` Peter Maydell
2022-09-12 17:45 ` Arwed Meyer
2022-09-12 17:54 ` Arwed Meyer
2022-09-13 12:30 ` Peter Maydell
2022-09-08 17:31 ` [PATCH v2 2/5] chardev: src buffer const for write functions Arwed Meyer
2022-09-09 13:13 ` Marc-André Lureau
2022-09-08 17:31 ` [PATCH v2 3/5] msmouse: Use fifo8 instead of array Arwed Meyer
2022-09-09 13:18 ` Marc-André Lureau
2022-09-11 17:27 ` Arwed Meyer
2022-09-11 6:12 ` Volker Rümelin
2022-09-11 17:53 ` Arwed Meyer
2022-09-08 17:31 ` [PATCH v2 4/5] msmouse: Add pnp data Arwed Meyer
2022-09-09 13:20 ` Marc-André Lureau
2022-09-08 17:31 ` [PATCH v2 5/5] serial: Allow unaligned i/o access Arwed Meyer
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=CAFEAcA_F+ETYHT-HSs3wHwjqP4CEe2LtdfCf8B_P2Ted4xvk+w@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=arwed.meyer@gmx.de \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).