[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <875znqhia0.fsf@cmbmachine.messageid.invalid>
Date: Wed, 24 Jul 2019 21:04:07 -0700
From: Chris Brannon <chris@...-brannons.com>
To: Gregory Nowak <greg@...gn.net>
Cc: Samuel Thibault <samuel.thibault@...-lyon.org>,
speakup@...ux-speakup.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Okash Khawaja <okash.khawaja@...il.com>,
devel@...verdev.osuosl.org, Kirk Reiser <kirk@...sers.ca>,
Simon Dickson <simonhdickson@...il.com>,
linux-kernel@...r.kernel.org,
Christopher Brannon <chris@...-brannons.com>
Subject: Re: [HELP REQUESTED from the community] Was: Staging status of speakup
Gregory Nowak <greg@...gn.net> writes:
> keymap
> I believe this is the currently active kernel keymap. I'm not sure of
> the format, probably what dumpkeys(1) and showkey(1) use. Echoing
> different values here should allow for remapping speakup's review
> commands besides remapping the keyboard as a whole.
AFAIK the Speakup keymap is just for remapping keys to Speakup
functions. It's a binary format, not related to dumpkeys etc. You need
a special program to compile a textual keymap into something that can be
loaded into /sys/accessibility/speakup/keymap. I may have source for
that lying around here somewhere. This is "here there be dragons"
territory. I think the only specification of the format is in the
source code.
-- Chris
Powered by blists - more mailing lists