public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Mark Hounschell <markh@compro.net>
Cc: Lee Revell <rlrevell@joe-job.com>,
	"linux-os (Dick Johnson)" <linux-os@analogic.com>,
	Paul Fulghum <paulkf@microgate.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Serial issue
Date: Fri, 18 Aug 2006 21:36:07 +0100	[thread overview]
Message-ID: <20060818203607.GK21101@flint.arm.linux.org.uk> (raw)
In-Reply-To: <44E623EB.1060908@compro.net>

On Fri, Aug 18, 2006 at 04:32:43PM -0400, Mark Hounschell wrote:
> 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)?
> > 
> > Lee
> > 
> > 
> 
> Your cable is probably wrong.  Both ends have to be using the type of flow
> control your cable is wired for.

Not quite true.  You can use XON/XOFF or hardware flow with a fully
populated cable, but if you have a sparsely populated cable (RX,TX,GND
only) then hardware flow control can't (and won't) work.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

  reply	other threads:[~2006-08-18 20:36 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 [this message]
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

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=20060818203607.GK21101@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    --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