linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Halasa <khc@pm.waw.pl>
To: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
Cc: Robin Getz <rgetz@blackfin.uclinux.org>,
	Oleksiy Kebkal <kebkal@gmail.com>,
	Mike Frysinger <vapier.adi@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-serial@vger.kernel.org
Subject: Re: should RTS init in serial core be tied to CRTSCTS
Date: Thu, 08 Mar 2007 17:51:28 +0100	[thread overview]
Message-ID: <m3r6rz3chb.fsf@maximus.localdomain> (raw)
In-Reply-To: <45F01AA8.7010608@gmx.net> (Carl-Daniel Hailfinger's message of "Thu, 08 Mar 2007 15:16:08 +0100")

Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net> writes:

> Unless you want two machines to monitor each other via serial console and
> each of them has only one serial port. It's not perfect, but it works well
> enough despite all claims to the contrary.

Sure, if you don't need "input" (only "console logger" function and
not "initial input/output terminal"). It has nothing to do with the
RTS "problem", though.

BTW: reasonably working, standard-compliant USB-RS232 converters
cost $15 or so. Unfortunately not that all machines have USB ports.

I agree with Russell - mixing kernel console and application's
port is asking for trouble.

OTOH I wonder what does the device in question require WRT the
serial port and WRT RTS line in particular.
I know there are some half-duplex converters which drive RTS only
while sending and which require CTS to send. They are perhaps a bit
broken and require some CSMA-alike retransmissions etc.

I don't know if one can expect RTS to stay low all the time. Even
a simple /sbin/setserial from /etc/rc.* would drive it high for
a moment. I'm afraid the only way which makes sense may be using
a customized plug.
-- 
Krzysztof Halasa

  parent reply	other threads:[~2007-03-08 16:51 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-02  0:03 should RTS init in serial core be tied to CRTSCTS Mike Frysinger
2007-03-04 16:20 ` Robin Getz
2007-03-04 19:46 ` Russell King
2007-03-04 20:42   ` Robin Getz
2007-03-05  8:39     ` Russell King
2007-03-05 17:09   ` Mike Frysinger
2007-03-05 17:39     ` Tosoni
2007-03-05 17:56     ` Russell King
2007-03-05 18:13       ` Mike Frysinger
2007-03-06 20:40 ` Krzysztof Halasa
2007-03-06 23:24   ` Robin Getz
2007-03-07 12:46     ` Krzysztof Halasa
2007-03-07 13:38       ` Oleksiy Kebkal
2007-03-07 15:19       ` Robin Getz
2007-03-07 21:30         ` Oleksiy Kebkal
2007-03-08 13:44           ` Robin Getz
2007-03-08 13:48             ` Russell King
2007-03-08 14:16               ` Carl-Daniel Hailfinger
2007-03-08 14:20                 ` Russell King
2007-03-08 16:51                 ` Krzysztof Halasa [this message]
2007-03-08 18:43                   ` Tosoni
2007-03-09 20:39                     ` Krzysztof Halasa
2007-03-12  9:22                       ` Tosoni
2007-03-12 12:59                         ` Krzysztof Halasa
2007-03-14 11:07                           ` Tosoni
2007-03-14 12:44                             ` Krzysztof Halasa
2007-03-14 13:45                               ` Tosoni
2007-03-14 23:59                                 ` Krzysztof Halasa
2007-03-08 14:23               ` Oleksiy Kebkal
2007-03-08 14:28                 ` Russell King
2007-03-08 14:40                   ` Oleksiy Kebkal
2007-03-08 14:25               ` Oleksiy Kebkal
2007-03-08 20:23               ` Robin Getz
2007-03-08 20:40                 ` Russell King
2007-03-08 23:32                   ` Robin Getz
2007-03-09  8:57                     ` Russell King
2007-03-09 14:18                   ` Oleksiy Kebkal
2007-03-07 12:54     ` Oleksiy Kebkal
2007-03-07 13:03       ` Krzysztof Halasa
2007-03-07 20:04         ` Mike Frysinger
2007-03-07  5:13   ` Oleksiy Kebkal
2007-03-07 12:48     ` Krzysztof Halasa

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=m3r6rz3chb.fsf@maximus.localdomain \
    --to=khc@pm.waw.pl \
    --cc=c-d.hailfinger.devel.2006@gmx.net \
    --cc=kebkal@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=rgetz@blackfin.uclinux.org \
    --cc=vapier.adi@gmail.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;
as well as URLs for NNTP newsgroup(s).