From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: Scrolling issues in edit command
Date: Tue, 5 Apr 2016 11:05:11 +0200 [thread overview]
Message-ID: <20160405090511.GC10108@pengutronix.de> (raw)
In-Reply-To: <CABDcavZM-45JiFmvzEcALOqmf8dVN8QrJP_2XUpXQe5GyZ+Gqg@mail.gmail.com>
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.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2016-04-05 9:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 15:38 Scrolling issues in edit command 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 [this message]
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
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=20160405090511.GC10108@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=guille.rodriguez@gmail.com \
/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.