From: "Artem B. Bityutskiy" <dedekind@yandex.ru>
To: Charles Manning <manningc2@actrix.gen.nz>, tglx@linutronix.de
Cc: William Watson <wjw1961@gmail.com>,
Vitaly Wool <vwool@ru.mvista.com>,
linux-mtd@lists.infradead.org, yaffs@stoneboat.aleph1.co.uk
Subject: Re: [Yaffs] bit error rates --> a vendor speaks
Date: Tue, 21 Feb 2006 15:14:28 +0300 [thread overview]
Message-ID: <43FB0424.1020309@yandex.ru> (raw)
In-Reply-To: <200602211140.30069.manningc2@actrix.gen.nz>
Charles Manning wrote:
> Sorry Thomas I don't buy that argument. If a system has a NAND device that
> does have spare OOB available then it does have spare OOB and I can rely on
> that. If a NAND chip is soldered to a board, and the system exposes the OOB
> it is there. YAFFS (or whatever) can then be used on this device.
I understand Thomas's point as as he is fighting for generalization.
Indeed, this OOB stuff introduces a lot of mess.
Charles' point is - if OOB is there, why not to let users use it? Also
sounds reasonable.
What I think would be nice to do is to get rid of OOB in MTD stuff, but
add a possibility to access OOB via some NAND-specific interfaces from
nand_base. Indeed, if one wants to work with a generalized flash device
- please use MTD interface. If one still wants to access OOB, use
lower-layer NAND interfaces. That's all about to have more then one
layer of Generalization. And I believe this is the right way to go.
--
Best Regards,
Artem B. Bityutskiy,
St.-Petersburg, Russia.
next prev parent reply other threads:[~2006-02-21 12:15 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <43EB96DC.3030900@eptar.com>
[not found] ` <35fb2e590602100558s2d868fa3o1752fbf3217439e4@mail.gmail.com>
[not found] ` <d97046180602151153g23064424x9e1ddf83a1d7ae4f@mail.gmail.com>
2006-02-16 1:32 ` [Yaffs] bit error rates --> a vendor speaks Charles Manning
2006-02-18 9:10 ` Thomas Gleixner
2006-02-18 16:31 ` Vitaly Wool
2006-02-19 8:22 ` Thomas Gleixner
2006-02-20 20:42 ` Charles Manning
2006-02-20 21:37 ` Thomas Gleixner
2006-02-20 22:40 ` Charles Manning
2006-02-20 23:18 ` Thomas Gleixner
2006-02-21 0:29 ` Jon Masters
2006-02-21 8:26 ` Thomas Gleixner
2006-02-21 9:35 ` Jörn Engel
2006-02-21 1:08 ` [Yaffs] bit error rates --> YAFFS for devices with no OOB Charles Manning
2006-02-21 2:12 ` Jon Masters
2006-02-22 0:38 ` Jamie Lokier
2006-02-21 12:14 ` Artem B. Bityutskiy [this message]
2006-02-21 13:50 ` [Yaffs] bit error rates --> a vendor speaks Josh Boyer
2006-02-21 14:36 ` Artem B. Bityutskiy
2006-02-21 14:49 ` Artem B. Bityutskiy
2006-02-21 11:59 ` Artem B. Bityutskiy
2006-02-21 12:06 ` Thomas Gleixner
2006-02-25 11:58 ` Artem B. Bityutskiy
2006-02-27 13:27 ` Josh Boyer
2006-02-27 16:01 ` Artem B. Bityutskiy
2006-02-27 16:15 ` Josh Boyer
2006-02-27 17:21 ` Artem B. Bityutskiy
2006-02-27 17:40 ` Josh Boyer
2006-02-18 18:11 ` Russ Dill
2006-02-19 0:29 ` Charles Manning
2006-02-19 5:08 ` Jon Masters
2006-02-19 8:29 ` Thomas Gleixner
2006-02-23 0:46 ` Russ Dill
2006-02-23 7:36 ` Thomas Gleixner
2006-02-23 8:31 ` Vitaly Wool
2006-02-24 9:51 ` Artem B. Bityutskiy
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=43FB0424.1020309@yandex.ru \
--to=dedekind@yandex.ru \
--cc=linux-mtd@lists.infradead.org \
--cc=manningc2@actrix.gen.nz \
--cc=tglx@linutronix.de \
--cc=vwool@ru.mvista.com \
--cc=wjw1961@gmail.com \
--cc=yaffs@stoneboat.aleph1.co.uk \
/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