scantest : READOOB Issue

scantest : READOOB Issue

[Adish Kuvelker]

Hello,

I have developed a NAND driver for an ARM9-based processor with
Samsung K9F2G08U0M NAND Flash. Since the Flash chip doesn't support
the  NAND_CMD_READOOB command I had skipped the development for this.
We are now subjecting this driver to MTD tests. But while doing the
MTD scantest I found that the test requires reading the OOB section
through the NAND_CMD_READOOB command.

Do I have to develop the support for this command in my code in order
to have a MTD compliant driver? Will the absence of support for this
result in the driver being non-compliant?

Regards;
Aadish

Re: scantest : READOOB Issue

[Artem Bityutskiy]

On Fri, 2009-11-06 at 18:53 +0530, Adish Kuvelker wrote:
> Hello,
> 
> I have developed a NAND driver for an ARM9-based processor with
> Samsung K9F2G08U0M NAND Flash. Since the Flash chip doesn't support
> the  NAND_CMD_READOOB command I had skipped the development for this.

But it looks like the random read command can be used instead, right?

> We are now subjecting this driver to MTD tests. But while doing the
> MTD scantest I found that the test requires reading the OOB section
> through the NAND_CMD_READOOB command.
> 
> Do I have to develop the support for this command in my code in order
> to have a MTD compliant driver? Will the absence of support for this
> result in the driver being non-compliant?

Those tests are not really compliance tests. If you do not want to
provide OOB read support, you should probably invent a nice way to
inform upper layers about unsupported OOB read operation. Then you
should amend the tests. And if you do not support reading OOB, it does
not make sense supporting writing OOB either, right?

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