Re: [PATCH] Newly erased page read workaround

[Artem Bityutskiy <Artem.Bityutskiy@nokia.com>]

On Fri, 2011-04-01 at 18:09 +0200, ext Ivan Djelic wrote:
> I had a quick look at fsmc_nand.c, and I don't see anything in the controller
> preventing this approach. The driver provides an IO_ADDR_W address for sending
> data to the NAND device, and lets mtd upper layers do the job. By implementing
> the page writing function in the driver, one could clear the marker in the oob
> array before programming (and check it in the page reading function).

OK, cool!

> I would be very surprised if the controller did not allow control over oob
> contents other than ecc bytes. By doing so, it would prevent things like
> software bad block marking. But sometimes hardware can be very surprising :)

Well, I actually meant that programming OOB could be a separate
operation (not impossible): instead of "write data, oob data and ECC in
one go", something like "write data and oob, wait for completion, write
additional oob byte". So I meant that this could have write speed
impact. But this does not matter, since this is not the case now.

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)