From: Frank Mandarino <fmandarino@endrelia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Write YAFFS filesystem images to NAND (Updated)
Date: Wed, 06 Dec 2006 17:09:24 -0500 [thread overview]
Message-ID: <el7f2l$eo1$1@sea.gmane.org> (raw)
The attached patch updates my previous patch of Sept 9th, 2006 for the
latest versions of U-Boot and YAFFS.
It adds two sub-commands, "write.yaffs" and "write.yaffs1", to the nand
command set, which write YAFFS filesystem images generated by
mkyaffs2image and mkyaffsimage from RAM to NAND flash.
YAFFS images cannot be written using the normal nand write command
because they contain data which must be written to the NAND OOB area.
The "write.yaffs" command writes images generated by mkyaffs2image for
2048+64 NAND chips. I do not have access to this type of chip, so it
has not been tested (any takers?).
The "write.yaffs1" command writes images generated by mkyaffsimage for
512+16 NAND. It writes the older yaffs1 OOB format used by Linux
kernels before 2.6.18, or, by defining a CFG parameter, it writes the
newer OOB format used by Linux 2.6.18 and up.
This patch is much simpler than the previous version because the new
nand_util.c code contains most of the required functionality. It uses
two CFG parameters:
CFG_NAND_WRITE_YAFFS - enables the YAFFS writing code.
CFG_NAND_WRITE_YAFFS1_NEW_OOB_LAYOUT - writes the OOB data in the
format used by Linux 2.6.18 and up.
I find it VERY convenient to write YAFFS filesystems in U-Boot,
especially the Linux root filesystem. Without this patch, I need to
maintain a separate non-YAFFS root filesystem in NAND so that I can boot
Linux in order to update my YAFFS root filesystem. This wastes
valuable NAND space and is more time-consuming.
Signed-off-by: Frank Mandarino <fmandarino@endrelia.com>
Regards,
../fam
--
Frank Mandarino fmandarino(a)endrelia.com
Endrelia Technologies Inc.
Toronto, Ontario, Canada
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nand_write_yaffs-2.patch
Type: text/x-patch
Size: 2908 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20061206/fc773c60/attachment.bin
reply other threads:[~2006-12-06 22:09 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='el7f2l$eo1$1@sea.gmane.org' \
--to=fmandarino@endrelia.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