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] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 16 May 2016 09:30:10 -0700
From:	Moritz Fischer <>
To:	Boris Brezillon <>
Cc:	David Woodhouse <>,
	Brian Norris <>,,
	Linux Kernel Mailing List <>,
Subject: Re: [PATCH] mtd: Adding of_mtd_info_get to get mtd_info from devicetree

Hi Boris,

On Mon, May 16, 2016 at 1:05 AM, Boris Brezillon
<> wrote:

>> Here are a few questions (I'm assuming the netdev + MAC address case):
>> - how would you link the net/PHY device to the MTD partition storing
>>   the MAC address

Well in my case I actually planned to use it with the OTP partition of my QSPI
device using spi_nor_read_usr_prot_reg and friends and I just needed a way
to get to the struct mtd_info from a child of my network device.

Right now the OTP 'partitions' are not really exposed to device tree afaik.
Maybe that would be worthwhile to further look into? Maybe exposing
(wrapping) that as nvmem
would be the way to go?

> Sorry, I sent it before asking all my questions :).
;-) (as you can see from this email, you're not the only one that
fails at email today, forgot to CC list ...)

> - it seems quite specific to MTD devices to me. What if the MAC address
>   is stored in something that is not exposed as an MTD device. I wonder
>   if we shouldn't add an nvmem wrapper around MTD devices.

That looks certainly worthwhile investigating for the general case.



Powered by blists - more mailing lists