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  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:   Mon, 11 May 2020 14:42:45 +0200
From:   Andrew Lunn <>
To:     Jiri Pirko <>
Cc:     Vadym Kochan <>,,
        "David S. Miller" <>,
        Oleksandr Mazur <>,
        Serhiy Boiko <>,
        Serhiy Pshyk <>,
        Volodymyr Mytnyk <>,
        Taras Chornyi <>,
        Andrii Savka <>,
        Jiri Pirko <>,
        Ido Schimmel <>,
        Chris Packham <>
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.


Powered by blists - more mailing lists