ignore messages which contain a timestamp invalid for
the current architecture.
If you think this fix is useful, feel free to apply it to ptp4l.
>From 2f4ddb130d43c2377d0391d2b03907b795bc57cd Mon Sep 17 00:00:00 2001
From: Oliver Westermann
Date: Fri, 11 Aug 2017 10:38:20 +0100
Subject: [PATCH]
I've a setup of multiple devices with a ARM CPU using a Marvell PHY with
hardware timestamping capabilitys for networking.
These Marvell PHYs analyse incoming and outgoing packages for PTP packages,
saves a hardware timestamp and issues a interrupt.
The PHY driver catches the interrupt, gets the
2018-02-13 19:36 GMT+01:00 Richard Cochran :
> On Tue, Feb 13, 2018 at 07:01:22PM +0100, Oliver Westermann wrote:
> > The issue is that the PHY only has two slots for timestamps, one for
> > outgoing packages and one for incoming packages. If the device in
> question
> >
2018-02-16 17:51 GMT+01:00 Keller, Jacob E :
>
> Even the interrupt itself takes up to 12 ms sometimes?
>
I got curious after your last messages and again dove deeper into the
kernel and drivers and tried to find out what happens when.
Just FYI: I inherited the code, so feel free to criticize and
