From: Wolfgang Grandegger <wg@grandegger.com>
To: Alexander Stein <alexander.stein@systec-electronic.com>
Cc: Marc Kleine-Budde <mkl@pengutronix.de>, linux-can@vger.kernel.org
Subject: Re: exclusive access to can interface
Date: Tue, 08 Jan 2013 11:08:36 +0100 [thread overview]
Message-ID: <50EBF024.1030507@grandegger.com> (raw)
In-Reply-To: <2293513.Wi876mfY7y@ws-stein>
On 01/08/2013 10:23 AM, Alexander Stein wrote:
> Hello Marc,
>
> 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?
>
> This was a customers request in order to prevent multiple applications (or
> instances) to send CAN frames on a specific CAN interface at the same time
> with the very same CAN-IDs. Concurrent reads shall still be allowed!
Application == CANopen?! It's like giving exclusive access to a network
device. Isn't that possible? Well, at a first glance I have not found
anything like that.
Wolfgang.
next prev parent reply other threads:[~2013-01-08 10:08 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 [this message]
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=50EBF024.1030507@grandegger.com \
--to=wg@grandegger.com \
--cc=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.