You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our application uses the timestamps from when frames arrive (setsocketopt with SO_TIMESTAMPING). This seems to not be implemented. For us it would be great if it was.
The text was updated successfully, but these errors were encountered:
It would be great if the actual timestamp recorded on the actual physical CAN device was delivered to the listener so that it can be read the same way as you would do with a normal SocketCAN.
Probably there is no easy way to do this in userspace as you would need to overwrite the time the kernel at which the kernel received the packet. If you find a way to do that, the timestamp could be added to the protocol with some effort.
Our application uses the timestamps from when frames arrive (setsocketopt with SO_TIMESTAMPING). This seems to not be implemented. For us it would be great if it was.
The text was updated successfully, but these errors were encountered: