All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thayne Harbaugh <tharbaugh@lnxi.com>
To: "Eric W. Biederman" <ebiederman@lnxi.com>
Cc: David Woodhouse <dwmw2@infradead.org>, linux-mtd@lists.infradead.org
Subject: Re: [RFC] refactoring MTD cmdset ops, jedec_probe, and cfi_probe
Date: Tue, 13 Jul 2004 09:21:48 -0600	[thread overview]
Message-ID: <1089732108.8696.127.camel@tubarao> (raw)
In-Reply-To: <m3acy4j6dn.fsf@maxwell.lnxi.com>

On Tue, 2004-07-13 at 09:04 -0600, Eric W. Biederman wrote:
> Thayne Harbaugh <tharbaugh@lnxi.com> writes:

> > There's a short list of things that have been removed or changed
> > significantly (although this is from memory and may not match the
> > current code):
> > 
> > * read-back check of written data
> 
> I have a patch  for that already.  Since we are not checking any other
> status bits.  At least verifying the data is correct is useful.  

Wonderful.

> > * retry of failed writes
> 
> This one is more interesting.   I don't know if it should be generic or we should
> just override do_write_one_word...
> 
> One way or another we will get this one back in there.

Good.
 
> > * unlock address for some chips (although this is likely part of the big
> > rewrite)
> > 
> > In the end, it's much appreciated that everything was cleaned up - there
> > were some major things done that I wanted to do but was too timid to do
> > major overhauling of the code.  Unfortunately it was just continuing to
> > grow harrier and uglier.
> 
> Thayne this problem I am not familiar with.  Could I have some details?

Errrr . . . the problem of the unlock address or of the harry, ugly
code?

The unlock story is that there was *no* unlock code in cfi_cmdset_0002.
One of the newer SST chips requires unlocking of the blocks.  Unlike
other chips that need unlocking, the addresses for unlocking this
particular chip is not at the block address but below the address of the
entire chip.

It was strange, but I figured that since there wasn't already an unlock
function it wouldn't matter that the new one was chip specific and less
than ideal.  Of course no more than a few weeks after I put it in the
unlock function was needed for *sane* flash chips and so the unlock code
was *corrected*.

The problem with the harry and ugly code was that the status checking
code was reproduced in multiple spots (at least three).  It was bulky
and very sensitive.  All of it needed to be consolidated into a single
location.  That was part of the last, major rewrite that *fixed* some of
the things that should have been left in.

  reply	other threads:[~2004-07-13 15:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-13  3:13 [RFC] refactoring MTD cmdset ops, jedec_probe, and cfi_probe Eric W. Biederman
2004-07-13  6:25 ` David Woodhouse
2004-07-13  7:05   ` Eric W. Biederman
2004-07-13  8:02     ` David Woodhouse
2004-07-13 14:23       ` Eric W. Biederman
2004-07-13 14:45         ` Thayne Harbaugh
2004-07-13 15:04           ` Eric W. Biederman
2004-07-13 15:21             ` Thayne Harbaugh [this message]
2004-07-13 15:40               ` Eric W. Biederman
2004-07-13 16:00               ` Eric W. Biederman
2004-07-14  5:44                 ` Eric W. Biederman
2004-08-12  7:39                   ` Eric W. Biederman
2004-07-13 15:25   ` Eric W. Biederman
2004-07-13 16:17     ` Josh Boyer
2004-08-12  7:13       ` Eric W. Biederman
2004-08-16 14:13         ` Josh Boyer
2004-07-13 16:36 ` Dan Post
2004-07-13 16:52   ` Nicolas Pitre
2004-07-13 17:33     ` Dan Post
2004-07-13 18:17       ` Nicolas Pitre

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=1089732108.8696.127.camel@tubarao \
    --to=tharbaugh@lnxi.com \
    --cc=dwmw2@infradead.org \
    --cc=ebiederman@lnxi.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.