From: David Woodhouse <dwmw2@infradead.org>
To: "Steve Tsai" <startec@ms11.hinet.net>
Cc: "Linux MTD mailing list" <linux-mtd@lists.infradead.org>
Subject: Re: nand_write_ecc
Date: Tue, 30 Jul 2002 23:40:05 +0100 [thread overview]
Message-ID: <14950.1028068805@redhat.com> (raw)
In-Reply-To: <002801c233ad$a2d39810$5501a8c0@synso.com.tw>
startec@ms11.hinet.net said:
> I am using NAND flash as a root file system. When I and flash a new
> root image to NAND flash and reboot the system. I copy a file to flash
> and the system halt. I got the following message when I operate the
> board. When nand_write_ecc was called, I will print out message as,
> "nand_write_ecc: col=%d last=%d page=%x ecc_code=%x %x %x %x %x %x". I
> think the first nand_write_ecc was called by GC and when I copy the
> file nand_write_ecc was called again. But as the following message,
> the two calls write to the same page 0x18FF. Why they write the same
> page?
Does this still happen with the latest code in CVS?
--
dwmw2
prev parent reply other threads:[~2002-07-30 22:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-25 7:33 nand_write_ecc Steve Tsai
2002-07-30 22:40 ` David Woodhouse [this message]
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=14950.1028068805@redhat.com \
--to=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=startec@ms11.hinet.net \
/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