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
| ||
|
Date: Thu, 26 Jun 2014 08:16:13 +0200 From: Christian Riesch <christian.riesch@...cron.at> To: Richard Cochran <richardcochran@...il.com> Cc: Stefan Sørensen <stefan.sorensen@...ctralink.com>, David Miller <davem@...emloft.net>, "netdev@...r.kernel.org" <netdev@...r.kernel.org> Subject: Re: [PATCH net-next 1/3] ptp: Allow reassigning calibration pin function On Thu, Jun 26, 2014 at 8:14 AM, Christian Riesch <christian.riesch@...cron.at> wrote: > Yes, indeed, but isn't that a bug? I think the calibration should be > done again whenever the clock is loaded with a new value, i.e. in > ptp_dp83640_settime. See section 3.1 in [1]: "All subsequent settings > should use a step > adjustment or temporary rate adjustment, which should occur at each > PHY without introducing any error." This means, whenever we do > something else (directly write to the clock register), we must > recalibrate. Forgot to paste the link: [1] http://www.ti.com/lit/pdf/snla104 Sorry. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists