public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Chuck Meade" <chuckmeade@mindspring.com>
To: <linux-mtd@lists.infradead.org>
Subject: _DoC_WaitReady timed out -- is this the correct way to handle it?
Date: Wed, 2 Apr 2003 15:51:06 -0500	[thread overview]
Message-ID: <IIEEICKJLNEPBBDJICNGMEHADCAA.chuckmeade@mindspring.com> (raw)

During bootup I get the following messages relating to my
DiskOnChip device:

Using configured DiskOnChip probe address 0xf1000000
DiskOnChip Millennium found at address 0xF1000000
Flash chip found: Manufacturer ID: 98, Chip ID: E6 (Toshiba TC58V64AFT/DC)
_DoC_WaitReady timed out.
_DoC_WaitReady timed out.
_DoC_WaitReady timed out.
DoC_Command (reset) for 1,0 returned true
_DoC_WaitReady timed out.
_DoC_WaitReady timed out.
_DoC_WaitReady timed out.
DoC_Command (reset) for 2,0 returned true
_DoC_WaitReady timed out.
_DoC_WaitReady timed out.
_DoC_WaitReady timed out.
DoC_Command (reset) for 3,0 returned true
1 flash chips found. Total DiskOnChip size: 8 MiB
mtd: Giving out device 0 to DiskOnChip Millennium
NFTL driver: nftlcore.c $Revision: 1.85 $, nftlmount.c $Revision: 1.25 $
NFTL_notify_add for DiskOnChip Millennium
.......

The problem is that the timeouts associated with the
"_DoC_WaitReady timed out." messages are greatly increasing the
bootup time (about 2 additional minutes).  It is running DoC_ScanChips(),
which is calling DoC_IdentChip(), which is timing out on a reset command,
very slowly.

One entry in the archives mentioned checking fewer floors, so I 
reduced the number of floors being checked from 4 to 1.  It now runs
fast enough, but I would like to know if this is the correct way to
go about handling this "long timeout" issue, or if there is a cleaner
approach.

Thanks very much,
Chuck

                 reply	other threads:[~2003-04-02 20:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=IIEEICKJLNEPBBDJICNGMEHADCAA.chuckmeade@mindspring.com \
    --to=chuckmeade@mindspring.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