On Wed, Nov 04, 2020 at 09:43:52AM +0100, Luigi 'Comio' Mantellini wrote: > The announce message should br managed by protocol as a normal PTP Announce > message to handle the BMC and select the grandmaster (I suppose).
Don't conflate those two. > From my protocol picture I think that ts2phc is not the best solution > because: > - this cover only sink scenario (slave). What about source scenario > (master) For this you don't need ts2phc. You can use ioctls directly from your supervisor program, call out to testptp, or even use a shell script to configure the PPS via sysfs. > - TAM cannot be handled in this way You supervisor program can do this. > - We cannot select automatically the best source between the serial and > the other eth interface You supervisor program can do this as well. > Do you have any suggestions in order to handle the message (announcement in > primis). An idea that I have is to have a sort of "RAW_SERIAL" transport > that translate the TEM messages into SYNC and TAM to PTP Announce. Don't over-engineer it. Just write a program that controls the serial port with PPS. All of the IPC interfaces that you need are already implemented. There is no need to change ptp4l, phc2sys, or ts2phc. Thanks, Richard _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
