Hello,
Yes, EEPROMs are small and are managed as a virtual fixed-size file.
The EEPROM bytes can be erased and written individually, which means the
erase block size of the associated mtd device would be one byte long,
which is uselessly complex. Using larger block sizes would make the
driver
On 11/4/2023 6:12 PM, Robert Middleton wrote:
I'm a little confused as to what the difference is between the MTD folder
and the EEPROM folder. It seems that both folders have support for the
at24xx and at25xx series of chips, so it's not obvious which one is
better.
MTD is more of a "heavyweigh
Thanks for the info. So does it make more sense to add the new
functionality as part of the EEPROM
driver(drivers/eeprom/spi_xx25xx.c) or under the MTD(drivers/mtd/??).
I assume anything added should be under the EEPROM folder, but I'm a
little confused as to what the difference is between the MTD
On 11/3/2023 4:02 PM, Robert Middleton wrote:
Hi,
I am working on a project that will need to be able to read/write the
ID page of an EEPROM(currently a M95M02 SPI device from ST). From the
code that I have seen, it seems that this chip is already supported,
but there is no code to read/write
Hi,
I am working on a project that will need to be able to read/write the
ID page of an EEPROM(currently a M95M02 SPI device from ST). From the
code that I have seen, it seems that this chip is already supported,
but there is no code to read/write the device ID page. I'm looking to
add support,
