From: Chris Brannon <chris@the-brannons.com>
To: Gregory Nowak <greg@gregn.net>
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>,
speakup@linux-speakup.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Okash Khawaja <okash.khawaja@gmail.com>,
devel@driverdev.osuosl.org, Kirk Reiser <kirk@reisers.ca>,
Simon Dickson <simonhdickson@gmail.com>,
linux-kernel@vger.kernel.org,
Christopher Brannon <chris@the-brannons.com>
Subject: Re: [HELP REQUESTED from the community] Was: Staging status of speakup
Date: Wed, 24 Jul 2019 21:04:07 -0700 [thread overview]
Message-ID: <875znqhia0.fsf@cmbmachine.messageid.invalid> (raw)
In-Reply-To: <20190725035352.GA7717@gregn.net> (Gregory Nowak's message of "Wed, 24 Jul 2019 20:53:52 -0700")
Gregory Nowak <greg@gregn.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
next prev parent reply other threads:[~2019-07-25 4:13 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 13:01 Staging status of speakup Okash Khawaja
2019-03-16 1:19 ` Chris Brannon
2019-03-16 9:35 ` Samuel Thibault
2019-03-16 10:22 ` Samuel Thibault
2019-03-19 16:31 ` Alan Cox
2019-03-19 17:07 ` Samuel Thibault
2019-03-19 17:11 ` Adam Borowski
2019-03-20 20:54 ` Okash Khawaja
2019-03-16 10:05 ` Okash Khawaja
2019-03-16 3:18 ` Greg Kroah-Hartman
2019-03-16 10:09 ` Okash Khawaja
2019-07-06 19:08 ` Okash Khawaja
2019-07-06 19:08 ` Okash Khawaja
2019-07-07 6:57 ` Greg Kroah-Hartman
2019-07-07 6:57 ` Greg Kroah-Hartman
2019-07-12 8:38 ` Greg Kroah-Hartman
2019-07-12 8:38 ` Greg Kroah-Hartman
2019-07-12 9:23 ` [HELP REQUESTED from the community] Was: " Samuel Thibault
2019-07-12 9:23 ` Samuel Thibault
2019-07-13 0:46 ` Gregory Nowak
2019-07-13 0:46 ` Gregory Nowak
2019-07-25 3:53 ` Gregory Nowak
2019-07-25 4:04 ` Chris Brannon [this message]
2019-07-25 10:44 ` John Covici
2019-08-21 16:39 ` Okash Khawaja
2019-08-21 22:22 ` Gregory Nowak
2019-09-08 9:43 ` Okash Khawaja
2019-09-08 9:43 ` Okash Khawaja
2019-09-09 2:54 ` Gregory Nowak
2019-09-09 2:54 ` Gregory Nowak
2019-09-14 21:08 ` Okash Khawaja
2019-09-14 21:08 ` Okash Khawaja
2019-09-14 23:32 ` Samuel Thibault
2019-09-14 23:32 ` Samuel Thibault
2019-09-15 13:43 ` Greg Kroah-Hartman
2019-09-15 13:43 ` Greg Kroah-Hartman
2019-09-15 18:41 ` Okash Khawaja
2019-09-15 18:41 ` Okash Khawaja
2019-09-16 13:47 ` Samuel Thibault
2019-09-16 13:47 ` Samuel Thibault
2019-09-16 14:11 ` Greg Kroah-Hartman
2019-09-16 14:11 ` Greg Kroah-Hartman
2019-09-16 22:38 ` Gregory Nowak
2019-09-16 22:38 ` Gregory Nowak
2019-09-17 8:01 ` Greg Kroah-Hartman
2019-09-17 8:01 ` Greg Kroah-Hartman
2019-09-18 1:03 ` Gregory Nowak
2019-09-18 1:03 ` Gregory Nowak
2019-09-18 6:16 ` Greg Kroah-Hartman
2019-09-18 6:16 ` Greg Kroah-Hartman
2019-09-18 20:30 ` Gregory Nowak
2019-09-18 20:30 ` Gregory Nowak
2019-09-20 7:46 ` Greg Kroah-Hartman
2019-09-20 7:46 ` Greg Kroah-Hartman
2019-09-20 10:18 ` Okash Khawaja
2019-09-20 10:18 ` Okash Khawaja
2019-09-16 20:21 ` Gregory Nowak
2019-09-16 20:21 ` Gregory Nowak
2019-07-25 6:11 ` Willem van der Walt
2019-07-25 6:33 ` Greg Kroah-Hartman
2019-07-25 10:41 ` John Covici
2019-07-12 9:24 ` Okash Khawaja
2019-07-12 9:24 ` Okash Khawaja
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=875znqhia0.fsf@cmbmachine.messageid.invalid \
--to=chris@the-brannons.com \
--cc=devel@driverdev.osuosl.org \
--cc=greg@gregn.net \
--cc=gregkh@linuxfoundation.org \
--cc=kirk@reisers.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=okash.khawaja@gmail.com \
--cc=samuel.thibault@ens-lyon.org \
--cc=simonhdickson@gmail.com \
--cc=speakup@linux-speakup.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.