On 11.10.2021 09:06, Sven Eckelmann wrote:
On Sunday, 10 October 2021 14:53:13 CEST Sven Eckelmann wrote:
[...]
Since there are most likely more devices out there which use mtdparts, I would
guess that there might already be a strategy out there which can be used to
define the nvmem-provider for
On Tuesday, 12 October 2021 20:24:46 CEST Pratyush Yadav wrote:
[...]
> I have been wanting to fix this problem for a while but just never got
> around to it. I was thinking about either extending the mtdparts syntax
> to maybe add nvmem cell information in there or adding a separate
> cmdline a
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Hi Sven,
On 11/10/21 09:06AM, Sve
On Sunday, 10 October 2021 14:53:13 CEST Sven Eckelmann wrote:
[...]
> Since there are most likely more devices out there which use mtdparts, I
> would
> guess that there might already be a strategy out there which can be used to
> define the nvmem-provider for mtdparts defined partitions. At le
Hi,
OpenWrt switched [1] their MAC address (from flash) retrieval code from their
mtd-mac-address based solution [2] to nvmem-cells. The mtd-mac-address based
solution had the benefit that it could find the correct partition by using
get_mtd_device_nm - which was label based. So a lookup for a
