From: "Jörn Engel" <joern@logfs.org>
To: Adrian McMenamin <lkmladrian@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
dwmw2@infradead.org, linux-sh <linux-sh@vger.kernel.org>
Subject: Re: MTD types
Date: Mon, 3 Mar 2008 15:01:56 +0100 [thread overview]
Message-ID: <20080303140155.GA17732@lazybastard.org> (raw)
In-Reply-To: <8b67d60803021219k23ca6c6bt2ce2fb2c61cda42e@mail.gmail.com>
On Sun, 2 March 2008 20:19:09 +0000, Adrian McMenamin wrote:
>
> I am loathe to just post a patch adding it back, so does it make any
> difference if I use another type (I really have no idea of what the
> physical type used in the Dreamcast is, though possibly someone here
> might?)
There is also a bit of confusion about what any specific time should
_mean_. Once upon a time NAND flash had ECC, could be written only once
(i.e. not write single bits by cleverly masking and rewriting), had a
well-known amount of OOB for general use, etc. while NOR could be
written bit-by-bit, rewritten, did not have ECC, had a higher quality
and all that.
These days you can buy NOR flashes that have all attributes of NAND
except OOB, NAND flashes may use all OOB area for error correction, etc.
etc. In short, there is just about nothing left you can use the type
for. And when it is used in JFFS2, you will find lots of code like "if
it is this type, but not that exception, then...".
Jörn
--
"Translations are and will always be problematic. They inflict violence
upon two languages." (translation from German)
prev parent reply other threads:[~2008-03-03 14:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-02 20:19 Adrian McMenamin
2008-03-03 14:01 ` Jörn Engel [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=20080303140155.GA17732@lazybastard.org \
--to=joern@logfs.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=lkmladrian@gmail.com \
/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
all inboxes | Powered by JetHome®