On Fri, Jun 23, 2017 at 11:57 AM, Miroslav Lichvar wrote:
> That's an interesting idea. Do you think people would prefer SW RX+HW
> TX timestamping over SW RX+SW TX?
"SW" in this context means kernel timestamps, right?
When I sent that email I was thinking it would be nice.
I have a setup that looks like the following:
GPS Receiver -- PTP --> machine_a -- NTP --> machine_b
Where:
These machines are all pretty close together (the switching latency
between them should be something like 10us).
machine_a is running linuxptp and chrony with a shared memory region
via
On Fri, Jun 23, 2017 at 02:38:26PM -0400, Chris Perl wrote:
> On Fri, Jun 23, 2017 at 1:10 PM, Miroslav Lichvar wrote:
> > I think we can support it, at least with a new option that would
> > disable the filter. I actually have a patch in my queue to allow
> > disabling the
On Fri, Jun 23, 2017 at 02:49:39PM -0400, Chris Perl wrote:
> On Fri, Jun 23, 2017 at 2:43 PM, Miroslav Lichvar wrote:
> > It's the patch included in the package from the copr repo. Does it not
> > work for you?
>
> Oh, sorry that wasn't clear to me and I haven't had a
On Fri, Jun 23, 2017 at 2:43 PM, Miroslav Lichvar wrote:
> It's the patch included in the package from the copr repo. Does it not
> work for you?
Oh, sorry that wasn't clear to me and I haven't had a chance to test
with it yet.
Is there something included in the copr repo
On Fri, Jun 23, 2017 at 1:10 PM, Miroslav Lichvar wrote:
> I think we can support it, at least with a new option that would
> disable the filter. I actually have a patch in my queue to allow
> disabling the new NTP-specific filter, which should be added in 4.13
> (although
On Fri, Jun 23, 2017 at 2:49 PM, Chris Perl wrote:
> Is there something included in the copr repo that isn't in the git
> repo? I'm not that familiar with copr, but based on what I have read,
> I wouldn't think so.
>
> If not, I'd prefer to just build from git. Assuming