On Fri, 18 Apr 2008, Alex Dubov wrote:BTW some bare nand flash have support to page copy (there is some issue because of no ecc checking during the copy). So the support of this could be usefull in mtd.
First off, can you please use a mail client which does line breaks at
around 78 chars ?
As you understand, both smartmedia media and hosts follow certain
spec (publicly available here:
http://www.ssfdc.or.jp/spec/index_e.htm, basic registration
required). xd card spec is almost identical, adding some cosmetic
features and restrictions (such as prohibition of single page
programming). This means, that smartmedia access protocol can be
abstracted out in the reader-independent way. You can seen in the
xd_card_blk.c that it can operate both completely dumb controllers,
while taking protocol shortcuts (using host->caps) to accommodate
smarter readers (the only feature currently not there is
adapter-side page copy - it can be easily added under FBD_COPY
clause in xd_card_trans_req). The backend itself (jmb38x_xd.c)
Having a separate driver infrastructure for clever controllers, whichI wonder if mtd shouldn't modified to handler more clever controller :
provide only semi raw access to the FLASH chip is fine simply because
such controllers do not fit into the MTD layer.
Current mtd have other limitations (4GB limit fix, dma buffer, ...),> Correct. Erase() is the only callback-based function and every single
> driver implements it synchronous anyway. Improving this situation is
> needed for mtd's own sake anyway. Either that or replacing mtd with
> something else, likely the block device code.