On Friday, December 24, 2010 14:06:34 Reinhard Meyer wrote:
Dear Mike Frysinger,
this seems to work much nicer for me. only odd thing is that 'fatls' does not work if i dont 'mmcinfo' first. do you see the same ? maybe this is (currently) expected behavior ?
Currently it is like that with the common MMC framework. Same behavior with gen_atmel_mci.
I'd think its normal that you have to "init" such a block device first, isn't it the same with USB?
Otherwise you'd have to implement automated init on first block read, and detection of removal and insertion of a new device to re-read the info.
my gripe is that it's called "mmcinfo" and not "mmc init". if it were the latter, i wouldnt be surprised at all. but it seems odd that i have to "query the device and print its extended info" rather than "initialize the mmc card". perhaps i'm just whining semantics though.
if this is currently the standard/expected behavior for the generic mmc framework, then that's OK from the mmc_spi perspective. i'll merge this into the Blackfin tree and let our testers validate it with our regression tests. -mike