From: Detlev Zundel <dzu@denx.de>
To: linux-mtd@lists.infradead.org
Subject: Re: [RFC] Handling of errors for AMD NOR (cfi_cmdset_0002) chips
Date: Wed, 23 Mar 2011 17:16:09 +0100 [thread overview]
Message-ID: <m2zkolx16e.fsf@ohwell.denx.de> (raw)
In-Reply-To: 4D7F1CF3.5010301@tqsc.de
Hi Markus,
> what type of chips are causing your problems?
Two 16-bit Spansion S29GL512P interleaved into 32-bit bus width.
> AFAIK in cfi_cmdset_0002 the use of max timouts from cfi query struct
> is missing (support in the per chip struct is prepared). This should
> be done first (I think).
I don't think we have this problem. As can be seen by the link provided
in my other mail, we are suffering from recovery problems after a reset,
everything else looks normal.
> Regarding the handling of status bits you can use MERGESTATUS /
> cfi_merge_status (from linux/mtd/cfi.h)
>
> Would it be useful to send rough patches for 2.6.34 for the max timout?
It is always uselful to post patches that solve problems for some of us,
so yes please! ;)
Best wishes
Detlev Zundel
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu@denx.de
next prev parent reply other threads:[~2011-03-23 16:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 1:42 [RFC] Handling of errors for AMD NOR (cfi_cmdset_0002) chips Ilya Yanok
2011-03-11 8:25 ` Norbert van Bolhuis
2011-03-23 15:47 ` Detlev Zundel
2011-03-23 17:33 ` Artem Bityutskiy
2011-03-24 7:35 ` Norbert van Bolhuis
2011-03-24 9:27 ` Detlev Zundel
2011-03-24 10:48 ` Norbert van Bolhuis
2011-03-15 8:01 ` Markus Niebel
2011-03-23 16:16 ` Detlev Zundel [this message]
2011-03-23 18:27 ` Ilya Yanok
2011-03-24 7:45 ` Alexander Stein
2011-03-24 7:55 ` Artem Bityutskiy
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=m2zkolx16e.fsf@ohwell.denx.de \
--to=dzu@denx.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