On Mon, May 15, 2017 at 08:14:52AM +0200, Morten Flå wrote:
> This is how the SMPTE 2059-2 is defined with messageId field set to
> Management Message and action set to Command followed by a
> Organization Extension TLV, so I guess someone did not think this
> through.
Oh man.
I guess we'll have
Hi,
Thanks for the clarification.
This is how the SMPTE 2059-2 is defined with messageId field set to
Management Message and action set to Command followed by a
Organization Extension TLV, so I guess someone did not think this
through.
Thanks,
Morten
--
On Fri, May 12, 2017 at 12:46:45PM +0200, Morten Flå wrote:
> In port.c:2259 we receive a packet, and the packet is rightly tagged
> as a management msg type in the common message header, and we're thus
> forwarded to the clock_manage function.
Ok, so the packet is a management message...
> In th
Hi,
I don't believe this is the case.
By following the current code sequence from git
d1bb9ecbd5a77cdb8d93accfa8c1bbf705002de0
In port.c:2259 we receive a packet, and the packet is rightly tagged
as a management msg type in the common message header, and we're thus
forwarded to the clock_manage fu
On Fri, May 12, 2017 at 09:03:51AM +0200, Morten Flå wrote:
> I'm currently testing a PTP Grandmaster clock that has the ability to
> send out Organization Extension TLVs. However, it seems like ptp4l
> treats these messages as a normal management message. The result of
> this is that ptp4l evaluat
