From: Chris Williams <chris@jem.co.jp>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Big Block NAND, JFFS2, and Me
Date: Thu, 12 May 2005 15:11:35 +0900 [thread overview]
Message-ID: <4282F397.8080800@jem.co.jp> (raw)
Howdy.
The board I am porting to uses Samsung's K9F1G08U0M NAND--which it
appears is a "Big Block NAND" chip and non-standard. I've tried doing
some general fiddling with the macros in the NAND, Flash, and JFFS2
segments of the code--which has gotten NAND and the generic Flash
commands working, but the JFFS2 code seems to have problems.
I researched this a bit, and it seems that Samsung has their own
solution, RFS, which they say should used with NAND chips with page
sizes more than 512 bytes (ours is 2048.) We are currently contacting
the board manufacturer to see about receiving the RFS code for U-Boot
and Linux, but if it ends up that we cannot receive this code, then I
would like to ask if anyone knows whether the current U-Boot JFFS2 code
should be able to work with big block NAND (and I just need to fiddle
with it more), or if I will need to essentially create my own JFFS2
handler? I don't currently have an adequate understanding of JFFS2 or
flash memory to determine what possible issues there are between
different chip formats.
Thank you,
Chris Williams
reply other threads:[~2005-05-12 6:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4282F397.8080800@jem.co.jp \
--to=chris@jem.co.jp \
--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