netdev - Reading MAC addresses with NVMEM under MTD partition [Was: Re: [PATCH v3 1/3] nvmem: Update the OF binding to use a subnode for the cells list]

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

Date:   Thu, 18 Apr 2019 15:36:46 +0200
From:   Petr Štetiar <ynezz@...e.cz>
To:     devicetree@...r.kernel.org
Cc:     Alban Bedel <albeu@...e.fr>,
        Maxime Ripard <maxime.ripard@...tlin.com>,
        Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
        linux-mtd@...ts.infradead.org, netdev@...r.kernel.org,
        Boris Brezillon <boris.brezillon@...tlin.com>,
        John Crispin <john@...ozen.org>
Subject: Reading MAC addresses with NVMEM under MTD partition [Was: Re:
 [PATCH v3 1/3] nvmem: Update the OF binding to use a subnode for the cells
 list]

Hi,

I'm wondering what is the status of this patch? I'm currently trying to do
following with modified of_get_mac_address[1] which uses nvmem_get_mac_address
under the hood:

flash@0 {
	partitions {
		compatible = "fixed-partitions";

		art: partition@...000 {
			label = "art";
			reg = <0xff0000 0x010000>;
			read-only;

			eth0_addr: ethernet-address@0 {
				reg = <0x0 0x6>;
			};

			eth1_addr: ethernet-address@6 {
				reg = <0x6 0x6>;
			};

			wmac_addr: ethernet-address@...2 {
				reg = <0x1002 0x6>;
			};
	};
};

&eth0 {
        nvmem-cells = <&eth0_addr>;
        nvmem-cell-names = "mac-address";
};

&eth1 {
        nvmem-cells = <&eth1_addr>;
        nvmem-cell-names = "mac-address";
};

&wmac {
        nvmem-cells = <&wmac_addr>;
        nvmem-cell-names = "mac-address";
};

It seems to me, that this use case is not supported yet, but it could be
probably handled with this proposed patch or something similar. What could be
done in order to move forward? Thanks!

1. https://github.com/ynezz/linux/commit/919e9a943af4cdf9b78b0ead17e9855be90d9466

-- ynezz