Sancho Dauskardt wrote: > > * when should the mapping table be rebuilt ? > START_STOP time & ALLOW_MEDIUM_REMOVAL time aren't quite suitable... > Or ist there just an easy mount option which forces READ_CAPACITY to > always be called ? Dunno... This is probably related to the "mount/umount/mount" problem in my driver. Something else to investigate. > > * Creating the mapping table currently takes 17 sek. for a 64 MB card > (4096 blocks) with the carry reader (two bulk urb's per block). Why on > earth is this so slow ? scheduling problem or is the device just so slow ? > 17/(4096*2) == 20,7mSek ?= 2*10mSek schedules ??? That's pretty slow... The SDDR reads the whole thing in one shot (32MB card under one second). Couldn't your driver do the same, doing a read_redundancy for more than one block? >> Yes, but SDDR supports read data only > > > --> read_raw(,....,...,512); > >> and read data+redundancy. > > --> read_raw(,....,...,520); What do you do when you want to read 2 sectors of data only? It looks like you'd call read_raw(.....,1024) which would read one sector, 8 bytes of redundancy, and then a partial sector? > > What we def. need is a > int (*write_and_erase_func)(...); > > which should be use when present. For sure! --Rob _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: http://lists.sourceforge.net/lists/listinfo/linux-usb-devel
