From: Dave Mielke <dave@mielke.cc>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/3] input: add support for kbd delays
Date: Mon, 2 Jun 2014 04:50:56 -0400 [thread overview]
Message-ID: <20140602085056.GC10889@beta.private.mielke.cc> (raw)
In-Reply-To: <1401692854.22391.3.camel@nilsson.home.kraxel.org>
[quoted lines by Gerd Hoffmann on 2014/06/02 at 09:07 +0200]
Hi:
>Sounds plausible. Then adding a delay after queuing the release events
>should fix it. Can you try the attached patch (as incremental fix on
>top of the other three patches)?
It still isn't working correctly. I've just played with it now, with the
incremental patch, and see some very odd things.
For example: I held down the letter "j" (a lowercase j), and, as expected, "j"s
were echoed back at about the right rate. When I let go of the "j", they kept
on coming. I then held down backspace, and they started to disappear. When they
were all gone, I let go of backspace. At that point, the keyboard appeared to
be dead. I played around with only short presses of "a" and 's" for a while,
and suddenly the "j"s started to come back.
Something else I noticed was that typing a control character would result in a
doubling of that character. For example, control "u" resulted in "UU".
Now to go figure out how to stop those "j"s again. I left them repeating while
I wrote this. :-)
--
Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God.
Phone: 1-613-726-0014 | Ottawa, Ontario | http://Mielke.cc/bible/
EMail: dave@mielke.cc | Canada K2A 1H7 | http://FamilyRadio.com/
next prev parent reply other threads:[~2014-06-02 8:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1401280016-20851-1-git-send-email-kraxel@redhat.com>
[not found] ` <20140531160354.GI13640@beta.private.mielke.cc>
2014-06-02 7:07 ` [Qemu-devel] [PATCH 0/3] input: add support for kbd delays Gerd Hoffmann
2014-06-02 8:50 ` Dave Mielke [this message]
2014-06-02 9:31 ` Gerd Hoffmann
2014-06-02 10:43 ` Dave Mielke
2014-06-02 9:00 ` Dave Mielke
2014-06-02 9:29 ` Gerd Hoffmann
2014-06-02 10:40 ` Dave Mielke
2014-06-02 11:28 ` Gerd Hoffmann
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=20140602085056.GC10889@beta.private.mielke.cc \
--to=dave@mielke.cc \
--cc=kraxel@redhat.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).