From: Charles Manning <manningc2@actrix.gen.nz>
To: u-boot@lists.denx.de
Subject: [U-Boot] yaffs2 u-boot patching support
Date: Mon, 16 Apr 2012 16:32:07 +1200 [thread overview]
Message-ID: <201204161632.07808.manningc2@actrix.gen.nz> (raw)
Hello ubooters and yaffsers
I was commissioned to refresh yaffs2 in u-boot and add a mechanism to support
dynamic yaffs partition set up (way simpler than screwing around with mtd
part) and manual configuration.
Rather than do this as a once off, I set this scripting up so that this can
be done at any time (painlessly I hope) to bring in the fresh code (as per
Linux patching).
Basically...
Get latest from yaffs git.
cd yaffs2-dir/direct/u-boot
./patch-u-boot.sh uboot-dir
Edit your u-boot config file and add
#define CONFIG_YAFFS2 1
Rebuild u-boot (mrproper probably a Good Idea). Job done.
OK, so how does the new dynamic partition stuff work?
There are 2 new commands: ydevconfig configures a mount point "partition" and
ydevls lists the mount points and their state
So for example let us say we want a mount point called foo on NAND device 0
starting at block 55 and ending at block 999.
ydevconfig foo 0 55 999
Now you want to mount it.
ymount foo
Access files and do stuff...
yls foo
yls -l foo # more info
ymkdir foo/dir
...
You can have multiple mountpoints in use at the same time though they are not
allowed to overlap.
inband tags is selected automatically if there is insufficient space in
oobavail to store the tags.
Have fun.
Charles
next reply other threads:[~2012-04-16 4:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 4:32 Charles Manning [this message]
2012-04-19 21:40 ` [U-Boot] yaffs2 u-boot patching support Tom Rini
2012-04-22 20:23 ` [U-Boot] [Yaffs] " Charles Manning
2012-04-23 15:18 ` Tom Rini
2012-04-23 15:33 ` Stefano Babic
2012-04-25 20:43 ` Charles Manning
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=201204161632.07808.manningc2@actrix.gen.nz \
--to=manningc2@actrix.gen.nz \
--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