public inbox for linux-serial@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Halasa <khc@pm.waw.pl>
To: Tosoni <jp.tosoni@acksys.fr>
Cc: linux-serial@vger.kernel.org
Subject: Re: should RTS init in serial core be tied to CRTSCTS
Date: Wed, 14 Mar 2007 13:44:11 +0100	[thread overview]
Message-ID: <m3slc8c7vo.fsf@maximus.localdomain> (raw)
In-Reply-To: <001d01c76629$06da71a0$2e01a8c0@acksys.local> (Tosoni's message of "Wed, 14 Mar 2007 12:07:58 +0100")

"Tosoni" <jp.tosoni@acksys.fr> writes:

>> A flag alone is no help for half-duplex devices, they would need
>> a complete handshaking code.
>
> Not true.
> This is also the view of the former maintainer of drivers/serial.

It's just reality. If your IC in question does this in hardware
- fine, but you still have to support it in the driver, adding
a #define XXX doesn't help.

"Code talks".

> But
> obviously neither of you used half duplex devices before.

This is your "not true". I was using them, though they weren't
modems.

> There is no need for handshake, since half duplex is used in master/slave
> situations.

Not necesarily, there are CSMA/CD-style designs as well as token-ring
style.

> And I can insure you, that Windows handles this very well, using
> only the above-mentioned RTS_TOGGLE flag.

That means the DCE does all the buffering and handshaking. I'd say
it's not common, most devices are simpler.
-- 
Krzysztof Halasa

  reply	other threads:[~2007-03-14 12:44 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
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 [this message]
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=m3slc8c7vo.fsf@maximus.localdomain \
    --to=khc@pm.waw.pl \
    --cc=jp.tosoni@acksys.fr \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox