From: Thomas Gleixner <tglx@linutronix.de>
To: jonathan@jonmasters.org
Cc: linux-mtd@lists.infradead.org,
Charles Manning <manningc2@actrix.gen.nz>,
Vitaly Wool <vwool@ru.mvista.com>,
yaffs@stoneboat.aleph1.co.uk
Subject: Re: [Yaffs] bit error rates --> a vendor speaks
Date: Tue, 21 Feb 2006 09:26:13 +0100 [thread overview]
Message-ID: <1140510373.2480.842.camel@localhost.localdomain> (raw)
In-Reply-To: <35fb2e590602201629i1c4eefd8v3dc4e43bfa194f2c@mail.gmail.com>
On Tue, 2006-02-21 at 00:29 +0000, Jon Masters wrote:
> > The worst serial device still guarantees a baudrate > 0 and the
> > effective baudrate has no impact on data storage size.
>
> Just let me make sure I'm getting this right:
>
> 1). You don't have OOB available to you with your NAND part.
> 2). You want YAFFS changed to suit your special case.
No, you get it wrong. Its not my personal problem at all. It's not about
the board on my desk.
It's about some piece of software relying on a non guaranteed hardware
feature.
I'm looking into the variety of hardware which evolves around NAND flash
and I carefully look in which direction this is going.
I see that the near future will require more complexity in the nand code
and I'm looking for a sane solution for that. I'm not saying that its
wrong, when something uses a nice hardware feature, but my point still
stands that it is wrong to rely on a feature which is nowhere
guaranteed.
tglx
next prev parent reply other threads:[~2006-02-21 8:25 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 [this message]
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 ` [Yaffs] bit error rates --> a vendor speaks Artem B. Bityutskiy
2006-02-21 13:50 ` 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=1140510373.2480.842.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=jonathan@jonmasters.org \
--cc=linux-mtd@lists.infradead.org \
--cc=manningc2@actrix.gen.nz \
--cc=vwool@ru.mvista.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