public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Josh Boyer <jdub@us.ibm.com>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: linux-mtd@lists.infradead.org
Subject: Re: lock bit and erase errors
Date: Mon, 21 Mar 2005 10:52:45 -0600	[thread overview]
Message-ID: <1111423965.7635.4.camel@windu.rchland.ibm.com> (raw)
In-Reply-To: <20050317103418.GA4501@wohnheim.fh-wedel.de>

On Thu, 2005-03-17 at 11:34 +0100, Jörn Engel wrote:
> > 
> > FYI, I just ran this with a 2.6 kernel + fairly recent MTD code and I
> > see the same problems.
> > 
> > No more updates from me until I hear back, I promise :).
> 
> I've had a quick look and would agree with you right now.  This
> appears to be a bug.

Thomas and I thought so too.

> 
> Generally speaking, there appears to be a lack of automated tests for
> the cfi code.  Getting it to work right for all combinations of bus
> widths, etc. is a challenge.  But automated tests would require one
> device of each kind and I have no idea how to get all those.

Me either.  Some kind of test suite would be nice though.  Artem has the
NAND simulator.  Perhaps someone could make a NOR simulator as well to
test the CFI stuff?  Any volunteers?

> 
> Maybe you should just fix your special case and hope not to break
> someone else.

Thomas actually came up with a patch for it and it's in CVS now.  It
fixed my bogus status merging problem so an error is actually returned
when an erase fails.

As for why dd never reported an error, that is because dd is stupid and
doesn't flush any of it's writes.  It just relies on the flush that is
done on the implicit close when exit(0) is called.

josh

  reply	other threads:[~2005-03-21 16:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-14 19:08 lock bit and erase errors Josh Boyer
2005-03-14 19:20 ` Josh Boyer
2005-03-14 19:29   ` Josh Boyer
2005-03-17 10:34     ` Jörn Engel
2005-03-21 16:52       ` Josh Boyer [this message]
2005-03-24  0:55         ` Jared Hulbert
2005-03-24  2:02           ` 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=1111423965.7635.4.camel@windu.rchland.ibm.com \
    --to=jdub@us.ibm.com \
    --cc=joern@wohnheim.fh-wedel.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox