From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Josh Boyer <jdub@us.ibm.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: lock bit and erase errors
Date: Thu, 17 Mar 2005 11:34:18 +0100 [thread overview]
Message-ID: <20050317103418.GA4501@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <1110828565.7642.33.camel@windu.rchland.ibm.com>
On Mon, 14 March 2005 13:29:24 -0600, Josh Boyer wrote:
> On Mon, 2005-03-14 at 13:20 -0600, Josh Boyer wrote:
> > On Mon, 2005-03-14 at 13:08 -0600, Josh Boyer wrote:
> > > Caveat: I am using some pretty old code in this case, but the current
> > > code is also questionable so bear with me.
>
> 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.
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.
Maybe you should just fix your special case and hope not to break
someone else.
Jörn
--
A surrounded army must be given a way out.
-- Sun Tzu
next prev parent reply other threads:[~2005-03-17 10:34 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 [this message]
2005-03-21 16:52 ` Josh Boyer
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=20050317103418.GA4501@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=jdub@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox