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: <20180830031110.GC16896@lunn.ch> Date: Thu, 30 Aug 2018 05:11:10 +0200 From: Andrew Lunn <andrew@...n.ch> To: Moritz Fischer <mdf@...nel.org> Cc: davem@...emloft.net, keescook@...omium.org, f.fainelli@...il.com, linux-kernel@...r.kernel.org, netdev@...r.kernel.org, alex.williams@...com Subject: Re: [PATCH net-next 2/3] net: nixge: Add support for having nixge as subdevice On Wed, Aug 29, 2018 at 05:40:45PM -0700, Moritz Fischer wrote: > Add support for instantiating nixge as subdevice using > fixed-link and platform data to configure it. > > Signed-off-by: Moritz Fischer <mdf@...nel.org> > --- > > Hi, > > not this patch is still in the early stages, > and as the rest of this series goes on top of [1]. > > The actual platform data might still change since > the parent device driver is still under development. Hi Moritz Could you tell us more about the parent device. I'm guessing PCIe. Is it x86 so no device tree? Are there cases where it does not have a PHY connected? What is connected instead? SFP? A switch? Can there be multiple PHYs on the MDIO bus? Answering these questions will help decide how best to structure this. Andrew
Powered by blists - more mailing lists