From: Frank Mandarino <fmandarino@endrelia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Write YAFFS filesystem images to NAND
Date: Thu, 07 Sep 2006 16:07:04 -0400 [thread overview]
Message-ID: <edpu5e$esh$1@sea.gmane.org> (raw)
In-Reply-To: <1157656342.30394.137.camel@blairs-desktop>
Hi Blair,
Thanks for the response, but I'm not sure what you are getting at.
I am aware of the yaffs1 compatibility mode, and I think I am running
the yaffs2 code in that mode. At least I only installed the yaffs2 code
into my Linux kernel.
But this has nothing to do with U-Boot's ability to write a yaffs
filesystem image to NAND flash.
In yaffs1 compatibility mode, I believe the yaffs2 code assumes that the
OOB is formatted as it is in a yaffs1 filesystem, so I am providing a
way to write the older yaffs1 OOB format, or the newer yaffs2 OOB format.
Regards,
../fam
Blair Barnett wrote:
> Hi Frank,
>
> You can run yaffs2 in yaffs1 compatibility mode.
> Check the yaffs2 source for the correct configuration options.
>
> -blair
>
> On Thu, 2006-09-07 at 11:46, Frank Mandarino wrote:
>> Hi,
>>
>> The attached patch for common/cmd_nand.c provides the ability to write
>> YAFFS filesystem images to NAND flash memory, using the newer MTD-based
>> nand code.
>>
>> The patch extends the nand write command to parse a ".yaffs1" suffix for
>> yaffs1 filesystems, or a ".yaffs" or ".yaffs2" suffix for yaffs2
>> filesystems.
>>
>> Yaffs1 filesystems support 512-byte page, 16-byte oob NAND chips, while
>> yaffs2 filesystems support 2048-byte page, 64-byte oob NAND chips.
>>
>> Yaffs1 filesystem images can be generated using the mkyaffsimage utility
>> in the yaffs2/utils directory.
>>
>> Yaffs2 filesystem images can be generated using the mkyaffs2image
>> utility in the yaffs2/utils directory, after applying Sergey Kubushyn's
>> patch. See
>> http://aleph1.co.uk/lurker/message/20060211.004601.77b55bf3.en.html.
>>
>> So, for example, to write a yaffs1 filesystem image of length 0x526320
>> from address 0x20000000 in ram to offset 0x100000 in flash, run the command:
>>
>> nand write.yaffs1 20000000 100000 526320
>>
>> The area to be written must be erased before writing the filesystem.
>>
>> I have tested this code with yaffs1 filesystems, and, in fact, I am
>> finally able to run Linux with rootfstype=yaffs. I am unable to test
>> with yaffs2 filesystems because I don't have access to a system using
>> 2048+64 NAND chips.
>>
>> Regards,
>> ../fam
>
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
--
Frank Mandarino fmandarino(a)endrelia.com
Endrelia Technologies Inc.
Toronto, Ontario, Canada
prev parent reply other threads:[~2006-09-07 20:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-07 18:46 [U-Boot-Users] [PATCH] Write YAFFS filesystem images to NAND Frank Mandarino
2006-09-07 19:12 ` Blair Barnett
2006-09-07 20:07 ` Frank Mandarino [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='edpu5e$esh$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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.