Re: slcanpty

[Oliver Hartkopp <socketcan@hartkopp.net>]

On 11.06.2013 23:19, janusz.uzycki@elproma.com.pl wrote:
>>>> The SLCAN protocol is a nice and simple ASCII protocol that fits for many
>>>> purposes. But it also has some disadvantages e.g. when you want timestamps
>>>> and
>>>> additional error signaling you can usually get from a CAN controller.
>>>>
>>>>> (https://github.com/dschanoeh/socketcand/blob/master/doc/protocol.md) some
>>>
>>> I noticed that both slcanpty and socketcand don't implement bitrate
>>> settings yet.
>>> iproute2 includes libnetlink but the library avoids CAN support.
>>> libsocketcan seems to be the best choice but libnl also good.
>>>
>>> What do you prefer for CAN interface control?
>>
>> I'm personally using the standard ip tool from iproute together with
>> this script:
>>
>> https://gitorious.org/linux-can/can-misc/blobs/master/etc/can_if
> 
> The script is nice but I thought about "< can0 B bitrate sample_point tq
> prop_seg phase_seg1 phase_seg2 sjw brp >" command in
> https://github.com/dschanoeh/socketcand/blob/master/doc/protocol.md exactly.
> I looked for a proper code in socketcand and I didn't find. Is the command
> planned?

Not yet.

Today the socketcand can run as normal user.

When we want to add the "B" option (which is generally a good idea) we need to
take care to run socketcand as root or as some sudo user to be able to
configure the CAN interfaces.

Configuring the CAN interfaces as administrator on the host that is connected
to CAN interfaces is IMO a good solution. Don't know what happens, if multiple
users connected to the socketcand and specifiy different bitrates %-(

> I'm asking because if it would be implemented in socketcand it could be also
> implemented in slcanpty for S/s command support. Unfortunately using an
> external library will introduce dependency :/

Btw. i would recommend the libsocketcan from the pengutronix git then.

Best regards,
Oliver