All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <dvrabel@arcom.com>
To: linux-mtd list <linux-mtd@lists.infradead.org>
Subject: CFI command set 0002 (AMD/Fujitsu) work.
Date: Mon, 16 Feb 2004 14:24:43 +0000	[thread overview]
Message-ID: <4030D2AB.7010002@arcom.com> (raw)

Hi,

I'm currently working on cfi_cmdset_0002.c to get erase-suspend-program 
working.  So far I've taken all the chip status checking code and 
refactored it into a single function -- it was all a bit of a mess.

A couple of questions:

1. There's a fair amount of crap related to very broken SST chips (all 
the stuff for retrying commands).  a) This is mess and appears only 
applicable to a very few number of chips; b) I'm not sure it would even 
work if talking to the chip is broken then retrying a few times won't 
guarantee it will work.  I'd suggest removing this stuff from 
cfi_cmdset_0002.c.  Clearly the SST chips aren't compliant even though 
they claim to be.  Thoughts?

2. The "fast programming" feature (unlock bypass) which is currently 
always disabled (due to "code brokeness"). I don't believe this will 
ever work with erase-suspends.  Should the "fast programming" stuff be 
removed?

David Vrabel
-- 
David Vrabel, Design Engineer

Arcom, Clifton Road           Tel: +44 (0)1223 411200 ext. 3233
Cambridge CB1 7EA, UK         Web: http://www.arcom.com/

             reply	other threads:[~2004-02-16 14:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-16 14:24 David Vrabel [this message]
2004-02-16 14:31 ` CFI command set 0002 (AMD/Fujitsu) work David Woodhouse
2004-02-17 15:47 ` David Vrabel
2004-02-17 16:40 ` Thayne Harbaugh

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=4030D2AB.7010002@arcom.com \
    --to=dvrabel@arcom.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 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.