From: Scott Wood <scottwood@freescale.com>
To: ??? <yuyongbao@126.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: mpc8379e rdb nand flash support
Date: Wed, 30 Apr 2008 13:28:15 -0500 [thread overview]
Message-ID: <20080430182815.GA8639@ld0162-tx32.am.freescale.net> (raw)
In-Reply-To: <2F9EE17A2D4D48458F49220889E0FAAD@baby>
On Thu, Apr 24, 2008 at 09:52:25AM +0800, ??? wrote:
> Since our projects need more capability to store filesystems,I changed nand flash to 1G byte.
> I think it is the same to operate nand flash both in u-boot and linux kernel ,because the code about FCM nand flash control is almost the same.So I just test it in u-boot.
> From the mpc8379e reference manual page 484 :
> 21 PGS NAND Flash E2PROM page size, buffer size, and block size.
> 0 Page size of 512 main area bytes plus 16 spare area bytes (small page devices);
> FCM RAM buffers are 1 Kbyte each; Flash block size of 16 Kbytes.
> 1 Page size of 2048 main area bytes plus 64 spare area bytes (large page devices);
> FCM RAM buffers are 4 Kbytes each; Flash block size of 128 Kbytes.
>
> Because the 32M nand flash block size is just the 16Kbytes,and it
> works well.But the block size of the 1G bytes nand flash is
> 256Kbytes,when every time I tried to write to it ,It just can be writed
> the first 128kbytes of every 256kbytes.As I wrote in last email.
> Below is the linux kernel information when I operate nand flash.
Try changing set_addr() to hardcode the shift applied before writing to
FBAR to the width of FPAR[PI], rather than basing it on the actual erase
block size.
-Scott
next prev parent reply other threads:[~2008-04-30 18:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2018.1208895004.11702.linuxppc-embedded@ozlabs.org>
2008-04-23 7:47 ` mpc8379e rdb nand flash support ???
2008-04-23 16:35 ` Scott Wood
2008-04-24 1:52 ` ???
2008-04-30 18:28 ` Scott Wood [this message]
[not found] <mailman.3.1208829603.21538.linuxppc-embedded@ozlabs.org>
2008-04-22 3:07 ` ???
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=20080430182815.GA8639@ld0162-tx32.am.freescale.net \
--to=scottwood@freescale.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=yuyongbao@126.com \
/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