linux-kernel - Re: [PATCH 0/3] nvmem: eeprom: add support for FRAM

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]

Date:   Mon, 12 Apr 2021 08:06:52 +0200
From:   Jiří Prchal <jiri.prchal@...ignal.cz>
To:     Christian Eggers <ceggers@...i.de>, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org
Cc:     Rob Herring <robh+dt@...nel.org>
Subject: Re: [PATCH 0/3] nvmem: eeprom: add support for FRAM

On 09. 04. 21 19:21, Christian Eggers wrote:
> Hi Jiri,
> 
> I have two Fujitsu different FRAMs running with the stock at25 driver. I set
> the page size equal to the device size (as FRAMs have no pages).
> 
> Are you able to run your FRAM with the unmodified driver?
> 
> I assume that getting the device geometry from the chip is vendor specific (in
> contrast to flash devices which have standard commands for this).  I suppose
> that there is no much value getting vendor specific information from a chip. If
> the drivers knows the vendor, it should also know the chip (e.g. from the dt).

Hi Christian,
main purpose of this patch is to get serial number from this chip. I 
don't have it done yet, in older kernels I expose it as separate file in 
sysfs, but in this kernel no luck. So a post first things while I'm 
working on sernum exposing.

Does your chip has serial number? Can you read it?

Any help welcomed.
Thanks
Jiri

PS: If standard EEPROMs has some commands to get size etc., why it's not 
used? I guess that size is increased as time goes while board is still 
the same, so isn't it annoying changing dt every new lot with bigger 
eeproms.