From: Grant Edwards <grant.b.edwards@gmail.com>
To: linux-serial@vger.kernel.org
Subject: Re: [PATCH] Documentation about RS485 serial communications
Date: Tue, 16 Nov 2010 15:52:11 +0000 (UTC) [thread overview]
Message-ID: <ibu9bb$k6c$1@dough.gmane.org> (raw)
In-Reply-To: A00955ACF1104CC28630FA1EAA4DF591@acksys.local
On 2010-11-16, Tosoni <jp.tosoni@acksys.fr> wrote:
>> I have seen hardware (kontron pmc-6l) that was capable of switching
>> between RS232, RS485 and one other standard by software.
>>
>> Is such hw common? If so, should we have standard interface?
>
> I believe it is neither common nor a good thing.
People who need multiple interface types disagree with you as to
whether it's a good thing or not.
> Dynamically switching between electrical levels means that the remote
> device must be capable of handling both electrical levels, else it
> might be damaged (i.e., when the serial card is configured to RS485
> but switches to RS232 when reset).
Nobody said anything about doing it "dynamically", and if you read the
manuals for the cards in question, it specifically says not to do
that. [Though if you look at the electrical specs for any reputable
RS485/422/232 driver/receiver you'll see that they're all spec'ed to
withstand that sort of thing without damage.]
The way it's done is that the card is installed, the ports are
configured, and then the cabling is hooked up.
> Or, different pins must be used for RS232 and RS485 (then software
> switching is not really useful).
That's not usually how it's done.
--
Grant Edwards grant.b.edwards Yow! Don't hit me!! I'm in
at the Twilight Zone!!!
gmail.com
next prev parent reply other threads:[~2010-11-16 15:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100408111310.524f7354@lxorguk.ukuu.org.uk>
[not found] ` <4BBDD71D.1010700@evidence.eu.com>
[not found] ` <4BFD1FB6.8050405@atmel.com>
[not found] ` <4BFE2F38.8050200@evidence.eu.com>
[not found] ` <4BFE41FD.2080804@atmel.com>
[not found] ` <20100527102917.GB31253@pengutronix.de>
[not found] ` <4C626CBF.9020609@evidence.eu.com>
[not found] ` <20100811083214.21d2919e.randy.dunlap@oracle.com>
[not found] ` <4C669120.8080707@evidence.eu.com>
[not found] ` <4C686411.3060500@oracle.com>
[not found] ` <20100815221906.GA24153@n2100.arm.linux.org.uk>
2010-10-19 12:28 ` [PATCH] Documentation about RS485 serial communications Claudio Scordino
2010-10-19 14:29 ` Grant Edwards
2010-10-19 15:27 ` Alexander Stein
2010-10-19 17:22 ` Grant Edwards
2010-10-20 8:00 ` Alexander Stein
2010-10-20 18:56 ` Alan Cox
2010-10-24 11:29 ` Claudio Scordino
2010-11-10 9:17 ` Nicolas Ferre
2010-11-10 17:28 ` Greg KH
2010-11-11 10:22 ` Claudio Scordino
2010-11-16 14:30 ` Pavel Machek
2010-11-16 14:58 ` Tosoni
2010-11-16 15:52 ` Grant Edwards [this message]
2010-11-16 15:23 ` Grant Edwards
2010-11-16 15:28 ` Alexander Stein
2010-11-16 16:13 ` Matt Schulte
2010-11-16 16:28 ` Grant Edwards
2010-11-16 18:41 ` Matt Schulte
2010-11-16 19:29 ` Grant Edwards
2010-11-16 17:20 ` Alan Cox
2010-11-16 18:03 ` Grant Edwards
2010-11-16 20:04 ` Alan Cox
2010-11-30 19:19 ` Pavel Machek
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='ibu9bb$k6c$1@dough.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).