From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Lee Revell <rlrevell@joe-job.com>
Cc: markh@compro.net, Paul Fulghum <paulkf@microgate.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Serial issue
Date: Fri, 18 Aug 2006 22:02:17 +0100 [thread overview]
Message-ID: <20060818210217.GL21101@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1155934453.2924.56.camel@mindpipe>
On Fri, Aug 18, 2006 at 04:54:13PM -0400, Lee Revell wrote:
> On Fri, 2006-08-18 at 21:34 +0100, Russell King wrote:
> > On Fri, Aug 18, 2006 at 04:28:36PM -0400, Lee Revell wrote:
> > > On Fri, 2006-08-18 at 16:25 -0400, Mark Hounschell wrote:
> > > > Take it from someone who actually still uses dumb terminals every day,
> > > > any thing over 9600 baud still requires some kind of flow control for
> > > > reliable consistent operation. Software (Xon/Xoff) and or hardware
> > > > (RTS/RTS/DTE) flow control.
> > > >
> > >
> > > Any idea why the serial console does not work at all with flow control
> > > enabled (regardless of whether the host runs Linux or another OS)?
> >
> > I use serial console with flow control and haven't seen any problems.
> >
> > Can you describe your issue with more detail?
> >
> > What actions are required to get this "does not work at all" state?
> >
> > Are you passing a kernel parameter to enable flow control?
> >
> > Are you saying that you get kernel messages if flow control is disabled,
> > but if you subsequently enable flow control, and provoke a kernel message,
> > you don't see any messages? When you re-disable flow control, you do?
> >
>
> I believe the flow control problem is due to my cable.
>
> Anyway I don't want to confuse the issue: the problem that I want to
> solve (or at least explain) is that while the serial console works with
> the host serial port in both interrupt and polled mode, kermit file
> transfers only work in polled mode ("setserial /dev/ttyS0 irq 0").
If you're talking about sending via a polled port, the average data rate
is probably slow enough that the receiving side can keep up. But in
interrupt mode, it's probably a stream of characters at the specified
baud rate, which results in lost characters.
That explaination doesn't resolve the receiving via a polled port though.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
prev parent reply other threads:[~2006-08-18 21:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-18 0:47 Serial issue Lee Revell
2006-08-18 15:44 ` Paul Fulghum
2006-08-18 16:25 ` Lee Revell
2006-08-18 16:34 ` Lee Revell
2006-08-18 17:55 ` Lee Revell
2006-08-18 18:11 ` Paul Fulghum
2006-08-18 18:17 ` Lee Revell
2006-08-18 18:36 ` Russell King
2006-08-18 18:40 ` Lee Revell
2006-08-18 18:52 ` Russell King
2006-08-18 19:06 ` Paul Fulghum
2006-08-18 19:09 ` Russell King
2006-08-18 19:15 ` linux-os (Dick Johnson)
2006-08-18 19:21 ` Lee Revell
2006-08-18 20:05 ` linux-os (Dick Johnson)
2006-08-18 20:25 ` Mark Hounschell
2006-08-18 20:28 ` Lee Revell
2006-08-18 20:32 ` Mark Hounschell
2006-08-18 20:36 ` Russell King
2006-08-18 20:57 ` Mark Hounschell
2006-08-18 20:34 ` Russell King
2006-08-18 20:54 ` Lee Revell
2006-08-18 21:02 ` Russell King [this message]
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=20060818210217.GL21101@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=markh@compro.net \
--cc=paulkf@microgate.com \
--cc=rlrevell@joe-job.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox