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

Thayne Harbaugh <tharbaugh@lnxi.com> writes:

> On Tue, 2004-07-13 at 08:23 -0600, Eric W. Biederman wrote:
> > David Woodhouse <dwmw2@infradead.org> writes:
> > 
> > > On Tue, 2004-07-13 at 01:05 -0600, Eric W. Biederman wrote:
> > > > That part does not look to bad...
> > > 
> > > Would be interesting to know if it works though ... :)
> > > 
> > > > Although there has been some error handling from cfi_cmdset_0002.c which
> > > > disturbs me.  Seeing as I'm good at finding flaky NOR flash parts...
> > > 
> > > I assume you mean some error handling _removed_ from cfi_cmdset_0002.c 
> > > 
> > > I don't recall doing that myself... can you elaborate?
> > 
> > Right.  Basically when Thayne was working on cfi_cmdset_0002 we got it stable
> > for the chips we care about.  But the code was so ugly someone rewrote the
> > code.  There were other priorities at the time so we have not been able to
> > get back and fix things up.
> > 
> > The primary thing was that the check that the written data is was what
> > we actually tried to write was removed.
> 
> 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.  
 
> * 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.
 
> * 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?

Eric

  reply	other threads:[~2004-07-13 15:04 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 [this message]
2004-07-13 15:21             ` Thayne Harbaugh
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=m3acy4j6dn.fsf@maxwell.lnxi.com \
    --to=ebiederman@lnxi.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=tharbaugh@lnxi.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.