GGZ8

> Please squash everything into one commit. Done! 👍

Sounds good, the changes you suggested enable a more precise replay of the original trace. The use of the `nanosleep` family of functions ensure a more efficient CPU sharing. However,...

I agree with marckleinebudde that is not possible to implement real time sending from stdin. I modified the implementation to accept as input traces in which messages have absolute timestamps,...

Since the -r option check the presence of an input file, the only way to use is `-I input_file -r`. I implemented the solution you suggested in https://github.com/linux-can/can-utils/pull/521#issuecomment-2126328951 removing the...

I think that the variable name should remain `gap_from_file` since we are still reading the gaps from the input trace, just avoiding the preprocessing phase. keep in mind that reading...

When using the `-g ` option, the interval between CAN frames is kept fixed according to the value of `g`, so messages are sent every ``. In contrast, the busy...

Dear maintainers, I implemented the solution suggested in https://github.com/linux-can/can-utils/pull/521#issuecomment-2117173507 using the `SO_TXTIME` like the `cangen` tool does, however the results obtained introduce a non-negligible delay in the replay of the...