All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darius Augulis <augulis.darius@gmail.com>
To: massimo cirillo <maxcir@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] Fixup for Numonyx M29W128 chips
Date: Thu, 26 Mar 2009 14:54:02 +0200	[thread overview]
Message-ID: <49CB7AEA.2000009@gmail.com> (raw)
In-Reply-To: <62cbdcd90903260402q61725160v7f1538762fbd76bc@mail.gmail.com>

Hi,

I'm getting jffs2 errors after write to flash. I don't have the output 
log now, but the idea is that after write to flash, jffs2 does not find 
magic numbers anymore. File system is broken.
It's completely resolved when write buffers are not used. I could make 
patch which disables write buffer only for M29W128 chips. Anyway it's 
not working, one who needs more performace, is welcome to fix this in 
better way...

Darius.

massimo cirillo wrote:
> Hi Darius,
> what kind of failure did you experiment with M29W?
>
> In my opinion, complete removal of the buffer program feature is not a
> good solution,
> because you are taking away an important feature of the device, that results in
> a very high performance decrease.
>
> Moreover, if you make the fix applicable to all devices with 0x227E device ID,
> you are removing the same feature from other devices too, such as M29EW
> that has a much bigger buffer thus resulting in a dramatic performance decrease
> for this device.
>
>   

  reply	other threads:[~2009-03-26 12:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-26 11:02 [PATCH] Fixup for Numonyx M29W128 chips massimo cirillo
2009-03-26 12:54 ` Darius Augulis [this message]
2009-03-30 12:56   ` massimo cirillo
2009-04-01  7:35     ` Darius Augulis
2009-04-13 18:52       ` Richard Retanubun
2009-04-14 18:02         ` Darius Augulis
  -- strict thread matches above, loose matches on Subject: below --
2009-03-25  9:23 Darius Augulis

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=49CB7AEA.2000009@gmail.com \
    --to=augulis.darius@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=maxcir@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.