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: Mon, 11 May 2020 14:42:45 +0200 From: Andrew Lunn <andrew@...n.ch> To: Jiri Pirko <jiri@...nulli.us> Cc: Vadym Kochan <vadym.kochan@...ision.eu>, netdev@...r.kernel.org, "David S. Miller" <davem@...emloft.net>, Oleksandr Mazur <oleksandr.mazur@...ision.eu>, Serhiy Boiko <serhiy.boiko@...ision.eu>, Serhiy Pshyk <serhiy.pshyk@...ision.eu>, Volodymyr Mytnyk <volodymyr.mytnyk@...ision.eu>, Taras Chornyi <taras.chornyi@...ision.eu>, Andrii Savka <andrii.savka@...ision.eu>, Jiri Pirko <jiri@...lanox.com>, Ido Schimmel <idosch@...lanox.com>, Chris Packham <Chris.Packham@...iedtelesis.co.nz> Subject: Re: [RFC next-next v2 1/5] net: marvell: prestera: Add driver for Prestera family ASIC devices > >I understand this is not good, but currently this is simple solution to > >handle base MAC configuration for different boards which has this PP, > >otherwise it needs to by supported by platform drivers. Is there some > >generic way to handle this ? > > If the HW is not capable holding the mac, I think that you can have it > in platform data. The usual way for such HW is to generate random mac. > module parameter is definitelly a no-go. And i already suggested it should be a device tree property. Andrew
Powered by blists - more mailing lists