From: Artem Bityutskiy <dedekind1@gmail.com>
To: Adish Kuvelker <adkuvi@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: scantest : READOOB Issue
Date: Sat, 07 Nov 2009 11:15:35 +0200 [thread overview]
Message-ID: <1257585335.21596.124.camel@localhost> (raw)
In-Reply-To: <52760a310911060523x6853acb2rbb92818324e920d8@mail.gmail.com>
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 (Артём Битюцкий)
prev parent reply other threads:[~2009-11-07 9:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 13:23 scantest : READOOB Issue Adish Kuvelker
2009-11-07 9:15 ` Artem Bityutskiy [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1257585335.21596.124.camel@localhost \
--to=dedekind1@gmail.com \
--cc=adkuvi@gmail.com \
--cc=linux-mtd@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox