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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <90A7E81AE28BAE4CBDDB3B35F187D2644073E9C4@CHN-SV-EXMX02.mchp-main.com>
Date:   Wed, 15 Aug 2018 18:03:51 +0000
From:   <Bryan.Whitehead@...rochip.com>
To:     <arnd@...db.de>,
        <UNGLinuxDriver@...rochipTechnology.Mail.Onmicrosoft.com>
CC:     <davem@...emloft.net>, <yuehaibing@...wei.com>,
        <netdev@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] net: lan743x_ptp: convert to ktime_get_clocktai_ts64

> 
> Question: this is the only ptp driver that sets the hardware time to the
> current system time in TAI. Why does it do that?

This is done when the driver starts up after reset. Otherwise the clock is off by 48 years. 
It seemed to me that the system time was the most appropriate clock to sync to. 
If my reasoning is incorrect, please enlighten me.

Thanks,
Bryan

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ