Hi,
drasko.drasko...@gmail.com wants to follow you.
** Is drasko.drasko...@gmail.com you friend? **
If Yes please follow the link below:
http://invites.flipmailer.com/signup_e.html?fullname=&email=linuxptp-devel@lists.sourceforge.net&invitername=Drasko.draskovic&inviterid=17473118&userid=
Yo Miroslav!
On Fri, 6 Mar 2015 12:45:50 +0100
Miroslav Lichvar wrote:
> On Wed, Mar 04, 2015 at 12:16:48PM -0800, Gary E. Miller wrote:
> > Which still leaves me with slave PHC clocks that either go crazy or
> > have huge offsets...
>
> Another thought, is it possible that the PTP master is us
On Fri, Mar 06, 2015 at 04:05:08PM +0100, Richard Cochran wrote:
> There are really two issues:
>
> 1. The filter algorithm itself.
> 2. How the new filter fits into the SW design.
>
> Although I am not convinced about #1
Not convinced that the raw offset should be sent to the servo when the
num
On Fri, Mar 06, 2015 at 12:49:51PM +0100, Miroslav Lichvar wrote:
>
> Any comments on this or other suggestions?
I want to put this on hold until I have a chance to really test your
scheme.
There are really two issues:
1. The filter algorithm itself.
2. How the new filter fits into the SW desig
On Mon, Feb 23, 2015 at 11:36:34AM +0100, Miroslav Lichvar wrote:
> On Sun, Feb 22, 2015 at 07:16:12PM +0100, Richard Cochran wrote:
> > - expand the servo/filter APIs to include all of the parameters you
> > will need.
>
> Like this?
>
> servo_sample(offset, local, weight, raw_offset, raw_dela
On Wed, Mar 04, 2015 at 12:16:48PM -0800, Gary E. Miller wrote:
> Which still leaves me with slave PHC clocks that either go crazy or have
> huge offsets...
Another thought, is it possible that the PTP master is using HW
timestamping with a PTP clock that is not synchronized to anything? If
it was
