staging/kaloz/config/Config-images.in, branch master

config: support new symbol intro'd in kernel 4.12

2018-01-13T15:27:45Z

Symbol CONFIG_INITRAMFS_FORCE allows to ignore the value passed by the bootloader. By default, all symbols containing INITRAMFS are wiped from the final config and then re-added conditionally. Add support for this symbol, as the build will stop otherwise questioning the user about this option: * Restart config... * * * General setup * Cross-compiler tool prefix (CROSS_COMPILE) [] Compile also drivers which will not load (COMPILE_TEST) [N/y/?] n ... Initial RAM filesystem and RAM disk (initramfs/initrd) support (BLK_DEV_INITRD) [Y/n/?] y Initramfs source file(s) (INITRAMFS_SOURCE) [] Ignore the initramfs passed by the bootloader (INITRAMFS_FORCE) [N/y/?] (NEW) Signed-off-by: Koen Vandeputte

mpc85xx: Enable initramfs for p1020 subtarget

2017-10-13T23:19:35Z

The following patch enables building of initramfs images by default for the P1020 subtarget in mpc85xx. Signed-off-by: Chris Blake

build: enable gzipping of images on x86 even if ext4 is disabled

2017-07-06T09:30:33Z

There is lots of padding between the boot partition and the rootfs, so gzipping is helpful here Signed-off-by: Felix Fietkau

build: allow specifying flow-control to grub on serial console

2017-04-03T06:51:02Z

On the more sophisticated (i.e. deeper FIFO) serial controllers, flow-control might be needed to avoid dropping output. Signed-off-by: Philip Prindeville

x86: Set default baud rate on Geode images to 115200

2017-02-17T09:30:38Z

Prior to commit 1496b95a0 ("x86: clean up default grub baudrate settings") we had three different baud rates for the Geode targets: 19200 for net5501, 38400 for alix2, and 115200 for Geos. It doesn't seem that there's a very good reason for varying from our default 115200 baud, so let's make the Geode target do that instead. Signed-off-by: David Woodhouse

x86: revert default root size back to 256 MB

2016-12-15T10:46:01Z

2 GB is overkill and was only added to allow unlimited ext4 resizing, which is a pretty rare use case. 256 MB allows resizing up to 256 GB, which should be good enough for almost all users. A lot of this is mostly irrelevant anyway, since you can just use squashfs + ext4 overlay. Signed-off-by: Felix Fietkau

uml: clean up the kernel config and add squashfs+ext4/f2fs support

2016-11-24T11:53:18Z

Replaces plain ext4 images Signed-off-by: Felix Fietkau

x86: bump default kernel partition size to 16M

2016-11-09T11:17:52Z

This leaves more room for sysupgrade config data or for having multiple kernel images to choose from Signed-off-by: Felix Fietkau

config: ext4: increase x86 rootfs size to 2GB to support online resize2fs

2016-10-27T17:24:38Z

The current default rootfs size of 256MB in conjunction with 4K blocks produces an ext4 filesystem which lacks the appropriate amount of backup GDT entries to support online-resizing. For x86 targets, increase the default rootfs size to 2048MB which allows online resizing the filesystem to up to 2TB which is the current theoretical maximum for LEDE, due to missing GPT support on the root block device. Note that the filesystem artefact will not occupy 2GB on the build system as the make_ext4fs utility uses sparse files to generate the filesystem images, so the actual disk usage is much lower. Furthermore the filesystem images are gzip compressed, shrinking them to only a few megabytes on the download server. Signed-off-by: Jo-Philipp Wich Acked-by: Michael Heimpold

config: ext4: drop option to set maximum number of inodes

2016-10-27T17:24:38Z

There is very little practical use to limit the number of available inodes on an ext4 filesystem and the make_ext4fs utility is able to calculate useful defaults by itself. Drop the option to make resulting ext4 filesystems more flexible by default. Signed-off-by: Jo-Philipp Wich Acked-by: Michael Heimpold