public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: massimo cirillo <maxcir@gmail.com>
Cc: augulis.darius@gmail.com, linux-mtd@lists.infradead.org,
	RichardRetanubun@ruggedcom.com
Subject: Re: [PATCH] [MTD] CHIPS: 0xFF intolerance for M29W128G
Date: Wed, 26 Aug 2009 18:55:03 +0100	[thread overview]
Message-ID: <20090826175503.GC25726@shareable.org> (raw)
In-Reply-To: <62cbdcd90908260842l66275d12na133bdb7cc4ac14@mail.gmail.com>

massimo cirillo wrote:
> From: Massimo Cirillo <maxcir@gmail.com>
> 
> The M29W128G Numonyx flash devices are intolerant to any 0xFF command:
> in the Cfi_util.c the function cfi_qry_mode_off() (that resets the device
> after the autoselect mode) must have a 0xF0 command after the 0xFF command.
> Intel-like devices are not influenced by a 0xF0 command.
> This fix solves also the cause of the fixup_M29W128G_write_buffer() fix,
> that can be commented out now.
> The following patch applies to 2.6.30 kernel.

This change was discussed 1 year ago:

   http://lists.infradead.org/pipermail/linux-mtd/2008-August/022497.html

The conclusion was that 0xf0 after 0xff might not be safe for some
chips ("early revisions of L30"), but nobody could confirm which
chips, so Alexey Korolov suggested staying safe and using fixup
functions.

I'm inclined to think a per-manufacturer (ignoring chip-id) reset
function would be better than the attempt to poke several different
commands at a chip all mixed together in a careful order, knowing that
some commands break some chips but later commands fix them again.

-- Jamie

  reply	other threads:[~2009-08-26 17:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-26 15:42 [PATCH] [MTD] CHIPS: 0xFF intolerance for M29W128G massimo cirillo
2009-08-26 17:55 ` Jamie Lokier [this message]
2009-08-27 15:59   ` massimo cirillo
  -- strict thread matches above, loose matches on Subject: below --
2009-08-31  6:47 Alexey Korolev
2009-09-03 14:34 ` [PATCH] " massimo cirillo

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=20090826175503.GC25726@shareable.org \
    --to=jamie@shareable.org \
    --cc=RichardRetanubun@ruggedcom.com \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox