On Fri, Nov 17, 2023 at 03:29:16PM -0800, Cliff Spradlin via Linuxptp-devel
wrote:
> I'm investigating why a port immediately enters a faulty state on
> startup (and then self-recovers).
>
> It looks like there might be some buggy rtnl logic.
This sounds familiar... wasn't there a bug in this
On Fri, Nov 17, 2023 at 08:27:43PM -0800, Richard Cochran wrote:
> How does this requirement improve synchronization?
>
> What benefit does it bring to users of the PTP?
rhetorical questions :^(
___
Linuxptp-devel mailing list
On Fri, Nov 17, 2023 at 01:51:18PM +0100, Andrew Zaborowski wrote:
> It is exposed on the wire in the Pdelay messages. Compliance tests
> look at this. They also simulate a few hypothetical scenarios like a
> domain 0 PTP port trying to communicate with a CMLDS link port since
> 1588 talks
I'm investigating why a port immediately enters a faulty state on
startup (and then self-recovers).
It looks like there might be some buggy rtnl logic.
In rtnl_link_status(), the following code is used to pass info to callers:
--
int slave_index = -1;
...
if (tb[IFLA_LINKINFO])
On Fri, 17 Nov 2023 at 16:24, Pham, Calvin via Linuxptp-devel <
linuxptp-devel@lists.sourceforge.net> wrote:
> Hi Richard,
>
> I am running Oracle Linux 9.1 in my server which is equipped with
> BCM57416. This Broadcom NIC supports IEEE-1588. But when I check if it
> supports HW Timestamp, it’s
Hi Richard,
I am running Oracle Linux 9.1 in my server which is equipped with BCM57416.
This Broadcom NIC supports IEEE-1588. But when I check if it supports HW
Timestamp, it's not there.
[root@COTS-DL380Gen11-39 ~]# ethtool -T eth0
Time stamping parameters for eth0:
Capabilities:
On Fri, 17 Nov 2023 at 05:50, Richard Cochran wrote:
> On Fri, Nov 17, 2023 at 01:41:19AM +0100, Andrew Zaborowski wrote:
> > Do you want to require the user to enforce that the port numbering is
> > the same between the ptp4l processes?
>
> No.
(I meant: do you want to require that the user
