Hey Mike, Mike Frysinger wrote: > On Wednesday 23 January 2008, Wolfgang Denk wrote: > >> In message <[EMAIL PROTECTED]> 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. > -mike > 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 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' regards, Ben ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
