All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: kmpark@infradead.org
Cc: linux-mtd@lists.infradead.org,
	'Adrian Hunter' <ext-adrian.hunter@nokia.com>
Subject: RE: [PATCH] [MTD] OneNAND: Do not allow oob write past end of page
Date: Mon, 05 Feb 2007 10:30:39 +0200	[thread overview]
Message-ID: <1170664239.3628.64.camel@sauron> (raw)
In-Reply-To: <003d01c748f9$705677c0$c7a3580a@swcenter.sec.samsung.co.kr>

On Mon, 2007-02-05 at 16:44 +0900, Kyungmin Park wrote:
> I mean that in the view point of software OnenNAND is NAND, but the one of
> hardware it is NOR.
> So we don't need to work it as NAND. I think we don't need to restrict the
> OneNAND

OneNAND stuff which we have now is _part of MTD_. MTD has its interface,
its model of the device. As long as we are part of this infrastructure,
we have to obey MTD's interface, rules and restrictions.

The whole idea of MTD is to make upper layers to access flashes in a
uniform layer. MTD achieves this at certain extent. There are flaws, but
anyway. So basically OneNAND implements more then NAND in this OOB
handling stuff. And it is bad. It encourages other people to write
OneNAND-only software, incompatible with NAND, which is totally
unreasonable in this case.

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

  reply	other threads:[~2007-02-05  8:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-02  7:54 [PATCH] [MTD] OneNAND: Do not allow oob write past end of page Adrian Hunter
2007-02-05  6:38 ` Kyungmin Park
2007-02-05  7:22   ` Adrian Hunter
2007-02-05  7:44     ` Kyungmin Park
2007-02-05  8:30       ` Artem Bityutskiy [this message]
2007-02-06  2:15         ` Kyungmin Park
2007-02-08 14:11           ` Adrian Hunter
2007-02-09  0:20             ` Kyungmin Park

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=1170664239.3628.64.camel@sauron \
    --to=dedekind@infradead.org \
    --cc=ext-adrian.hunter@nokia.com \
    --cc=kmpark@infradead.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.