From: Jamie Lokier <jamie@shareable.org>
To: Chris Heath <chris@heathens.co.nz>
Cc: aebr@win.tue.nl, linux-kernel@vger.kernel.org, vojtech@ucw.cz,
Ralf Hildebrandt <Ralf.Hildebrandt@charite.de>
Subject: Re: keyboard - was: Re: Linux 2.6.0-test4
Date: Thu, 4 Sep 2003 21:48:16 +0100 [thread overview]
Message-ID: <20030904204816.GD31590@mail.jlokier.co.uk> (raw)
In-Reply-To: <20030903235647.C765.CHRIS@heathens.co.nz>
Chris Heath wrote:
> 1. I assume it is OK to defer processing the code e0 until the following
> byte arrives. Are there any keyboards out there with e0 in the keyboard
> ID? This could break the atkbd probe for such keyboards. (The
> alternative would be to pass the repeated key releases through to atkbd,
> and let that layer remove the duplicates.)
>
> 2. The event that appears between two repeated key releases is always a
> key release and not a key press.
>
> 3. There will only be at most one key event in between two repeated key
> releases.
Why so many complicated assumptions? Just maintain a bitmap if key
up/down states (initialised to up), and if you receive a release event
when the key is in the up state, ignore the event.
-- Jamie
next prev parent reply other threads:[~2003-09-04 20:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-04 4:09 Chris Heath
2003-09-04 20:48 ` Jamie Lokier [this message]
2003-09-04 22:34 ` Andries Brouwer
2003-09-04 23:00 ` Jamie Lokier
2003-09-05 0:19 ` Andries Brouwer
2003-09-05 3:41 ` Chris Heath
2003-09-05 10:08 ` Andries Brouwer
-- strict thread matches above, loose matches on Subject: below --
2003-09-05 14:57 John Bradford
2003-09-05 23:45 ` Andries Brouwer
2003-09-05 13:46 Norman Diamond
2003-08-31 16:22 Chris Heath
2003-09-02 8:07 ` Ralf Hildebrandt
2003-09-02 10:47 ` keyboard - was: " Andries Brouwer
2003-09-02 11:18 ` Ralf Hildebrandt
2003-09-02 12:32 ` Ralf Hildebrandt
2003-09-02 21:41 ` Andries Brouwer
2003-09-03 7:45 ` Ralf Hildebrandt
2003-09-03 13:25 ` Ralf Hildebrandt
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=20030904204816.GD31590@mail.jlokier.co.uk \
--to=jamie@shareable.org \
--cc=Ralf.Hildebrandt@charite.de \
--cc=aebr@win.tue.nl \
--cc=chris@heathens.co.nz \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@ucw.cz \
/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
all inboxes | Powered by JetHome®