From: David Woodhouse <dwmw2@infradead.org>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Chris Fowler <cfowler@outpostsentinel.com>,
Robert White <rwhite@casabyte.com>, Ed Vance <EdV@macrolink.com>,
"'Linux PPP'" <linuxppp@indiainfo.com>,
linux-serial@vger.kernel.org,
"'linux-kernel'" <linux-kernel@vger.kernel.org>
Subject: Re: RS485 communication
Date: 16 Mar 2003 10:51:47 +0000 [thread overview]
Message-ID: <1047811906.22070.44.camel@imladris.demon.co.uk> (raw)
In-Reply-To: <20030316103517.B14404@flint.arm.linux.org.uk>
On Sun, 2003-03-16 at 10:35, Russell King wrote
> No - that's not how RS485 works. With a balanced line, the result
> that any one receiver will see will depend on it's position on the
> line and the relative distance to each transmitter, the resistance
> of the line, and the manufacturer/type of the RS485 transceiver.
> In other words, the state you see is indeterminent.
Ah, OK. Then I must have been mistaken in thinking that CAN was based on
RS485 -- or mistaken in remembering that that's how CAN does collision
avoidance I suppose, but I suspect the former is more likely.
Thanks for the correction.
--
dwmw2
next prev parent reply other threads:[~2003-03-16 10:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-13 16:56 RS485 communicatio Ed Vance
2003-03-13 17:46 ` Richard B. Johnson
2003-03-13 22:54 ` RS485 communication Robert White
2003-03-13 23:30 ` Chris Fowler
2003-03-15 8:07 ` Robert White
2003-03-15 15:42 ` Chris Fowler
2003-03-15 12:46 ` David Woodhouse
2003-03-16 0:56 ` Alan Cox
2003-03-16 10:05 ` David Woodhouse
2003-03-16 10:35 ` Russell King
2003-03-16 10:51 ` David Woodhouse [this message]
2003-03-15 19:46 ` RS485 communicatio Pavel Machek
2003-03-16 19:57 ` Alan Cox
2003-03-17 5:41 RS485 communication Cigol C
2003-03-20 23:09 ` Robert White
2003-03-20 23:17 ` Chris Fowler
2003-03-21 2:48 ` Robert White
2003-03-24 11:43 Cigol C
2003-03-25 3:23 ` Paul Mackerras
[not found] <20030324143723.11625.qmail@indiainfo.com>
2003-03-24 16:41 ` Joachim Franek
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=1047811906.22070.44.camel@imladris.demon.co.uk \
--to=dwmw2@infradead.org \
--cc=EdV@macrolink.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cfowler@outpostsentinel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linuxppp@indiainfo.com \
--cc=rmk@arm.linux.org.uk \
--cc=rwhite@casabyte.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
all inboxes | Powered by JetHome®