Re: Problems w/ serial flow control
- From: Philip Prindeville <philipp_subx@xxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 31 May 2006 12:48:22 -0600
Rick Stevens wrote:
On Wed, 2006-05-31 at 12:14 -0600, Philip Prindeville wrote:
Tim wrote:
On Tue, 2006-05-30 at 21:25 -0600, Philip Prindeville wrote:It is an 8-wire connection (over RJ-45 to DB-9), and can do 115200 (max rate)
I'm running FC3 on an MSI-7142 (K8MM-V motherboard), and usingLooking at a friend's router, his one's serial port connection *ONLY*
the two serial ports on the m/b. I used the stock
out-of-the-shrinkwrap settings for most hardware (except for the sound
board and X drivers), and things have worked fine.
But... when connecting to a router's console at 115200 with either
RTS/CTS or XON/XOFF flow control, I'm seeing dropped characters.
had the three-wire type of serial connection. So his couldn't possibly
use hardware handshaking (RTS/CTS). Perhaps yours can't too?
Also, check what your router says about its maximum port speeds and
handshaking protocols.
with either XON/XOFF or RTS/CTS.
I've tried both, and they're both lossy.
The issue is on the PC as the receiver...
Remember that both ends have to agree on the flow control. If one is
running RTS/CTS and the other is XON/XOFF, you don't have flow control.
At 115K, I'd always opt for RTS/CTS...XON/XOFF requires CPU intervention
unless you have fairly sophisticated hardware. All you have to do is
be a bit pokey at responding to an interrupt and you'll drop characters.
RTS/CTS is usually done at the hardware level and is a bit more
reliable.
I started with RTS/CTS... And had it set on both ends.
I'm using the FC5 version of kermit. My .kermrc looks like:
set modem type none
set line /dev/ttyS0
set carrier-watch off
set speed 115200
set flow rts/cts
set parity none
set stop-bits 1
connect
Not sure what the difference is between "/dev/tty0" and
"/dev/ttyS0"...
-Philip
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
- Follow-Ups:
- Re: Problems w/ serial flow control
- From: Mikkel L. Ellertson
- Re: Problems w/ serial flow control
- References:
- Problems w/ serial flow control
- From: Philip Prindeville
- Re: Problems w/ serial flow control
- From: Tim
- Re: Problems w/ serial flow control
- From: Philip Prindeville
- Re: Problems w/ serial flow control
- From: Rick Stevens
- Problems w/ serial flow control
- Prev by Date: lvm boot from second volume group
- Next by Date: Re: Fedora Core 5 LDAP client authentication problem with Solaris 9 iPlanet LDAP Server
- Previous by thread: Re: Problems w/ serial flow control
- Next by thread: Re: Problems w/ serial flow control
- Index(es):
Relevant Pages
- Re: Problems w/ serial flow control
... the two serial ports on the m/b. ... RTS/CTS or XON/XOFF flow control,
... use hardware handshaking. ... (Fedora) - Re: Problems w/ serial flow control
... the two serial ports on the m/b. ... RTS/CTS or XON/XOFF flow control,
... use hardware handshaking. ... (Fedora) - Re: Accessing peripherals from a managed application
... You call the Win32 APIs for serial ports. ... beitman AT applieddata DOT
net ... Maybe you open the driver with CreateFile, ... Call on the imported
functions to access the hardware. ... (microsoft.public.windowsce.app.development) - Re: Bug in X86 serial port driver in CE.NET 4.2 ?
... > Yeah I have noticed that too on some UARTs. ... From the behaviour I am
seeing with my driver it seems to ... > connected up (system configurable to control
different pieces of hardware). ... > no serial ports and no hang with
my driver. ... (microsoft.public.windowsce.platbuilder) - Re: [REVIEW] move tty lock/initial up in the stack
... Well, the hardware doesn't know, but the state of the hardware does ... :>:
The major difference is that serial ports are rapidly headed into ... The serial layer
is a spigot. ... I'll plow forward on the cyclades driver I'm working on then. ...
(freebsd-arch)