From: Finn Thain <fthain@telegraphics.com.au>
To: Angelo Dureghello <angelo@sysam.it>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: coldfire uart question
Date: Wed, 18 Oct 2017 19:15:44 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LNX.2.00.1710181831220.3@nippy.intranet> (raw)
In-Reply-To: <c903087c-7997-8b8d-88fd-38028022dab4@sysam.it>
On Wed, 18 Oct 2017, Angelo Dureghello wrote:
> Ok will do some test, maybe also adding 1 stop bit
Adding a stop bit or two will marginally reduce the effective data rate
but it could be that 115200 baud is unrealistic.
> or killing some processes may help ? I am already into initramfs, so the
> write should not be that heavy.
I take it you mean storing into rootfs. So the latency is caused by some
other interrupt source (not flash storage) with higher priority than the
uart irq...
> Will try also zmodem in case.
>
Keep in mind that a larger block size would mean a larger penalty for a
single overrun, which can reduce throughput.
--
> Regards,
> Angelo
>
next prev parent reply other threads:[~2017-10-18 8:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-15 17:28 coldfire uart question Angelo Dureghello
2017-10-15 23:08 ` Finn Thain
2017-10-17 21:18 ` Angelo Dureghello
2017-10-18 0:06 ` Finn Thain
2017-10-18 6:37 ` Geert Uytterhoeven
2017-10-18 7:05 ` Angelo Dureghello
2017-10-18 8:15 ` Finn Thain [this message]
2017-10-18 7:12 ` Greg Ungerer
2017-10-18 7:19 ` Angelo Dureghello
2017-10-18 7:35 ` Philippe De Muyter
2017-10-15 23:57 ` Greg Ungerer
2017-10-17 21:07 ` Angelo Dureghello
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=alpine.LNX.2.00.1710181831220.3@nippy.intranet \
--to=fthain@telegraphics.com.au \
--cc=angelo@sysam.it \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.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