On Fri, 18 Apr 2008, Alex Dubov wrote:

quoted text
> mtd_blkdevs breaks the block layer request into separate pages,
> effectively disabling lower layer from making decision based on a
> real data block size, and using dma to any useful extent. What is
> the proposed way to deal with this?

Wrong in two aspects. 

1) it does not break the request into separate pages. It breaks it
into mtd_blktrans_ops->blksize chunks, which is set by the blkdev
user.

2) Using DMA on raw NAND Flash is on per page basis except you have an
"intellegent" controller chip which does the low level handling of the
nand flash itself. Such controllers do not necessarily fit into MTD.

quoted text
> (By the way, first question already puts us into a "quirk" area of
> the statement "smartmedia are flash chips with quirks". Both
> memorystick and smartmedia are always operated in tandem with their
> controllers, as you could notice.)

I have no idea what you want to tell me. there is no quirk in a
smartmedia card.

Thanks,
	tglx


--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/