From: Grant Edwards <grant.b.edwards@gmail.com>
To: linux-serial@vger.kernel.org
Subject: Re: RS485 implementation questions (primarly in atmel_serial.c)
Date: Thu, 31 Jan 2013 14:42:03 +0000 (UTC) [thread overview]
Message-ID: <kedvrr$qb0$1@ger.gmane.org> (raw)
In-Reply-To: 000401cdfef7$0d4a9020$27dfb060$@acksys.fr
On 2013-01-30, Jean-Pierre Tosoni <jp.tosoni@acksys.fr> wrote:
>
> Well, you need to ascertain that the previous frame is all out AND
> the RTS has dropped before sending a new frame. Else the receiver
> might think it is the same long frame. Using TXEMPTY interrupt avoids
> setting an extra timer. However in the real life you are half-duplex
> and never send two frames in a row without waiting for an answer.
> Other than that I agree with your remark.
>
>> rare. But this function is not especially related to RS485. It is
>> also applicable in RS232 mode. So in my view it is not the
>
> True, it applies to some half-duplex RS232 radio modems too AFAIK.
It applies to half duplex modems and line-drivers whether they're
radio or not. Believe it or not, Bell-202 half-duplex over plain old
copper wire is still used a lot in the process control industry.
But, because of the general brokeness of both Windows and Linux serial
drivers when it comes to half-duplex communications, many of the
Bell-202 modems sold these days have automatic tx data detection and
handle the "RTS toggle" function themselves.
--
Grant Edwards grant.b.edwards Yow! Psychoanalysis??
at I thought this was a nude
gmail.com rap session!!!
next prev parent reply other threads:[~2013-01-31 14:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 22:56 RS485 implementation questions (primarly in atmel_serial.c) Guido Classen
2013-01-24 0:10 ` Grant Edwards
2013-01-25 9:13 ` Guido Classen
2013-01-25 15:39 ` Grant Edwards
2013-01-29 21:56 ` Guido Classen
2013-01-29 22:29 ` Grant Edwards
2013-01-30 15:24 ` Guido Classen
2013-01-30 17:57 ` Grant Edwards
2013-01-30 14:35 ` Jean-Pierre Tosoni
2013-01-31 14:42 ` Grant Edwards [this message]
[not found] <CAJa4H3cYT6QOaacWEy2yZjb0hM3m4p+0L2_fXBYv8tWajYkmGw@mail.gmail.com>
2013-01-30 10:30 ` Claudio Scordino
[not found] ` <510A3740.6060809@evidence.eu.com>
[not found] ` <CAJa4H3dG4V6viRbVQBgHQKtJr4Sz26mkhj8-kT7RFaLGRFXW1g@mail.gmail.com>
[not found] ` <51125488.7090408@evidence.eu.com>
[not found] ` <CAJa4H3eNAS7B+aGnN0D3WJMPVtE=sxp5HhRMutq-TrBOmXb7dw@mail.gmail.com>
[not found] ` <5114B500.7050007@evidence.eu.com>
2013-02-08 12:12 ` Guido Classen
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='kedvrr$qb0$1@ger.gmane.org' \
--to=grant.b.edwards@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 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).