On Wednesday 23 January 2008, Ben Warren wrote:
Hey Mike,
Mike Frysinger wrote:
On Wednesday 23 January 2008, Wolfgang Denk wrote:
In message 200801231729.18316.vapier@gentoo.org you wrote:
with eeprom_info behind CONFIG_SPI. most SPI flashes nowadays support the jedec id command which allows for dynamic detection (which is how the Blackfin SPI driver that i wrote works). hook up any SPI flash and it "just works".
I think you are doing something wrong when you try to use "eeprom" to access "SPI flash" - these are differnt entities...
then what is the "correct" method ? i dont see any other usable option in u-boot for hooking up SPI flashes without writing my own subsystem.
Until recently SPI in U-boot was synonymous with 'SPI-based EEPROM'. In fact, CONFIG_SPI doesn't mean 'configure support for a SPI controller', it means 'configure support for a SPI EEPROM'. This is of course yet another artifact from another day that it would be nice to clean up.
i'm aware of this
I introduced CONFIG_HARD_SPI in the latest release cycle, and included a driver for a Freescale controller. It would be nice to have other drivers added for generic SPI support. My preference would be for you to expand the 'spi' command with something like:
'spi eeprom info'
i dont see how in the long run, this is any different from today. Wolfgang can still argue that the SPI flash is not an eeprom device, so "spi eeprom ..." is not appropriate. which means there is still no subsystem whatsoever for accessing SPI flashes. -mike