All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Parkins <andyparkins@gmail.com>
To: linux-serial@vger.kernel.org
Subject: Re: tcdrain / TCSBRK / wait_until_sent delay
Date: Tue, 10 May 2005 08:44:59 +0100	[thread overview]
Message-ID: <200505100845.03206.andyparkins@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0505090825470.750@deadrat.localdomain>

[-- Attachment #1: Type: text/plain, Size: 2029 bytes --]

On Monday 2005 May 09 17:33, rich+ml@lclogic.com wrote:
> On Mon, 9 May 2005, Andy Parkins wrote:
> > Are you sure that RTSCTS flow control is what you think it is?  These
> > days RTS means "request to send to me" rather than "I request to send";
> > that allows RTS and CTS to be crossed over in null modem cables - and
> > puts the flow control in the receiver directly.
>
> Yep. RTS is an output from the PC, CTS is an input to the PC, weird
> cabling does not change this.

I wasn't suggesting otherwise; I think these days though, RTS doesn't mean 
that the PC is requesting to send it means the PC is open to receiving. 

http://www.pccompci.com/cable.html

Hence, when the RTS and CTS are crossed over in a null modem cable (which 
isn't by any means weird) RTS from device 1 lights up CTS in device 2 and 
vice versa -- exactly what would be required.  Although t

> > I'm coming to accept that what I'm after isn't possible.  How likely is
> > it that I could patch the serial_core kernel driver to do the RTS control
> > for me?  Am I going to end up in the same situation?
>
> I believe you will end up in the same situation.

As it happens, Christer Weinigel in another part of the thread suggested a 
solution that I've had great success with - so thankfully I don't have to go 
near the kernel :-)

> You might take a look at a usb-to-serial cable, kernel will 'mount' it as
> /dev/ttyUSB0 or something so the application doesn't have to know any
> better. However these cables contain PL2303 or similar uart which supports
> auto rts/cts if so enabled (the idea is to not push every control signal
> transient down the usb). Google for PL2303 spec, look for pl2303.c in the
> kernel.

That would be an excellent solution, and I still may look into that - the 
option of lots of serial ports via USB has a certain appeal.

Again, thanks for your help on this.  It's all been (and continues to be) very 
interesting.

Andy

-- 
Dr Andrew Parkins, M Eng (hons), AMIEE


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-05-10  8:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-05 15:50 tcdrain / TCSBRK / wait_until_sent delay Andy Parkins
2005-05-05 17:51 ` rich+ml
2005-05-06  8:01   ` Andy Parkins
2005-05-06 19:14     ` rich+ml
2005-05-07  9:35       ` Andy Parkins
2005-05-07 18:09         ` rich+ml
2005-05-09  8:01           ` Andy Parkins
     [not found]             ` <Pine.LNX.4.58.0505090825470.750@deadrat.localdomain>
2005-05-10  7:44               ` Andy Parkins [this message]
2005-05-09  8:16         ` Tosoni
2005-05-09  8:59           ` Russell King
2005-05-09 10:03             ` Tosoni
2005-05-09 10:13               ` Russell King
2005-05-09 15:43                 ` Theodore Ts'o
2005-05-07 10:32       ` Gerald Emig
2005-05-09  9:15 ` Christer Weinigel
2005-05-09  9:22   ` Christer Weinigel
2005-05-09 11:05     ` Andy Parkins
2005-05-09 15:53     ` Andy Parkins
2005-05-09 19:45     ` rich+ml

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=200505100845.03206.andyparkins@gmail.com \
    --to=andyparkins@gmail.com \
    --cc=linux-serial@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.