public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Jon Masters" <jonmasters@gmail.com>
To: tglx@linutronix.de
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 00:29:55 +0000	[thread overview]
Message-ID: <35fb2e590602201629i1c4eefd8v3dc4e43bfa194f2c@mail.gmail.com> (raw)
In-Reply-To: <1140477524.2480.827.camel@localhost.localdomain>

On 2/20/06, Thomas Gleixner <tglx@linutronix.de> wrote:

> On Tue, 2006-02-21 at 11:40 +1300, Charles Manning wrote:
> > Just going for the lowest common denominator all the time is like saying "run
> > all serial links at 9600 and never use 115200 because 115200 might not be
> > supported on all possible serial links", or "you can't run an ftdi USB serial
> > port at 230k because most PC serial ports only go up to 115200".
>
> Again, the comparison is still flawed.
>
> 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.

It's all very well arguing that relying on OOB in all cases is a bad
idea - and indeed, it sounds like a good idea to support packing extra
data into pages on flash - but you seem very keen on pushing the idea
that it's always bad to use OOB. So long as logic is added such that
you can have different behaviour, I fail to see the problem here.

Cheers,

Jon.

  reply	other threads:[~2006-02-21  0:30 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 [this message]
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                   ` [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=35fb2e590602201629i1c4eefd8v3dc4e43bfa194f2c@mail.gmail.com \
    --to=jonmasters@gmail.com \
    --cc=jonathan@jonmasters.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=manningc2@actrix.gen.nz \
    --cc=tglx@linutronix.de \
    --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