On Monday 30 March 2009, s-paul...@ti.com wrote: > The SPI on DM355 EVM and DM6467 EVM is conencted only to > AT25 EEPROM. This patch adds support for the EEPROM client driver. > The EEPROM is accessed using the MTD interface
I'm trying to understand why this shouldn't use the existing EEPROM driver... The primary reason to use an MTD interface has been to stick a filesystem on top of it, like JFFS2 or (nowadays) UBI. Sticking MTD on top of an EEPROM seems like a very odd model. Especially when there's only two pages of memory in the EEPROM ... hardly enough to handle filesystem overhead. If it were appropriate to have an MTD interface to an EEPROM, it shouldn't be DaVinci-specific. _______________________________________________ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source