linux-kernel - Re: [PATCH] Revert "mtd: spinand: esmt: fix id code for F50D1G41LB"

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:
 <BL4PR19MB8902CF825EF35C4F145300BF9DA2A@BL4PR19MB8902.namprd19.prod.outlook.com>
Date: Mon, 8 Dec 2025 13:26:21 +0400
From: George Moussalem <george.moussalem@...look.com>
To: Miquel Raynal <miquel.raynal@...tlin.com>,
 Ziyang Huang <hzyitc@...look.com>, quic_mdalam@...cinc.com
Cc: richard@....at, vigneshr@...com, tudor.ambarus@...aro.org,
 mmkurbanov@...utedevices.com, linux-mtd@...ts.infradead.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Revert "mtd: spinand: esmt: fix id code for F50D1G41LB"



On 12/8/25 12:33, Miquel Raynal wrote:
> On 02/12/2025 at 23:05:56 +08, Ziyang Huang <hzyitc@...look.com> wrote:
> 
>> This reverts commit dd26402642a0899fde59ea6b0852fad3d799b4cc.
>>
>> The issue George met is due to the limit of QPIC, not the issue of the
>> flash chip.
>>
>> QPIC only supports 4 bytes ID. So the fifth byte is always 0.
>>
>> If we use spi-gpio, the fifth byte can be read correctly.
>>
>> Signed-off-by: Ziyang Huang <hzyitc@...look.com>
>> ---
> 
> So how do we solve that?
> 
> Is there anything than can be done on the qpic side?

Hi Alam,

Is the hardware itself limited to reading 4 ID bytes only or is it a
driver limitation?

> 
> Thanks,
> Miquèl

Best regards,
George