On Mon, Aug 10, 2015 at 11:13:00PM +0200, Richard Cochran wrote:
@@ -151,8 +157,16 @@ static int udp_open(struct transport *t, const char
*name, struct fdarray *fda,
enum timestamp_type ts_type)
{
struct udp *udp = container_of(t, struct udp, t);
+ struct
On Tue, Aug 11, 2015 at 11:43:01AM +0800, Arnold kang wrote:
when I test linuxptp. I unplug the cable and plug in after a while,
the ptp can't recovery. and precision stay bad. any one know why?
What driver and HW are you using?
Some of the Intel drivers reset the NIC time when the link
Dear Richard,
thanks for your reply.I'm using AR8031, and hardware timestamp mode
. OS version: 3.0
some detail:
{359.993454} [DEBUG] master offset 2461 s2 freq -51098 path delay
32041
{360.380834} [DEBUG] t1 +1439307277796976619
{360.380880} [DEBUG] t2
On Tue, Aug 11, 2015 at 03:35:26PM +0800, Arnold kang wrote:
Dear Richard,
thanks for your reply.I'm using AR8031, and hardware timestamp mode
. OS version: 3.0
That HW is not present in mainline Linux, and so I cannot help you
with it. Probably it is buggy.
Also, from the ptp4l
On Tue, Aug 11, 2015 at 05:52:41PM +0800, Arnold kang wrote:
I know why, when the cable unplugged , the rtc in phy still run as list
freq set. so after some seconds, the phy is slower or faster than master .
when cable plug in, after a very lone time to adjfreq, the ptp will sync.
but how
thanks. i'll try tomorrow!
2015-08-11 19:20 GMT+08:00 Richard Cochran richardcoch...@gmail.com:
On Tue, Aug 11, 2015 at 05:52:41PM +0800, Arnold kang wrote:
I know why, when the cable unplugged , the rtc in phy still run as
list
freq set. so after some seconds, the phy is slower or
On Mon, 2015-08-10 at 23:12 +0200, Richard Cochran wrote:
This patch adds method to initialize a configuration and look up
values.
All port options are also global option, with the global option
giving the
default value. The port look up method first checks for a port
specific
value,
