public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Adrian Hunter <ext-adrian.hunter@nokia.com>
To: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: OneNAND: Rate of write errors
Date: Fri, 23 Feb 2007 10:04:17 +0200	[thread overview]
Message-ID: <45DEA001.9060202@nokia.com> (raw)
In-Reply-To: <e167438e0702220835gbc5562fl4dc0bc4bd879f649@mail.gmail.com>

ext Julianne C. wrote:
> This does verify the suspicion that the buffer was corrupted before it
> was committed.  Does anyone have any idea how or why the data in the
> bufferram might be corrupted?

This is outside my experience but as far as I know there is little that
OneNAND can control aside from latency and size of synchronous burst
reads/writes.  The rest is controlled by other hardware
e.g. a memory controller of some sort

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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-22 16:35 OneNAND: Rate of write errors Julianne C.
2007-02-23  8:04 ` Adrian Hunter [this message]
2007-02-26  0:41 ` Kyungmin Park
  -- strict thread matches above, loose matches on Subject: below --
2007-02-22  0:21 Julianne C.
2007-02-22  9:28 ` Adrian Hunter

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=45DEA001.9060202@nokia.com \
    --to=ext-adrian.hunter@nokia.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox