On Mon, Sep 11, 2023 at 09:53:54PM +, Keller, Jacob E wrote:
>
>
> > -Original Message-
> > From: Eyal Itkin via Linuxptp-devel
> > Sent: Sunday, September 10, 2023 9:23 AM
> > To: linuxptp-devel@lists.sourceforge.net
> > Subject: [Linuxptp-de
> -Original Message-
> From: Eyal Itkin via Linuxptp-devel
> Sent: Sunday, September 10, 2023 9:23 AM
> To: linuxptp-devel@lists.sourceforge.net
> Subject: [Linuxptp-devel] [PATCH] [pmc] Avoid conflicting port IDs over PMC
> UDS
>
> The UDS interface is cur
The UDS interface is currently associated with a clock ID of zeros
and a 16-bit port number which is the process id. However, the
process id on Linux can easily by bigger than 16 bits (supposed
to be limited to 22 bits). This means that several linuxptp processes
(pmc and phc2sys for instance) can
The UDS interface is currently associated with a clock ID of zeros
and a 16-bit port number which is the process id. However, the
process id on Linux can easily by bigger than 16 bits (supposed
to be limited to 22 bits). This means that several linuxptp processes
(pmc and phc2sys for instance) can
