public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
* DoC-2000: NAND_CMD_READID hangs on stock 2.6.10 kernel
@ 2005-02-18 20:20 John Kelly
  2005-02-18 20:32 ` Thomas Gleixner
  0 siblings, 1 reply; 2+ messages in thread
From: John Kelly @ 2005-02-18 20:20 UTC (permalink / raw)
  To: linux-mtd

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?

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: DoC-2000: NAND_CMD_READID hangs on stock 2.6.10 kernel
  2005-02-18 20:20 DoC-2000: NAND_CMD_READID hangs on stock 2.6.10 kernel John Kelly
@ 2005-02-18 20:32 ` Thomas Gleixner
  0 siblings, 0 replies; 2+ messages in thread
From: Thomas Gleixner @ 2005-02-18 20:32 UTC (permalink / raw)
  To: John Kelly; +Cc: linux-mtd

On Fri, 2005-02-18 at 13:20 -0700, John Kelly wrote:
> 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.

It's not READID, there is something wrong with the number of chips to
scan for. I have encountered the problem here too. I will post again
when I have fixed it.

tglx

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2005-02-18 20:32 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-02-18 20:20 DoC-2000: NAND_CMD_READID hangs on stock 2.6.10 kernel John Kelly
2005-02-18 20:32 ` Thomas Gleixner

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox