linux-kernel - Re: [PATCH v2 2/2] nvmem: add ONIE NVMEM cells support

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

Message-ID: <9f73d7ea-1f1f-9820-a9d1-55baa984873e@linaro.org>
Date:   Mon, 15 Jun 2020 12:06:11 +0100
From:   Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
To:     Vadym Kochan <vadym.kochan@...ision.eu>
Cc:     linux-kernel@...r.kernel.org,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Taras Chornyi <taras.chornyi@...ision.eu>
Subject: Re: [PATCH v2 2/2] nvmem: add ONIE NVMEM cells support



On 05/06/2020 11:53, Vadym Kochan wrote:
>> One of the example is atmel eeprom (at24), but there might be different
>> devices.
>>
>> But can you please explain what is the technical/conceptual issue with
>> this approach ?
>>
>> Thanks,
> I just I'd like to clarify if there is a way it can be acceptable. The
> problem is that there is TLV format which  might be used on any nvmem
> device which contains for example mac address which needs to be exposed
> as nvmem cell. If to populate cells via nvmem_config then anyway I need
> to parse these cells from the "target" nvmem device.



As a first step this need to be part of the provider logic to parse this 
before nvmem provider is registered. If there are more users for such 
parsing, we can think of adding some level of parsing to nvmem core itself.

Hope this answers your query.

Thanks,
srini