From: John Kelly <johnfkelly@earthlink.net>
To: linux-mtd@lists.infradead.org
Subject: DoC-2000: NAND_CMD_READID hangs on stock 2.6.10 kernel
Date: Fri, 18 Feb 2005 13:20:40 -0700 (GMT-07:00) [thread overview]
Message-ID: <18307332.1108758040913.JavaMail.root@bigbird.psp.pas.earthlink.net> (raw)
I'm working on getting a Technologics TS-5400 board runnig Linux-2.6 to see a 32MB DoC.
When inserting the diskonchip.ko driver from a vanilla 2.6.10 kernel, I get into an infinite loop in nand_command with command=0x90 (READID). The loop is at the bottom of the function:
/* Apply this short delay always to ensure that we do wait tWB in
* any case on any machine. */
ndelay (100);
/* wait until command is processed */
while (!this->dev_ready(mtd));
If I use a counter to break out of the loop after 40 tries, everything works--only READID seems to need this.
Is there some other way this should be handled?
next reply other threads:[~2005-02-18 20:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-18 20:20 John Kelly [this message]
2005-02-18 20:32 ` DoC-2000: NAND_CMD_READID hangs on stock 2.6.10 kernel Thomas Gleixner
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=18307332.1108758040913.JavaMail.root@bigbird.psp.pas.earthlink.net \
--to=johnfkelly@earthlink.net \
--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