mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: Scrolling issues in edit command
Date: Tue, 5 Apr 2016 10:40:48 +0200	[thread overview]
Message-ID: <CABDcavZM-45JiFmvzEcALOqmf8dVN8QrJP_2XUpXQe5GyZ+Gqg@mail.gmail.com> (raw)
In-Reply-To: <20160405081413.GB10108@pengutronix.de>

Hello,

2016-04-05 10:14 GMT+02:00 Uwe Kleine-König <u.kleine-koenig@pengutronix.de>:
> On Tue, Apr 05, 2016 at 09:52:39AM +0200, Guillermo Rodriguez Garcia wrote:
>> 2016-04-04 22:07 GMT+02:00 Uwe Kleine-König <u.kleine-koenig@pengutronix.de>:
>> > Hello,
>> >
>> > On Wed, Mar 30, 2016 at 05:38:53PM +0200, Guillermo Rodriguez Garcia wrote:
>> >> I am trying to setup Barebox on a SAMA5D3-Xplained board. I started
>> >> with barebox-2016.03.0. So far things are looking good.
>> >>
>> >> I have found that I have problems in the 'edit' command, when trying
>> >> to scroll using the arrow keys. Scrolling up inserts random "A"
>> >> characters in the text, scrolling down inserts random "B" characters.
>> >> I am using minicom as the terminal. I don't remember seeing this
>> >> before with older versions of barebox on different boards.
>> >
>> > Can you instrument your serial driver to count/notice overflow events?
>>
>> You mean in barebox, or in the host where I'm running minicom/microcom?
>
> in barebox.

I can inspect the UART's status register using md and clear the
overrun bit using mw.

Yes, both the scrolling problem and the "missing chars problem" when
pasting text in barebox are associated with overruns.

Still I don't understand why pasting the same text in the command line
does not result in an overrun.

Perhaps "edit" is so busy repainting the screen that the incoming
characters are not handled in time?

> Also, what is your rs232 hardware? Some usb-to-rs232
> adapters are not reliable. The native 8250 ports on PCs are good ones I
> think.

It is a USB to rs232 converter but I am also using this on other
boards running barebox (older version of barebox though, and different
target hardware) and no problems there.

Just to be safe I repeated the tests on a PC that has native serial
ports. That one is a Windows box so I used PuTTY. On that setup I do
not see the "missing chars problem" , however the scrolling problem
still exists (random "A" and "B" characters inserted while scrolling).

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
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" ?

Best,

Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2016-04-05  8:41 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 [this message]
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

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=CABDcavZM-45JiFmvzEcALOqmf8dVN8QrJP_2XUpXQe5GyZ+Gqg@mail.gmail.com \
    --to=guille.rodriguez@gmail.com \
    --cc=barebox@lists.infradead.org \
    --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