From: Okash Khawaja <okash.khawaja@gmail.com>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>
Cc: covici@ccs.covici.com,
"Speakup is a screen review system for Linux."
<speakup@linux-speakup.org>
Subject: Re: DecTalk External (decext) testers wanted!
Date: Mon, 1 May 2017 16:59:33 +0100 [thread overview]
Message-ID: <20170501155933.GA660@sanghar> (raw)
In-Reply-To: <20170501093157.nktysqryj6eltlps@var.youpi.perso.aquilenet.fr>
Hi,
On Mon, May 01, 2017 at 11:31:57AM +0200, Samuel Thibault wrote:
> Hello,
>
> John Covici, on dim. 30 avril 2017 04:18:12 -0400, wrote:
> > If there is a lot of output, it takes a very long time -- 30 seconds
> > or more to shut up when I hit the enter key on the numpad.
>
> Okash, this may be related with the serial port layer buffering data.
Right, that would explain it but I thought send_xchar would prioritise
SYNTH_CLEAR over buffered data.
> I
> realize that we haven't made the synth_flush functions call the
> flush_buffer tty ops. We need to do so, otherwise even if we send the
> clear character, that's only after the processing of pending data.
>
> So in the synth_flush functions, one needs to first call flush_buffer()
> and then send the clear character.
>
> Yes, flush_buffer is yet another method to be added to the spk_io_ops
> structure.
Cool, I'll make the changes and share them here as a patch.
> In the serialio case, you can just let it do nothing. One
> could want to flush the UART 16550 buffer but that's not the point of
> your patch anyway :)
Sure, may be something to keep in mind for later.
Thanks,
Okash
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
Okash Khawaja
` Okash Khawaja
` Okash Khawaja
` John Covici
` Okash Khawaja
` Okash Khawaja
` Keith Barrett
` Okash Khawaja
` Karen Lewellen
` Okash Khawaja
` Tom Fowle
` Gregory Nowak
` Keith Barrett
` Tom Fowle
` Gregory Nowak
` Okash Khawaja
` Okash Khawaja
` Gregory Nowak
` Okash Khawaja
` Keith Barrett
` Gregory Nowak
` Keith Barrett
` Okash Khawaja
` Keith Barrett
` Gregory Nowak
` Keith Barrett
` Okash Khawaja
` Keith Barrett
` Keith Barrett
` Okash Khawaja
` Okash Khawaja
` Keith Barrett
` Okash Khawaja
` Keith Barrett
` Okash Khawaja
` Keith Barrett
` Okash Khawaja
` John Covici
` Okash Khawaja
` Okash Khawaja
` Gregory Nowak
` John Covici
` Gregory Nowak
` Samuel Thibault
` bns indexing, was: " Gregory Nowak
` Samuel Thibault
` Samuel Thibault
` Samuel Thibault
` John Covici
` Okash Khawaja
` Tony Baechler
` Okash Khawaja
` John Covici
` Okash Khawaja
` John Covici
` Frost
` Zachary Kline
` Okash Khawaja
` John Covici
` Okash Khawaja
` John Covici
` Samuel Thibault
` Samuel Thibault
` staging: speakup: flush tty buffers Okash Khawaja
` Okash Khawaja
` John Covici
` Okash Khawaja
` John Covici
` Okash Khawaja
` Samuel Thibault
` Okash Khawaja
` Samuel Thibault
` staging: speakup: flush tty buffers and ensure hardware flow control Okash Khawaja
` Samuel Thibault
` Okash Khawaja [this message]
` DecTalk External (decext) testers wanted! Samuel Thibault
Okash Khawaja
` Gregory Nowak
` Kirk Reiser
` Gregory Nowak
` Kirk Reiser
` Gregory Nowak
` Tom Fowle
` Butch Bussen
` Okash Khawaja
` Gregory Nowak
` Gregory Nowak
` 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=20170501155933.GA660@sanghar \
--to=okash.khawaja@gmail.com \
--cc=covici@ccs.covici.com \
--cc=samuel.thibault@ens-lyon.org \
--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).