netdev - Re: Linux mvneta driver unable to read MAC address from HW

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] [day] [month] [year] [list]

Message-Id: <5B9D8BBF-BED3-4762-96A1-5B14DC75CE20@easyb.ch>
Date:   Tue, 13 Oct 2020 10:20:26 +0200
From:   Ezra Buehler <ezra@...yb.ch>
To:     Thomas Petazzoni <thomas.petazzoni@...tlin.com>
Cc:     netdev@...r.kernel.org, Stefan Roese <sr@...x.de>,
        linux-arm-kernel@...ts.infradead.org, u-boot@...ts.denx.de
Subject: Re: Linux mvneta driver unable to read MAC address from HW

Hi Thomas,

On 13 Oct 2020, at 08:35, Thomas Petazzoni <thomas.petazzoni@...tlin.com> wrote:
> I suspect you have the mvneta driver as a module ? If this is the case,
> then indeed, the MAC address is lost because Linux turns of all unused
> clocks at the end of the boot. When the driver is built-in, there is a
> driver adding a reference to the clock before all unused clocks are
> disabled. When the driver is compiled as a module, this does not
> happen. So indeed, the correct solution here is to have U-Boot pass the
> MAC address in the Device Tree.

Yes, you are right, the driver is compiled as module. This explains
everything, thank you very much for the clarification.

Have a nice day!

Cheers,
Ezra.