diff options
| author | Remy Bohmer <linux@bohmer.net> | 2008-08-20 20:46:56 +0200 |
|---|---|---|
| committer | Scott Wood <scottwood@freescale.com> | 2008-08-21 14:05:33 -0500 |
| commit | 0bb86d823b6c150c7ee17de0cfca9ffccc16463b (patch) | |
| tree | 761a81896f2ce58031d4e8ea3be221dec2a79402 /doc/README.AMCC-eval-boards-cleanup | |
| parent | bfd7f38614e21f745b6d6845fcc616ebc5e4d36f (diff) | |
| download | u-boot-imx-0bb86d823b6c150c7ee17de0cfca9ffccc16463b.zip u-boot-imx-0bb86d823b6c150c7ee17de0cfca9ffccc16463b.tar.gz u-boot-imx-0bb86d823b6c150c7ee17de0cfca9ffccc16463b.tar.bz2 | |
Make the YAFFS filesystem work
Recently the YAFFS filesystem support has been added to U-boot.
However, just enabling CONFIG_YAFFS2 is not enough to get it working.
ymount will generate an exception (when dereferencing mtd->readoob()), because
the genericDevice is a null pointer. Further, a lot of logging is produced
while using YAFFS fs, so logging should also be disabled.
Both issues are solved by this patch.
With this patch and CONFIG_YAFFS2 enabled, I get a readable filesystem
in U-boot, as well as in Linux.
Tested on a Atmel AT91SAM9261EK board.
Signed-off-by: Remy Bohmer <linux@bohmer.net>
Acked-by: William Juul <william.juul@tandberg.com>
Signed-off-by: Scott Wood <scottwood@freescale.com>
Diffstat (limited to 'doc/README.AMCC-eval-boards-cleanup')
0 files changed, 0 insertions, 0 deletions