From: Okash Khawaja <okash.khawaja@gmail.com>
To: John Covici <covici@ccs.covici.com>
Cc: "Speakup is a screen review system for Linux."
<speakup@linux-speakup.org>
Subject: Re: speakup-r functionality
Date: Sun, 20 Aug 2017 22:45:27 +0100 [thread overview]
Message-ID: <20170820214527.GA464@sanghar> (raw)
In-Reply-To: <m38tie12un.wl-covici@ccs.covici.com>
Hi,
Here's one thing I think worth trying. I have updated the patch so that
the net difference between before and after the patch is that
speakup_fake_down_arrow() is not called when inside interrupt context.
Calling speakup_fake_down_arrow() inside interrupt causes the kernel
lock up because this itself generates same interrupt, leading to
infinite recursion.
I didn't think this code was triggered outside of interrupt context, but
it possibly is when using a serial console - which is the only
explanation I can think of for the behaviour you've described.
Thanks
---
drivers/staging/speakup/main.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
--- a/drivers/staging/speakup/main.c
+++ b/drivers/staging/speakup/main.c
@@ -1408,7 +1408,10 @@ static void read_all_doc(struct vc_data
cursor_track = read_all_mode;
spk_reset_index_count(0);
if (get_sentence_buf(vc, 0) == -1) {
- kbd_fakekey2(vc, RA_DOWN_ARROW);
+ del_timer(&cursor_timer);
+ if (!in_interrupt())
+ speakup_fake_down_arrow();
+ start_read_all_timer(vc, RA_DOWN_ARROW);
} else {
say_sentence_num(0, 0);
synth_insert_next_index(0);
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
Okash Khawaja
` John Covici
` Okash Khawaja
` John Covici
` Okash Khawaja
` John Covici
` Okash Khawaja
` John Covici
` Okash Khawaja
` John Covici
` Okash Khawaja [this message]
` John Covici
` 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=20170820214527.GA464@sanghar \
--to=okash.khawaja@gmail.com \
--cc=covici@ccs.covici.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).