On 1/28/07, Wolfgang Denk wd@denx.de wrote:
In message 45BD21D7.20203@comcast.net you wrote:
What my goal in this proposed design is to allow users to choose at compile time what features are desired for the u-boot memory commands a) without an ifdef maze and b) without needing to inject new code into cmd_mem.c and cmd_load.c for every different memory technology that will use memory access type commands. If somebody wants to use the memory commands on a serial EEPROM, this can be made to work if desired, or not
I feel that would be not natural. And EEPROM (like on a I2C bus) does not have any natural adresses in the CPU's address space. Same for IDE or USB devices. These are storage devices on some form of I/O bus, but certainly NOT memory.
This is the exact category that MMC and DataFlash devices are in (both accessed via SPI). Yet they are both accessible by commands in cmd_mem.c.
IMHO we should provide a user inteface which is powerful, yet easy to use - this requires it must be intuitive to the end user. For most f them, (NOR) flash *is* memory, while and IDE or USB disk and even an EEPROM is not.
Right; so what do we do with MMC and DataFlash?
g.