Mathias Kresin ddd259b0d5 image: pass device blocksize to padjffs2 ... At the moment the padding steps are hardcoded. Especially images for devices with a 4K sector size can be unnecessarily bloated using the hardcoded padding steps. It has been observed that 192Kb of padding was added to the image of a 4MB device, albeit due to the 4K sector size the minimum required extra padding for the jffs2 rootfs_data is 20Kb. In worst case it means that the image-size check could fail albeit there is enough space for all selected packages For device build code not exposing the blocksize, use the hardcoded padding further on. Signed-off-by: Mathias Kresin <dev@kresin.me>		2016-09-03 07:40:15 +02:00
..
site
autotools.mk
cmake.mk
debug.mk
depends.mk
device_table.txt
download.mk
feeds.mk
hardening.mk
host-build.mk
host.mk
image-commands.mk	image: pass device blocksize to padjffs2	2016-09-03 07:40:15 +02:00
image-legacy.mk
image.mk
kernel-build.mk
kernel-defaults.mk
kernel-version.mk
kernel.mk
netfilter.mk
nls.mk
package-bin.mk
package-defaults.mk
package-dumpinfo.mk
package-ipkg.mk
package-seccomp.mk
package.mk
prereq-build.mk
prereq.mk
quilt.mk
rootfs.mk
scan.awk
scan.mk
scons.mk
shell.sh
subdir.mk
target.mk
toolchain-build.mk
toplevel.mk
uclibc++.mk
unpack.mk
verbose.mk
version.mk