From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: Rolf Evers-Fischer <embedded24@evers-fischer.de>
Cc: barebox@lists.infradead.org,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: Re: Scrolling issues in edit command
Date: Tue, 5 Apr 2016 13:01:02 +0200 [thread overview]
Message-ID: <CABDcavY5+W7wQv19UiSGJ1-+-V4Mw4Trv8NsCCGAdWNgCPofbQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1604051131350.3483@9VTHT2J-D520>
2016-04-05 11:40 GMT+02:00 Rolf Evers-Fischer <embedded24@evers-fischer.de>:
> Uwe Kleine-König <u.kleine-koenig@...> writes:
>
>>
>> Hello,
>>
>> On Tue, Apr 05, 2016 at 10:40:48AM +0200, Guillermo Rodriguez Garcia
> wrote:
>> > I am wondering: If I am correct, serial in/out in barebox is not
>> > interrupt-driven. Plus, the default UART in the sama5d3_xplained board
>>
>> right
>>
>> > that I am using (DBGU) has no FIFOs. Plus, "edit" does a lot of
>> > repaint work while editing. Could it be the case that received chars
>> > are being missed by barebox due to the repainting work in "edit" ?
>>
>> Sounds likely.
>>
>
> But if the instruction cache is enabled, the SAMA5 should be fast enough,
> even without any interrupt handling for the UART data.
It actually seems to be fast enough for handling input data the
command line. I only see problems in "edit". And the original issue
(problems while scrolling continuously) mostly happens when the window
needs to be scrolled, and thus fully repainted for every scroll
up/down command received.
I don't think the limitation is actually related to CPU power in the
SAMA5. When "edit" is repainting, it needs to send all the new data
out through the serial port. If serial port tx is also not
interrupt-driven (not sure about that), then this means that barebox
will not have a chance to process new input until "edit" is done
sending data. Combine this with the lack of FIFOs in the DBGU port and
I guess that this could explain the results.
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.
Best,
Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2016-04-05 11:01 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 [this message]
2016-04-05 12:23 ` Uwe Kleine-König
2016-04-05 15:31 ` Guillermo Rodriguez Garcia
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=CABDcavY5+W7wQv19UiSGJ1-+-V4Mw4Trv8NsCCGAdWNgCPofbQ@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