I see it's not that easy to get a generic & fast abstract support for the 
different command sets.
Check out the ssfdc_xx.x files attached. I'm still waiting for approval 
concerning the NDA, so only some bits on the real driver included.

Stil some more problems:
* 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 ?

* 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 ???


>>As above: read_raw should do just that.
>
>Yes, but SDDR supports read data only

--> read_raw(,....,...,512);

>, read redundancy only,

--> read_dedundancy( ....,....,)

>  and read data+redundancy.
--> read_raw(,....,...,520);

What we def. need is a
int (*write_and_erase_func)(...);

which should be use when present.


-

sda

ssdfc_info.tar.gz

Reply via email to