From: Grant Edwards <grant.b.edwards@gmail.com>
To: linux-serial@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation about RS485 serial communications
Date: Tue, 16 Nov 2010 16:28:21 +0000 (UTC) [thread overview]
Message-ID: <ibubf5$ev$1@dough.gmane.org> (raw)
In-Reply-To: AANLkTi=grehSnfWzCDtSXXmNb=-NAwbHHJ_P1XPyOuw8@mail.gmail.com
On 2010-11-16, Matt Schulte <matts@commtech-fastcom.com> wrote:
> On Tue, Nov 16, 2010 at 8:30 AM, Pavel Machek <pavel@ucw.cz> wrote:
>> Hi!
>>
>>> Documentation about RS485 serial communications
>>
>> 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?
>
> In my opinion this type of card is not that common. Generally
> speaking the achievable baud rates for this type of multi-protocol
> card are very limited because of limitations of the transceiver chips.
I'm curious which selectable interface cards you're talking about that
are slow? The ones I'm familiar with generally support baud rates up
to either 460K bps or 921K bps
> It seems that most of the time people would rather have a faster
> serial port than one that does several different voltages.
Where did you find a selectable interface serial card that couldn't
support high baud rates?
--
Grant Edwards grant.b.edwards Yow! Well, O.K.
at I'll compromise with my
gmail.com principles because of
EXISTENTIAL DESPAIR!
next prev parent reply other threads:[~2010-11-16 16:28 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
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 [this message]
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='ibubf5$ev$1@dough.gmane.org' \
--to=grant.b.edwards@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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).