[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170919164615.mfv77pxuuyqc4zq4@localhost>
Date: Tue, 19 Sep 2017 18:46:15 +0200
From: Richard Cochran <richardcochran@...il.com>
To: Miroslav Lichvar <mlichvar@...hat.com>
Cc: Richard Cochran <rcochran@...utronix.de>, netdev@...r.kernel.org,
Andre Guedes <andre.guedes@...el.com>,
Henrik Austad <henrik@...tad.us>, linux-kernel@...r.kernel.org,
Jesus Sanchez-Palencia <jesus.sanchez-palencia@...el.com>,
intel-wired-lan@...ts.osuosl.org,
John Stultz <john.stultz@...aro.org>,
Thomas Gleixner <tglx@...utronix.de>,
Anna-Maria Gleixner <anna-maria@...utronix.de>,
David Miller <davem@...emloft.net>
Subject: Re: [PATCH RFC V1 net-next 0/6] Time based packet transmission
On Tue, Sep 19, 2017 at 04:43:02PM +0200, Miroslav Lichvar wrote:
> If I understand it correctly, this also allows us to make a PTP/NTP
> "one-step" clock with HW that doesn't support it directly.
Cool, yeah, I hadn't thought of that, but it would work...
Thanks,
Richard
Powered by blists - more mailing lists