Lasse Johnsen

@wbb12 I'm a little confused. Why can't you just use software timestamping? The fact that the in-kernel software timestamping is not supported with the so_timstamping api does not prevent you...

Yeah, they are both part of the so_timestamping subsystem. I don’t understand LinuxPTP well, but in Timebeat if you had neither option we capture a timestamp just before the send...

@popcornmix I think not a bad compromise.... what approach do you prefer? I can submit patch to upstream or @jclark can do it. ptp4l will then work on the 4revB...

Hi Phil, Sorry for the delay. I confirm this works on the CM4 and enables HWTS. Great solution. Thank you for highlighting it! Merge away… :-) All the best, Lasse...

It's very old and uncool. Can't you use SO_TIMESTAMPING instead?

@popcornmix @ghollingworth one doesn't like to tag people to draw people into one's problems, but it feels like there could be an underlying problem here. Any ideas? Again, to summarise:...

@P33M Thank you for taking the time. As I indicated above, it fails with -IGC_ERR_SWFW_SYNC (also -13) and it does so because from igc_probe it's the first time the driver...

> If I assume the link has been up since before the trace started, that's a very long initialisation time - CM4 might just be slower and get lucky with...

Hi Wis! Nice speaking with you the other day. I think you are doing great work :-) For the production card I don't really mind. For the "normal" modular Timecard,...

> ``` > Region 0: Memory at 1b00000000 (32-bit, non-prefetchable) [virtual] [size=1M] > Region 3: Memory at 1b00200000 (32-bit, non-prefetchable) [size=16K] > ``` > > At first glance that looks...