From: Savin Zlobec <savin@epico.si>
To: tglx@linutronix.de
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] AT91RM9200 NAND support
Date: Tue, 20 Jun 2006 15:17:04 +0200 [thread overview]
Message-ID: <4497F550.6090302@epico.si> (raw)
In-Reply-To: <1150807931.6780.160.camel@localhost.localdomain>
Thomas Gleixner wrote:
>On Tue, 2006-06-20 at 14:44 +0200, Thomas Gleixner wrote:
>
>
> Oops, looked at the wrong place. The culprit is elsewhere.
>
>Please replace the debug patch by the one below.
>
>
[...]
Here is what I get.
savin
Chip not ready in nand_command():
Last caller: c012bd44 (nand_base.c:1638)
Last command: 0x10
Current caller: c012c12c (nand_base.c:1728)
Current command: 0x60
Chip not ready in nand_command():
Last caller: c012bffc (nand_base.c:1393)
Last command: 0x10
Current caller: c012bfd0 (nand_base.c:1382)
Current command: 0x80
Chip not ready in nand_command():
Last caller: c012bd44 (nand_base.c:1638)
Last command: 0x10
Current caller: c012b688 (nand_base.c:996)
Current command: 0x00
961 static int nand_do_read_ops(struct mtd_info *mtd, loff_t from,
996 chip->cmdfunc(mtd, NAND_CMD_READ0, 0x00, page);
1375 static int nand_write_page(struct mtd_info *mtd, struct
nand_chip *chip,
1382 chip->ecc.write_page(mtd, chip, buf);
1393 status = chip->waitfunc(mtd, chip, FL_WRITING);
1582 static int nand_do_write_oob(struct mtd_info *mtd, loff_t to,
1638 status = chip->waitfunc(mtd, chip, FL_WRITING);
1723 static void single_erase_cmd(struct mtd_info *mtd, int page)
1728 chip->cmdfunc(mtd, NAND_CMD_ERASE2, -1, -1);
next prev parent reply other threads:[~2006-06-20 13:08 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 6:54 [PATCH] AT91RM9200 NAND support Andrew Victor
2006-06-20 7:08 ` Thomas Gleixner
2006-06-20 7:17 ` Andrew Victor
2006-06-20 7:43 ` Savin Zlobec
2006-06-20 8:00 ` Thomas Gleixner
2006-06-20 8:08 ` Thomas Gleixner
2006-06-20 9:07 ` Savin Zlobec
2006-06-20 9:18 ` Thomas Gleixner
2006-06-20 10:49 ` Savin Zlobec
2006-06-20 11:12 ` Thomas Gleixner
2006-06-20 11:42 ` Savin Zlobec
2006-06-20 11:55 ` Thomas Gleixner
2006-06-20 12:28 ` Savin Zlobec
2006-06-20 12:44 ` Thomas Gleixner
2006-06-20 12:52 ` Thomas Gleixner
2006-06-20 13:17 ` Savin Zlobec [this message]
2006-06-20 13:01 ` Savin Zlobec
2006-06-20 13:21 ` Thomas Gleixner
2006-06-20 13:48 ` Savin Zlobec
2006-06-20 13:57 ` Thomas Gleixner
2006-06-20 14:24 ` Savin Zlobec
2006-06-20 14:24 ` Thomas Gleixner
2006-06-20 14:29 ` Thomas Gleixner
2006-06-20 15:53 ` Savin Zlobec
2006-06-20 15:53 ` Thomas Gleixner
2006-06-20 16:03 ` Savin Zlobec
2006-06-20 9:07 ` David Woodhouse
2006-06-20 9:14 ` 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=4497F550.6090302@epico.si \
--to=savin@epico.si \
--cc=linux-mtd@lists.infradead.org \
--cc=tglx@linutronix.de \
/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