Re: exclusive access to can interface

[Alexander Stein <alexander.stein@systec-electronic.com>]

Hello,

On Tuesday 08 January 2013 10:32:25, Marc Kleine-Budde wrote:
> 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!
> 
> Sending CAN frames is proper serialized by the networking subsystem :)
> If back to back CAN frames are a problem it seems the design of the
> application is fishy.

I don't think serializaton or back to back frames are the problem. Think of CANopen there would be the same Node-ID twice on the bus.

Alexander