From: Alexander Stein <alexander.stein@systec-electronic.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: linux-can@vger.kernel.org
Subject: Re: exclusive access to can interface
Date: Tue, 22 Jan 2013 10:41:03 +0100 [thread overview]
Message-ID: <3261122.aWhS3clJQh@ws-stein> (raw)
In-Reply-To: <50EB10F4.6070308@pengutronix.de>
Hello again,
On Monday 07 January 2013 19:16:20, Marc Kleine-Budde wrote:
> On 01/07/2013 05:52 PM, Alexander Stein wrote:
> > is there a way to get exclusive (write) access to a CAN interface, so
> > that only one bound socket can write CAN frames on the bus?
>
> No, what's the use case?
I have now a more detailed view about the customers request and background: The problem runs some (time consuming) tests using CAN and they want to prohibit CAN write access meanwhile in order to prevent e.g. some (mis-)configuration of CAN devices or firmware updates. In such a case the test might shutdown and needs to be restarted. During the test nobody alse should be allowed to write to the CAN bus. I think this is justified.
It seems this is unrelated to CANopen or user application started twice, like I've expected and written before.
Best regards,
Alexander
next prev parent reply other threads:[~2013-01-22 9:41 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
2013-01-08 10:08 ` Wolfgang Grandegger
2013-01-08 10:15 ` Heinz-Jürgen Oertel
2013-01-22 9:41 ` Alexander Stein [this message]
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=3261122.aWhS3clJQh@ws-stein \
--to=alexander.stein@systec-electronic.com \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.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.