On Tue, Nov 28, 2023 at 12:53:38PM +0100, Miroslav Lichvar wrote: > On Sun, Nov 26, 2023 at 11:10:05AM -0800, Richard Cochran wrote: > > The Rx filters are applied globally at the device level, but the PTP > > operates at the application level. This means that the Rx filter are > > shared between applications. And so you can see that one application > > cannot simply change the shared global settings at run time. > > This problem already exists, e.g. with ptpv2-l4-event vs ptpv2-l2-event.
That is totally different. As long as the HW supports the given transport, then it works. > If the > hardware which cannot timestamp all event messages is very rare, ok, > maybe it's not worth the trouble. And it simply cannot work in real life. > However, timestamping only sync messages has an advantage with very > large number of clients as they don't have timestamp each other's > delay requets and timestamping of sync messages is more reliable. Actually, in hardware is it much simpler and more efficient just to time stamp every frame. (The reporting can be selectable if the application doesn't care about some frame types) _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
