diff options
author | wdenk <wdenk> | 2003-03-14 20:47:52 +0000 |
---|---|---|
committer | wdenk <wdenk> | 2003-03-14 20:47:52 +0000 |
commit | 06d01dbe000057e5df4af0f113242f0eba716340 (patch) | |
tree | 9188617ad1907e44f41910b99af9bde7258338f9 /doc/README.JFFS2 | |
parent | 09127c60964c47621937ada7b0ccbf0c26329376 (diff) | |
download | u-boot-imx-06d01dbe000057e5df4af0f113242f0eba716340.zip u-boot-imx-06d01dbe000057e5df4af0f113242f0eba716340.tar.gz u-boot-imx-06d01dbe000057e5df4af0f113242f0eba716340.tar.bz2 |
* Avoid flicker on the TRAB's VFD by synchronizing the enable with
the HSYNC/VSYNC. Requires new CPLD code (Version 101 for Rev. 100
boards, version 153 for Rev. 200 boards).
* Patch by Vladimir Gurevich, 12 Mar 2003:
Fix relocation problem of statically initialized string pointers
in common/cmd_pci.c
* Patch by Kai-Uwe Blöm, 12 Mar 2003:
Cleanup & bug fixes for JFFS2 code:
- the memory mangement was broken. It caused havoc on malloc by
writing beyond the block boundaries.
- the length calculation for files was wrong, sometimes resulting
in short file reads.
- data copying now optionally takes fragment version numbers into
account, to avoid copying from older data.
See doc/README.JFFS2 for details.
Diffstat (limited to 'doc/README.JFFS2')
-rw-r--r-- | doc/README.JFFS2 | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/README.JFFS2 b/doc/README.JFFS2 index 0d39c46..3243895 100644 --- a/doc/README.JFFS2 +++ b/doc/README.JFFS2 @@ -9,6 +9,14 @@ fsload - load binary file from a file system image fsinfo - print information about file systems ls - list files in a directory +If you boot from a partition which is mounted writable, and you +update your boot environment by replacing single files on that +partition, you should also define CFG_JFFS2_SORT_FRAGMENTS. Scanning +the JFFS2 filesystem takes *much* longer with this feature, though. +Sorting is done while inserting into the fragment list, which is +more or less a bubble sort. That algorithm is known to be O(n^2), +thus you should really consider if you can avoid it! + There is two ways for JFFS2 to find the disk. The default way uses the flash_info structure to find the start of a JFFS2 disk (called |