From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Ave Milia <avemilia@protonmail.com>
Cc: "kernelnewbies@kernelnewbies.org" <kernelnewbies@kernelnewbies.org>
Subject: Re: Fixing keyboard chatter in Linux
Date: Sat, 03 Oct 2020 23:54:28 -0400 [thread overview]
Message-ID: <67342.1601783668@turing-police> (raw)
In-Reply-To: <QUq3MMK_YQlS6Atq1q1ghy94c9PwbJlSRd4FX3r8qK29wPbwn_34igJ_UrzUbJRXTGPdej_b-Sy3vkQjux3TJp2SiPjdbtaMNib96V9G7x0=@protonmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1128 bytes --]
On Sat, 03 Oct 2020 22:15:08 -0000, Ave Milia said:
> Hello,
>
> I have a faulty key switch on the keyboard that apparently sends multiple
> signals upon a single press. And apparently this is called keyboard chatter.
> Since no such software exists (or if it does, please share it), I would like
> to ask for your advice on how to implement this. I more or less know C, but I
> have no idea where to start on this problem:
> * what do I need to know about Linux kernel to solve this?
> * at which point of Linux input logic can I put this filter?
> * does the filter have to be in kernel mode or it can be in user mode (I'd
> prefer not to work in kernel mode)?
> * do I need to write a special input driver to implement this filter (the key
> board is a USB keyboard controlled by usbhid)?
>
> So, I just need some basic directions and where to start.
Step 0: Decide if that amount of effort is even worth it rather than just
replacing the keyboard.
Step 1: Design your software solution to be able to deal with multiple wonky
keys, because if one is broken, there's probably others that are going to give
out soon.
[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2020-10-04 3:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-03 22:15 Fixing keyboard chatter in Linux Ave Milia
2020-10-04 3:54 ` Valdis Klētnieks [this message]
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=67342.1601783668@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=avemilia@protonmail.com \
--cc=kernelnewbies@kernelnewbies.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).