Pev

Ah, OK, that's interesting, I had wondered if something like that was the case! Do you want anything else from my end? I've got a easily testable forked copy of...

Ah, nice one, thanks. Having a quick dig, you're right - it will be universal as it's part of rpm : [https://github.com/rpm-software-management/rpm/blob/6d4c68ba10b9713f3e599cf20c2455eb80e9bfe1/lib/Makefile.am#L119w](https://github.com/rpm-software-management/rpm/blob/6d4c68ba10b9713f3e599cf20c2455eb80e9bfe1/lib/Makefile.am#L119w) That's a tidy resolution!

> Any update on this? I’d love to get it in as I’m using it in derived code we have here and I’m sure it’s helpful, but I’m not sure...

> > I’d love to get it in as I’m using it in derived code we have here and I’m sure it’s helpful, but I’m not sure what changes I...

I've done some tests to illustrate better using a piece of hardware sending out a packet on a 1.95ms cycle. Timestamps imported into a spreadsheet and a scatter plotted of...

Digging into the code it looks like socketcan uses SO_TIMESTAMPNS which is system timestamp only. Comparing to how candump implements hardware timestamps I can see that you need to use...

Pull request #1882 fixes this.