All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Korpilla <okorpil@fh-landshut.de>
To: Shawn Jin <xiaogeng_jin@agilent.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Newbie help! - Old AMD (cfi_cmdset_0002) interleaved flash problems
Date: Mon, 26 Apr 2004 21:57:38 +0200	[thread overview]
Message-ID: <408D69B2.8050906@fh-landshut.de> (raw)
In-Reply-To: <408D4A58.7000402@agilent.com>

Shawn Jin wrote:

> A general remark is that the current CVS code of cmdset_0002 may not 
> work on all interleaved chips. If I were you, I would try some older 
> version, e.g. the code coming with DENX distribution (v 1.62).
>
> -Shawn.
>
Thank you, Shawn.

If you mean v 1.62 if cfi_cmdset_0002.c, this is what actually comes
with Linux 2.4.25, and I tried that. On top of the timeouts I get a
kernel panic as well on a timeout with that version.

Did you mean that, or am I getting my versions wrong?

http://lists.infradead.org/pipermail/linux-mtd/2004-April/009660.html
http://lists.infradead.org/pipermail/linux-mtd/2004-April/009666.html

Both these references above are why I cannot actually go with that
release (I currently have tested 1.62, 1.93 and 1.98(current)).

Is this simply a too low timeout problem (which I guess it isn't -
timeout seems now to be longer, and it still doesn't help), or is it a
problem of the write failing (so a timeout will show in any case)? I'm
beginning to guess the 2nd one.

With kind regards,
Oliver Korpilla

  reply	other threads:[~2004-04-26 19:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3236F92B82933347807DFF6A8BA63280D74675@wcosmb04.cos.agilent.com>
2004-04-26 17:43 ` Newbie help! - Old AMD (cfi_cmdset_0002) interleaved flash problems Shawn Jin
2004-04-26 19:57   ` Oliver Korpilla [this message]
2004-04-26 11:03 Oliver Korpilla

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=408D69B2.8050906@fh-landshut.de \
    --to=okorpil@fh-landshut.de \
    --cc=linux-mtd@lists.infradead.org \
    --cc=xiaogeng_jin@agilent.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.