aboutsummaryrefslogtreecommitdiffstats
path: root/tools/genext2fs/patches/400-byteswap_fix.patch
Commit message (Collapse)AuthorAgeFilesLines
* tools: bring back genext2fs for apm821xxFelix Fietkau2016-07-231-0/+44
| | | | | | | | This reverts commit 8c68c104eaba65273280c7a4727fbb10ab10f5af. It is used for apm821xx, which needs ext2 (not ext4) images for some devices. Signed-off-by: Felix Fietkau <nbd@nbd.name>
* tools: drop unused genext2fsJo-Philipp Wich2015-04-201-44/+0
| | | | | | Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 45518
* tools: genext2fs: add support for blocksize != 1024John Crispin2014-06-021-0/+44
This patch series is extracted from http://ftp.de.debian.org/debian/pool/main/g/genext2fs/genext2fs_1.4.1-4.debian.tar.gz The patches are used in Debian for quite a long time, so I assume that this is solid material. At least, my Ubuntu host fsck.ext4 does not bark :-) The goal is to allow building filesystems with larger blocksizes instead of the current default of 1k. This should improve performance and lifetime when the filesystem is stored e.g. on a SD card (on Raspberry Pi/I2SE Duckbill for example) which uses internal flash memory. Writing to flash memory is slow because writing the data of one block results in erasing a whole erase block of the flash memory. Thus it is preferable to align the filesystem block size on a flash device with the erase blocksize, or at least bring it closer to the later one, to avoid unnecessary write amplification. Signed-off-by: Michael Heimpold <mhei@heimpold.de> SVN-Revision: 40921