On Wed, Aug 18, 2021 at 05:25:53PM +, Eric Decker wrote:
> So the proper fix would be to ensure the ptp4l's write() is non blocking.
> EDecker: I wonder if that approach would have unexpected consequences.
No, it would not. ptp4l should never block because of issues at the
other end of the
On Thu, Aug 19, 2021 at 02:32:49PM +, Eric Decker wrote:
> I can see now how to use interactive mode. I suggest considering
> documenting this in the manpages and the help for pmc. Some
> examples in the manpages would be helpful.
I agree.
Any patches with documentation improvements will
Thank you, Erez.
I can see now how to use interactive mode. I suggest considering documenting
this in the manpages and the help for pmc. Some examples in the manpages would
be helpful.
Eric Decker
-Original Message-
From: Geva, Erez
Sent: Thursday, August 19, 2021 5:19 AM
To: Eric
Hi,
Entering the pmc tool interactive mode is simple.
Run the pmc tool without a management command.
For example:
Using direct mode:
# pmc -u -f /etc/linuxptp/ptp4l.conf 'get VERSION_NUMBER' 'get PRIORITY1'
Using interactive mode:
# pmc -u -f /etc/linuxptp/ptp4l.conf
Now you can enter:
get
Hi Erez,
I thought it might be better to take this part of the conversation offline, but
maybe it will benefit others.
How do you run pmc in interactive mode? I do not see that in the documentation.
What is libpmc? Is it a part of the standard Linux PTP distribution, or is it
a supplement
Hi,
Regarding: "pmc executes as a new process each time it is called".
1. No you can run the pmc tool in interactive mode. Then send new requests,
line by line and with increasing the sequence ID.
2. You can use the libpmc library https://sf.net/projects/libpmc/, The library
allow you to
Response below tagged as EDecker:
Eric Decker
-Original Message-
From: Richard Cochran
Sent: Wednesday, August 18, 2021 12:23 PM
To: Eric Decker
Cc: linuxptp-devel@lists.sourceforge.net
Subject: Re: [Linuxptp-devel] [PATCH] Only forward responses to UDS port with
corresponding
On Mon, Aug 16, 2021 at 03:38:21PM +, Eric Decker wrote:
> Subject: [PATCH] Only forward responses to UDS port with corresponding
> requests on the UDS port, and always send management with a unique sequence
> count from uds.
The subject line should be ONE sentence, please.
>
> 1.
Subject: [PATCH] Only forward responses to UDS port with corresponding requests
on the UDS port, and always send management with a unique sequence count from
uds.
1. Only forward responses to UDS port with a corresponding requests on the
UDS port.
The context of the issue/feature:
See
