> -Original Message-
> From: Richard Cochran
> Sent: Friday, February 26, 2021 10:58 PM
> To: Y.b. Lu
> Cc: linuxptp-devel@lists.sourceforge.net; Miroslav Lichvar
>
> Subject: Re: [Linuxptp-devel] [v2] msg: bump to IEEE 1588-2019 version
>
> On Fri, Feb 2
On Fri, Feb 26, 2021 at 02:42:40AM +, Y.b. Lu wrote:
> My fault. I Just forgot the message printed. How about,
>
> versionNumber 2
> minorVersionNumber 1
>
> This may match field definition in standard. Considering it's only message
> printed, I think either is ok.
> What do y
> -Original Message-
> From: Richard Cochran
> Sent: Friday, February 26, 2021 1:09 AM
> To: Y.b. Lu
> Cc: linuxptp-devel@lists.sourceforge.net; Miroslav Lichvar
>
> Subject: Re: [Linuxptp-devel] [v2] msg: bump to IEEE 1588-2019 version
>
> On Thu, Feb 2
On Thu, Feb 25, 2021 at 09:09:23AM -0800, Richard Cochran wrote:
> I think we should have pmc print versionNumber 2.1 here (format %u.%u)
> and then ask Miroslav to adapt the test suite...
>
> Miroslav, I'm thinking the way to handle this in the test suite is to
> accept both versionNumber 2 and v
On Thu, Feb 25, 2021 at 03:20:41PM +0800, Yangbo Lu wrote:
> IEEE 1588-2019 specified new UInteger4 type minorVersionPTP field
> in header, and minorVersionNumber data in portDS. It has the value
> 1 for IEEE 1588-2019, and has the value 0 for IEEE 1588-2008.
>
> This patch is to bump to IEEE 1588
IEEE 1588-2019 specified new UInteger4 type minorVersionPTP field
in header, and minorVersionNumber data in portDS. It has the value
1 for IEEE 1588-2019, and has the value 0 for IEEE 1588-2008.
This patch is to bump to IEEE 1588-2019 version directly in message,
considering v2.1 and even future v
