From: Mike Rapoport <mike.rapoport@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Testing rewrite of NAND code?
Date: Mon, 26 Sep 2005 16:52:13 +0200 [thread overview]
Message-ID: <f870da1805092607525c7159a8@mail.gmail.com> (raw)
In-Reply-To: <20050922094019.C15B8353A0B@atlas.denx.de>
I've made several tests of the new NAND code on a custum board based on mpc8272.
Read worked for me just fine for both "raw data" read and JFFS2
functions (ls and fsload).
When I tried to write data to the NAND flash using the command
=> nand write.jffs2 400000 200000 400000
the system hanged right after printing:
"NAND write: device 0 offset 2097152, size 4194304 ... 4194304 bytes
written: OK"
As far as I understood, the "erase" is still not implemented.
--
Sincerely yours,
Mike Rapoport.
next prev parent reply other threads:[~2005-09-26 14:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 9:40 [U-Boot-Users] Testing rewrite of NAND code? Wolfgang Denk
2005-09-26 9:45 ` [U-Boot-Users] " Hoda
2005-09-26 11:01 ` Hoda
2005-09-26 14:52 ` Mike Rapoport [this message]
2005-09-26 15:39 ` [U-Boot-Users] " Ladislav Michl
2005-10-02 12:44 ` Mike Rapoport
2005-09-28 8:21 ` [U-Boot-Users] " Hoda
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=f870da1805092607525c7159a8@mail.gmail.com \
--to=mike.rapoport@gmail.com \
--cc=u-boot@lists.denx.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