On Wed, Aug 16, 2017 at 09:32:11PM +0800, Hangbin Liu wrote:
> @@ -322,7 +366,7 @@ static void reconfigure(struct node *node)
>
> if (c->new_state) {
> if (c->new_state == PS_MASTER)
Another issue here. When we run phc2sys in slave mode and phc index changed
(
When parsing the argument, the minimum value should be -DBL_MAX instead
of DBL_MIN, which is the smallest positive value.
Signed-off-by: Miroslav Lichvar
---
phc_ctl.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/phc_ctl.c b/phc_ctl.c
index 461f2ac..a4daa4e 100644
--- a/ph
On Fri, Sep 08, 2017 at 06:00:50PM +0100, Alan Young wrote:
> On 08/09/17 13:27, Richard Cochran wrote:
> > Last time I looked, I didn't see any way to get a useful Tx time
> > stamp, due to aggregation and the opaque firmware blobs in the radio
> > chips.
> >
> > But if you see a way in the ath9k
On 11/09/17 13:45, Miroslav Lichvar wrote:
Is there an upper bound on the latency which could be used to fix
the timestamp as if it was captured before the transmission?
Well, I guess there is a upper bound but I think it could possibly be
much larger than the mean or median value.
I think
I have a system with two network ports running PTPv2/IPv6 (boundary
clock) and I'm using phc2sys (v1.8) to synchronize the the two PHC
devices associated with each ethernet port (JBOD enabled). I also want
the system clock (CLOCK_REALTIME) synchronized to one of the PHC
devices. I'm running p
On Mon, Sep 11, 2017 at 09:59:03AM -0500, Mike Lynch wrote:
>
>phc2sys -a -r
>
>
> The issue I'm experiencing is that when both of the PTP ports are in modes
> (both are in PTP state MASTER) that disqualifies them as the "master" in
> phc2sys, the system clock is not synchronized to whicheve
On 09/11/2017 02:21 PM, Richard Cochran wrote:
So, when all of the ports of a system are in the MASTER state, then
the system is the Grand Master (GM). Normally, a GM has some global
time reference like GPS, but if you don't have that, then you can tell
phc2sys to use the GM's CLOCK_REALTIME in
