From: "Heinz-Jürgen Oertel" <oe@port.de>
To: Oliver Hartkopp <oliver.hartkopp@volkswagen.de>
Cc: Alexander Stein <alexander.stein@systec-electronic.com>,
Marc Kleine-Budde <mkl@pengutronix.de>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: exclusive access to can interface
Date: Tue, 8 Jan 2013 10:18:27 +0000 [thread overview]
Message-ID: <2287848.8ERXcjpij0@uschi> (raw)
In-Reply-To: <50EBF058.5050400@volkswagen.de>
Am Dienstag, 8. Januar 2013, 11:09:28 schrieb Oliver Hartkopp:
> .....
> This should be solved by the system setup.
+1
> E.g. if you start two applications using/providing identical resources at
> the same time, you'll always get into trouble.
>
> If you start two inetd daemons, the second one would fail as he would like
> to bind the same IP ports. But this kind of mechanic is not available with
> CAN sockets.
>
> I would tend to make sure that the Node-ID is always unique in your system.
> What would happen, if you start a Node-ID on your host that already exists
> on the CAN networks attached to the system? You have to deal with that too:
> E.g. terminate myself with some error logging if i see my own Node-ID
that is the point, correct.
> .....
regards
Heinz
next prev parent reply other threads:[~2013-01-08 10:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 16:52 exclusive access to can interface Alexander Stein
2013-01-07 18:16 ` Marc Kleine-Budde
2013-01-08 9:23 ` Alexander Stein
2013-01-08 9:32 ` Marc Kleine-Budde
2013-01-08 9:48 ` Alexander Stein
2013-01-08 10:09 ` Oliver Hartkopp
2013-01-08 10:18 ` Heinz-Jürgen Oertel [this message]
2013-01-08 10:08 ` Wolfgang Grandegger
2013-01-08 10:15 ` Heinz-Jürgen Oertel
2013-01-22 9:41 ` Alexander Stein
2013-01-22 12:53 ` Kurt Van Dijck
2013-01-22 13:36 ` Alexander Stein
2013-01-07 18:37 ` Oliver Hartkopp
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=2287848.8ERXcjpij0@uschi \
--to=oe@port.de \
--cc=alexander.stein@systec-electronic.com \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=oliver.hartkopp@volkswagen.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.