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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 11 May 2020 15:53:59 +0200
From:   Andrew Lunn <>
To:     Vadym Kochan <>
Cc:     Jiri Pirko <>,,
        "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

> Looks like it might be hard for the board manufacturing? I mean each
> board item need to have updated dtb file with base mac address, instead
> to have common dtb for the board type.
> And it sounds that platform data might be the way in case if the vendor
> will implement platform device driver which will handle reading base mac
> from eeprom (or other storage) depending on the board and put it to the
> platform data which will be provided to prestera driver ?

Hi Vadym

This is not a new problem. Go look at the standard solutions to this.

of_get_mac_address(), eth_platform_get_mac_address(),
nvmem_get_mac_address(), of_get_mac_addr_nvmem(), etc.


Powered by blists - more mailing lists