On Sat, Oct 12, 2019 at 09:06:53PM -0700, Richard Cochran wrote:
> A PHC device representing the host clock will appear in the guest.
> Then, for example:
>
> To configure Chronyd to use PHC refclock, add the
> following line to its configuration file:
>
> refclock PHC /dev/ptpX
On Tue, Oct 01, 2019 at 05:48:41AM +0200, Hans-Heinrich Hansen wrote:
> are there any ideas how LinuxPTP could be used in virtual machines?
>
> It would be sufficient to be able to use the exact time generated by PTP,
> e.g. with LinuxPTP running on the host system.
On the VM host, simply run
On Thu, Sep 26, 2019 at 03:54:32PM +0200, Miroslav Lichvar wrote:
> @@ -250,6 +252,45 @@ out:
> return err;
> }
>
> +static void free_master_table(struct unicast_master_table *table)
> +{
> + struct unicast_master_address *address;
> +
> + while ((address = STAILQ_FIRST(>addrs)))
On Thu, Sep 26, 2019 at 03:54:30PM +0200, Miroslav Lichvar wrote:
> Signed-off-by: Miroslav Lichvar
Applied, but I also fixed two other goto labels further down.
Thanks,
Richard
___
Linuxptp-devel mailing list
Linuxptp-devel@lists.sourceforge.net
On Thu, Sep 26, 2019 at 03:54:31PM +0200, Miroslav Lichvar wrote:
> In port_synchronize(), when the clock returned SERVO_UNLOCKED and
> port_dispatch() triggered a switch of the PHC, the variable "s" would
> point to a servo which was already freed and the following call of
>
On Thu, Sep 26, 2019 at 10:47:21AM -0700, Jacob Keller wrote:
> @@ -320,12 +320,16 @@ static int do_caps(clockid_t clkid, int cmdc, char
> *cmdv[])
> " %d programable alarms\n"
> " %d external time stamp channels\n"
> " %d programmable periodic
On Thu, Sep 12, 2019 at 11:06:28AM +, Petr Machata wrote:
> In commit 424bbde8fcca ("Custom management TLV PORT_PROPERTIES_NP"), a new
> TLV was added that allows introspection into PTP ports, and in particular
> translation from PTP port identifiers to system netdevice names. The TLV
> was
On Tue, Oct 01, 2019 at 10:00:42AM +0200, Miroslav Lichvar wrote:
> On Mon, Sep 30, 2019 at 07:17:23PM -0700, Richard Cochran wrote:
> > The delay between the Tx time stamp on the GM and the Rx time stamp
> > must not exceed a small fraction of the sync. period, otherwise the
> > servo on the
On Fri, Oct 11, 2019 at 07:23:38AM +, Y.b. Lu wrote:
> I'm just not familiar how applications use 802.1AS synchronized time.
I don't know of any open source applications using 802.1AS either!
> For physical clock adjustment, I know we have /dev/ptpx device to access for
> time.
> For free
