netdev - Re: [PATCH] dp83640: Support a configurable number of periodic outputs

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]

Date:	Wed, 5 Feb 2014 07:40:17 +0000
From:	Sørensen, Stefan 
	<Stefan.Sorensen@...ctralink.com>
To:	"richardcochran@...il.com" <richardcochran@...il.com>
CC:	"ben@...adent.org.uk" <ben@...adent.org.uk>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [PATCH] dp83640: Support a configurable number of periodic
 outputs

On Tue, 2014-02-04 at 16:43 +0100, Richard Cochran wrote:
> On Tue, Feb 04, 2014 at 03:24:27PM +0000, Sørensen, Stefan wrote:
> > 
> > I would definitely prefer the DT approach. On all the platforms I have
> > used, the GPIO configuration has been set in stone by the HW. But there
> > might be some dev boards or the like that has them configurable.
> 
> I think DT is fine for the initial configuration, but the ethtool way
> will still be needed in at least two cases.
> 
> 1. Platform has no DT at all.
> 2. User wants to change the function at run time.

Will all PTP clocks be associated with an ethernet device? If not,
wouldn't a PTP ioctl be better than ethtool? 

Stefan