Thanks Richard, I will try to better describe my scenario. On my input-only ITU 8271 interface I receive a Time Event message (with T1=Time and T2 timestamp and a configurable "cable delay") and at the same time I receive an Announcement-like message. Ideally, this port should work like any other slave port (slave only). My question is: how can I push T1, T2 and the "cable delay' into linuxPTP? (T3 and T4 can be derived easily). And How Can I push the announcement-like message, that can be easily mapped 1-to-1 to a PTP Announce message? You speak about an already available IPC interface, but, sorry if I ask again, can you point me to the exact calls to use? I will appreciate it a lot. Another issue is that my hw doesn't have any "linux" interface, but a creepy API that provides the TS in some way and I cannot use RAW transport. I would like to avoid touching raw.c code, but, again, I have not found any better way to implement the transport. You are right saying that this is an orrible choice, but I'm not understanding how I can create this building block outside the linuxPTP sources without hacking the transport.*
This is the model PTP raw <--- creepy ETH1 driver --> [ Supervisor ] <--- ??? ---> [LinuxPTP] PTP raw <--- creepy ETH2 driver --> [ Supervisor ] <--- ??? ---^ ??? is the interface that I'm not understanding. Thanks again for your patience (but I started just now to dive into the ptp world). luigi Il giorno mer 11 nov 2020 alle ore 13:26 Richard Cochran < richardcoch...@gmail.com> ha scritto: > On Wed, Nov 11, 2020 at 10:04:46AM +0100, Luigi 'Comio' Mantellini wrote: > > This is an aspect really interesting for me, because in my environment I > > haven't true linux interfaces and the serial line discussed above. > > Is there an example of "new transport" implementation using your API? > > Yes, there is udp, udp6, and raw. > > > My idea is to directly hack transport.c/.h files adding a new entry > inside > > the create switch. Is it the correct way? > > No, that is a terrible idea. > > > Or do you have any other > > suggestions? > > Yes, and I already told you: > > > > 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 > -- *Luigi 'Comio' Mantellini* My Professional Profile <http://www.linkedin.com/in/comio> *"UNIX is very simple, it just needs a genius to understand its simplicity." [cit.]*
_______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
