lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <20230227154037.7c775d4c@kmaincent-XPS-13-7390> Date: Mon, 27 Feb 2023 15:40:37 +0100 From: Köry Maincent <kory.maincent@...tlin.com> To: linux@...linux.org.uk Cc: andrew@...n.ch, davem@...emloft.net, f.fainelli@...il.com, hkallweit1@...il.com, kuba@...nel.org, netdev@...r.kernel.org, richardcochran@...il.com, Thomas Petazzoni <thomas.petazzoni@...tlin.com>, Maxime Chevallier <maxime.chevallier@...tlin.com> Subject: Re: [PATCH RFC net-next] net: phy: add Marvell PHY PTP support [multicast/DSA issues] Hello RMK, > Hence why I'm at the point of giving up; I don't see that PTP will be > of very limited benefit on my network with all these issues, and in > any case, NTP has been "good enough" for the last 20+ years. Given > that only a limited number of machines will be able to implement PTP > support anyway, NTP will have to run along side it. I see this patch has been abandoned. I am testing it with a ZynqMP board (macb ethernet) and it seems to more or less work. It got tx timestamp timeout at initialization but after some times (~20 seconds) ptp4l manages to set it working. Also the IEEE 802.3 network PTP mode is not working, it constantly throw rx timestamp overrun errors. I will aim at fixing these issues and adding support to interrupts. It would be good to have it accepted mainline. What do you think is missing for that? I see you faced issues with few Armada SOM and IP_MULTICAST, is it still the case? I am new to the PTP and Ethernet APIs I will try to not speak nonsense but please correct me if I do. Köry
Powered by blists - more mailing lists