linux-kernel - Re: [PATCH] mtd: micron-st: enable lock/unlock for mt25qu512a

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: <59d54d8a-7c23-c6d3-5608-b06b1ce31bda@linaro.org>
Date:   Thu, 13 Jul 2023 06:58:58 +0300
From:   Tudor Ambarus <tudor.ambarus@...aro.org>
To:     Michael Walle <michael@...le.cc>,
        Mamta Shukla <mamta.shukla@...ca-geosystems.com>
Cc:     pratyush@...nel.org, miquel.raynal@...tlin.com, richard@....at,
        vigneshr@...com, linux-mtd@...ts.infradead.org,
        linux-kernel@...r.kernel.org,
        bsp-development.geo@...ca-geosystems.com
Subject: Re: [PATCH] mtd: micron-st: enable lock/unlock for mt25qu512a



On 06.07.2023 10:26, Michael Walle wrote:
> Am 2023-07-05 15:22, schrieb Michael Walle:
> 
>> FWIW, I noticed the difference between MT25QU and MT25QL here. But
>> I don't think we can do anything about it. It is just another example,
>> that the name is mostly irrelavant/cannot be trusted. Vendors tend to
>> reuse the id for different (software compatible probably) parts. Maybe
>> we can get rid of it entirely. Tudor, Pratyush?
> 
> I must have been blind, the ID is different (ba vs bb), but my point
> is still valid.
> 

the name is good for debug purposes to differentiate between flashes
that use the same ID. But otherwise I too don't see a great benefit of
showing/printing the flash name.