-
Notifications
You must be signed in to change notification settings - Fork 736
Use timespec #592
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Use timespec #592
Conversation
I think we're not allowed to change the output for the
Otherwise this is a good enhancement for the hardware timestamps. |
Yes. The 6 decimal places are fix in the CAN log file format for 20+ years now. And having the maximum rate of CAN frames on the CAN bus in mind we are already far beyond what is needed as a timestamp precision. Of course everyone might use a higher precision from timespec inside a SocketCAN application - but we have to stay with 6 decimal places in the log file format. |
We are using MCP2518FD with 25ns resolution and are planning to correlate that to PTP time. |
@RikusW Can you elaborate on you use case a but more, I have some proof of concept patches that implement a PTP clock for the mcp251xfd driver. |
@marckleinebudde We will be using 8 CAN ports with all of them exactly in sync and will be doing the PTP part in userspace for now. I'm working on https://tsn.systems/en/products/basicsolution/tsn-basicsolution-octocan/ |
I'm not generally against creating a new log file format flavor that supports a nanosecond resolution with a |
For now I just need to be able to view nanosecond timestamps, transmit/replay ability could be done at a later time even. |
Let's hold this PR in mind until it is completed with the other tools then. |
Use timespec instead of timeval so timestamp values with nanosecond resolution can be displayed.