From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: barebox@lists.infradead.org,
Rolf Evers-Fischer <embedded24@evers-fischer.de>
Subject: Re: Scrolling issues in edit command
Date: Tue, 5 Apr 2016 17:31:21 +0200 [thread overview]
Message-ID: <CABDcavbZzU2=AbnRKYvoi1JJW95QHDHmc1_UHeSFRvqW-Guq7w@mail.gmail.com> (raw)
In-Reply-To: <20160405122319.GF10108@pengutronix.de>
Hello,
2016-04-05 14:23 GMT+02:00 Uwe Kleine-König <u.kleine-koenig@pengutronix.de>:
> Hello,
>
> On Tue, Apr 05, 2016 at 01:01:02PM +0200, Guillermo Rodriguez Garcia wrote:
>> However if there are other issues I would also like to find out. If
>> you would like to suggest any new tests please let me know and I'll be
>> happy to try them here.
> There are ANSI control sequences for scrolling, too. I don't know if
> they are used, but if they were it would greatly reduce the needed
> bandwidth.
The ANSI control sequences are disabled by default, but they are used
if the command is invoked as "sedit" instead of "edit".
When the command is invoked as "sedit" the scrolling problem is gone.
I guess this more or less supports the hypothesis that the problem
could be caused by losing incoming characters due to the lack of FIFOs
in this port + the repainting performed by "edit". If this sounds
reasonable then I guess there's not much more that can be done here. I
just wanted to make suere there were no other underlying problems.
Thank you all for the feedback and help,
Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2016-04-05 15:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 15:38 Guillermo Rodriguez Garcia
2016-03-31 13:39 ` Holger Schurig
2016-03-31 15:36 ` Guillermo Rodriguez Garcia
2016-04-04 6:38 ` Sascha Hauer
2016-04-04 13:34 ` Guillermo Rodriguez Garcia
2016-04-05 7:32 ` Rolf Evers-Fischer
2016-04-04 20:07 ` Uwe Kleine-König
2016-04-05 7:52 ` Guillermo Rodriguez Garcia
2016-04-05 8:14 ` Uwe Kleine-König
2016-04-05 8:40 ` Guillermo Rodriguez Garcia
2016-04-05 9:05 ` Uwe Kleine-König
2016-04-05 9:40 ` Rolf Evers-Fischer
2016-04-05 11:01 ` Guillermo Rodriguez Garcia
2016-04-05 12:23 ` Uwe Kleine-König
2016-04-05 15:31 ` Guillermo Rodriguez Garcia [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='CABDcavbZzU2=AbnRKYvoi1JJW95QHDHmc1_UHeSFRvqW-Guq7w@mail.gmail.com' \
--to=guille.rodriguez@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=embedded24@evers-fischer.de \
--cc=u.kleine-koenig@pengutronix.de \
/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