From: Russell King <rmk@arm.linux.org.uk>
To: Robin Getz <rgetz@blackfin.uclinux.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Haavard Skinnemoen <hskinnemoen@atmel.com>,
linux-serial@vger.kernel.org
Subject: Re: Inter-Character Delay
Date: Tue, 26 Feb 2008 19:18:25 +0000 [thread overview]
Message-ID: <20080226191825.GA31527@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200802261321.18288.rgetz@blackfin.uclinux.org>
On Tue, Feb 26, 2008 at 01:21:18PM -0500, Robin Getz wrote:
> On Tue 26 Feb 2008 12:11, Russell King pondered:
> > On Tue, Feb 26, 2008 at 11:11:58AM -0500, Robin Getz wrote:
> > > ping.
> > >
> > > Comments appreciated.
> >
> > ascii-xfr does inter-line and inter-character delays without requiring
> > any kernel modifications - used it with some dumb boot loaders which
> > required 'mem deposit <address> <word>' to be sent slowly to the target.
>
> Thanks for the pointer.
>
> Solving the problem in userspace (with tcdrain and udelay) when some
> hardware can do the same thing with zero overhead - doesn't seem like
> the most efficient way to do things....
I know of no serial hardware which can insert arbitary delays inbetween
characters.
> It also lacks the ability to work with pre-existing user space
> applications.
So one could say those applications are buggy.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2008-02-26 19:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 18:36 Inter-Character Delay Robin Getz
2008-02-26 16:11 ` Robin Getz
2008-02-26 17:11 ` Russell King
2008-02-26 18:21 ` Robin Getz
2008-02-26 19:18 ` Russell King [this message]
2008-02-26 20:10 ` Robin Getz
2008-02-26 20:59 ` Chris Doré
2008-02-27 15:57 ` Robin Getz
2008-03-03 8:29 ` Tosoni
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=20080226191825.GA31527@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hskinnemoen@atmel.com \
--cc=linux-serial@vger.kernel.org \
--cc=rgetz@blackfin.uclinux.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