aboutsummaryrefslogtreecommitdiffstats
path: root/config/Config-images.in
Commit message (Collapse)AuthorAgeFilesLines
* build: make zstd initramfs selectableFelix Fietkau2021-02-161-0/+4
| | | | | | fix typo in kernel initramfs zstd compression option Signed-off-by: Felix Fietkau <nbd@nbd.name>
* build: use SPDX license tagsPaul Spooren2021-02-051-4/+2
| | | | | | | | | The license folder is a core part of OpenWrt and all GPL-2.0 licensed. Use SPDX license tags to allow machines to check licenses. Signed-off-by: Paul Spooren <mail@aparcar.org> [rebase, keep some Copyright lines, sharpen commit message] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* rb532: drop targetAdrian Schmutzler2020-09-021-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This target is still on kernel 4.14, and recent attempts to move it to kernel 5.4 have not led to success. The device tester reported that it wouldn't boot with the following messages: From sysupgrade: Press any key within 4 seconds to enter setup.... loading kernel from nand... OK setting up elf image... OK jumping to kernel code At this point the system hangs. From CompactFlash: Press any key within 4 seconds to enter setup.... Booting CF Loading kernel... done setting up elf image... kernel out of range kernel loading failed The tester reported that the same was observed with current master (kernel 4.14) as well. This looks like some kernel size restriction. Since this target is quite old and only supports one device, and since nobody else seemed interested in working on this for quite some time, I decided to not put further work into analyzing the problem and drop this together with the other 4.14-only targets. Patchwork series: https://patchwork.ozlabs.org/project/openwrt/list/?series=197066&state=* Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ar71xx: drop targetAdrian Schmutzler2020-08-301-1/+0
| | | | | | | | | | This target has been mostly replaced by ath79 and won't be included in the upcoming release anymore. Finally put it to rest. This also removes all references in packages, tools, etc. as well as the uboot-ar71xx and vsc73x5-ucode packages. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: add support for MikroTik RouterBOARD 493G (rb4xx series)Christopher Hill2020-06-151-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds support for the MikroTik RouterBOARD RB493G, ported from the ar71xx target. See https://routerboard.com/RB493G for details Specification: - SoC Qualcomm Atheros AR7161 - RAM: 256 MiB - Storage: 128MiB NAND - Ethernet: 9x 1000/100/10 Mbps - USB 1x 2.0 / 1.0 type A - PCIe: 3x Mini slot - MicroSD slot Working: - Board/system detection - Ethernet - SPI - NAND - LEDs - USB - Sysupgrade Enabled (but untested due to lack of hardware): - PCIe - ath79_pci_irq struct has the slot/pin/IRQ mappings if needed Installation methods: - tftp boot initramfs image, scp then flash via "sysupgrade -n" - nand boot existing OpenWrt, scp then flash via "sysupgrade -n" Notes: - initramfs image will not work if uncompressed image size over ~8.5Mb - The "rb4xx" drivers have been enabled Signed-off-by: Christopher Hill <ch6574@gmail.com>
* x86: generate EFI platform bootable images李国2020-03-311-10/+19
| | | | | | | | | | | | | | | | | Add EFI platform bootable images for x86 platforms. These images can also boot from legacy BIOS platform. EFI System Partition need to be fat12/fat16/fat32 (not need to load filesystem drivers), so the first partition of EFI images are not ext4 filesystem any more. GPT partition table has an alternate partition table, we did not generate it. This may cause problems when use these images as qemu disk (kernel can not find rootfs), we pad enough sectors will be ok. Signed-off-by: 李国 <uxgood.org@gmail.com> [part_magic_* refactoring, removed genisoimage checks] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* x86: switch image generation to new codePaul Spooren2020-03-211-10/+8
| | | | | | | | | | | | | | | | | | | | | | | | This commit introduces few related changes which need to be done in single commit to keep images buildable between git revisions. In result it retains all previous image creation possibilities with slight name change of generated images. Brief summary of the commit: * Split up image generation recipe to smaller chunks to make it more generic and reusable. * Make iso images x86 specific and drop their definition as root filesystem. * Convert image creation process to generic code specified in image.mk. * Make geode subtarget inherit features from the main target instead of redefining them. * For subtargets create device definitions with basic packages set. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl> [rebased] Signed-off-by: Paul Spooren <mail@aparcar.org>
* brcm2708: rename target to bcm27xxAdrian Schmutzler2020-02-141-1/+1
| | | | | | | | | | | | | | | | | This change makes the names of Broadcom targets consistent by using the common notation based on SoC/CPU ID (which is used internally anyway), bcmXXXX instead of brcmXXXX. This is even used for target TITLE in make menuconfig already, only the short target name used brcm so far. Despite, since subtargets range from bcm2708 to bcm2711, it seems appropriate to use bcm27xx instead of bcm2708 (again, as already done for BOARDNAME). This also renames the packages brcm2708-userland and brcm2708-gpu-fw. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> Acked-by: Álvaro Fernández Rojas <noltari@gmail.com>
* build: set TARGET_ROOTFS_PARTSIZE to make combined image fit in 128MBMatthias Schiffer2019-09-211-1/+1
| | | | | | | | | | | | Change TARGET_ROOTFS_PARTSIZE from 128 to 104 MiB, so the whole image (bootloader + boot + root) will fit on a 128MB CF card by default. With these settings, the generated images (tested on x86-generic and x86-64) have 126,353,408 bytes; the smallest CF card marketed as "128MB" that I found a datasheet for (a Transcend TS128MCF80) has 126,959,616 bytes. Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* brcm2708: add linux 4.19 supportÁlvaro Fernández Rojas2019-07-141-1/+1
| | | | | | Boot tested on Raspberry Pi B+ (BCM2708) and Raspberry Pi 2 (BCM2709) Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* build: enable gzipped images for armvirt and maltaPetr Štetiar2019-06-251-1/+1
| | | | | | | | As we're now going to pad all images by default to 128MiB let's enable compression of the images for armvirt and malta in order to save some space and bandwidth. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* build: make TARGET_ROOTFS_PARTSIZE 128MiB by defaultPetr Štetiar2019-06-251-1/+1
| | | | | | | | | | | As we're now going to pad all images by default, lets decrease the default rootfs partition size from 256MiB to 128MiB in order to save some space. I'm keeping it above 100MiB in order to keep current behavior, where overlay filesystem is using F2FS. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* build: remove TARGET_IMAGES_PAD optionPetr Štetiar2019-06-251-7/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | It's being used only in x86 target to produce combined images, where it's mandatory to have padded images in order to produce working squashfs combined images usable in QEMU. Currently we're producing unusable x86 combined squashfs images (18.06.1, 18.06.2 and snapshots) as we don't enable TARGET_IMAGES_PAD, thus providing very small space for the overlay filesystem, leading to the following with OpenWrt 18.06.1 r7258-5eb055306f images on x86 QEMU: root@(none):/# mount | egrep 'root|overlay' /dev/root on /rom type squashfs /dev/loop0 on /overlay type ext4 overlayfs:/overlay on / type overlay root@(none):/# df -h | egrep 'root|overlay|Size' Filesystem Size Used Available Use% Mounted on /dev/root 2.5M 2.5M 0 100% /rom /dev/loop0 113.0K 8.0K 97.0K 8% /overlay overlayfs:/overlay 113.0K 8.0K 97.0K 8% / So we should rather ensure proper image padding in image generation code and we shouldn't rely on config options in order to generate usable images. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* lantiq/xrx200: enable initramfs imagesStijn Segers2019-05-151-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | Commit eae6cac6a3 ("lantiq: add support for AVM FRITZ!Box 7362 SL"), but one needs an initramfs image to flash OpenWrt from stock firmware (as described in the commit log). This patch has the initramfs image built by default. Thanks to blogic (for pointing to the FEATURES declaration in the target Makefiles) and Musashino on the forum for suggesting config/Config-images.in needed editing too. While at it, reorder the TARGET_INITRAMFS_COMPRESSION_LZMA declarations alphabetically. This patch will result in initramfs images for all lantiq subtargets that have the ramdisk flag set. I tested on the falcon and ase subtargets, which lack that flag, to confirm they don't produce any initramfs images with this patch - which they do not. Given the limited scope of the lantiq (sub)target(s), blogic indicated this should be OK. Signed-off-by: Stijn Segers <foss@volatilesystems.org> Signed-off-by: Petr Štetiar <ynezz@true.cz> [fixed the wrong reference to eae6cac6a3 commit]
* mvebu: make bootfs size for sdcard image configurableTomasz Maciej Nowak2019-04-061-1/+1
| | | | | | | Let's take this oportunity to implement boot-part and rootfs-part feature flags. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* build: remove leftovers from previous x86 commitsTomasz Maciej Nowak2019-02-171-6/+3
| | | | | | | | | | | | | | | | | VBoxManage is not used and the image is created with proper permisions: 0f5d0f6 image: use internal qemu-img for vmdk and vdi images drop host dependencies on qemu-utils and VirtualBox Unreachable config symbols: 9e0759e x86: merge all geode based subtargets into one No need to define those symbols since x86_64 is subtarget of x86: 196fb76 x86: make x86_64 a subtarget instead of a standalone target Unreachable config symbols, so remove GRUB_ROOT: 371b382 x86: remove the xen_domu subtarget Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* omap: fix build without ext4 rootfsAndre Heider2019-01-311-1/+1
| | | | | | Same fix as 7b76219e, just for omap. Signed-off-by: Andre Heider <a.heider@gmail.com>
* brcm2708: boot-part feature integrationChristian Lamparter2019-01-241-0/+1
| | | | | | | | | | | | | | This patch adds the boot-part feature which enables the brcm2708 target move from the custom boot partition size config option to the generic CONFIG_TARGET_KERNEL_PARTSIZE. Note: For people using custom images: Just like with CONFIG_TARGET_ROOTFS_PARTSIZE changing the value can cause sysupgrade to repartition the device! Make sure to have a backup in this case. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: sata: boot-part feature integrationChristian Lamparter2019-01-011-0/+1
| | | | | | | | | | | | This patch adds the boot-part feature to the apm82181 sata target. This makes it possible to configure the boot partition size with the generic CONFIG_TARGET_KERNEL_PARTSIZE symbol. Please note: For people using custom images: Just like with CONFIG_TARGET_ROOTFS_PARTSIZE changing the value can cause sysupgrade to repartition the device! Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* sunxi: fix build without ext4 rootfsAndre Heider2018-09-291-1/+1
| | | | | | | | | | | | The sdcard image generation uses CONFIG_TARGET_ROOTFS_PARTSIZE, which is currently bound to TARGET_ROOTFS_EXT4FS on this target. Since the rootfs is squashfs anyway, allow deselecting of the ext4fs one. Sort the target list alphabetically while here. Signed-off-by: Andre Heider <a.heider@gmail.com>
* build: add support for enabling the rootfs/boot partition size option via ↵Felix Fietkau2018-09-031-2/+2
| | | | | | target feature Signed-off-by: Felix Fietkau <nbd@nbd.name>
* x86: add support to set GRUB menu entry titleKjel Delaey2018-07-301-0/+8
| | | | | | | | $ make menuconfig Target Images -> Title for the menu entry in GRUB Signed-off-by: Kjel Delaey <kjel_delaey@hotmail.com>
* config: extend small_flash featureAlex Maclean2018-07-121-0/+1
| | | | | | | | | | Extend the small_flash feature to disable swap, core dumps, and kernel debug info, and change the squashfs block size to 1024KiB. Also change squashfs fragment cache to 2 for small_flash to ease memory usage. Signed-off-by: Alex Maclean <monkeh@monkeh.net>
* config: support new symbol intro'd in kernel 4.12Koen Vandeputte2018-01-131-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 <koen.vandeputte@ncentric.com>
* mpc85xx: Enable initramfs for p1020 subtargetChris Blake2017-10-141-0/+1
| | | | | | | The following patch enables building of initramfs images by default for the P1020 subtarget in mpc85xx. Signed-off-by: Chris Blake <chrisrblake93@gmail.com>
* build: enable gzipping of images on x86 even if ext4 is disabledFelix Fietkau2017-07-061-1/+1
| | | | | | | There is lots of padding between the boot partition and the rootfs, so gzipping is helpful here Signed-off-by: Felix Fietkau <nbd@nbd.name>
* build: allow specifying flow-control to grub on serial consolePhilip Prindeville2017-04-031-0/+5
| | | | | | | On the more sophisticated (i.e. deeper FIFO) serial controllers, flow-control might be needed to avoid dropping output. Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
* x86: Set default baud rate on Geode images to 115200David Woodhouse2017-02-171-1/+0
| | | | | | | | | | | 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 <dwmw2@infradead.org>
* x86: revert default root size back to 256 MBFelix Fietkau2016-12-151-2/+1
| | | | | | | | | | | 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 <nbd@nbd.name>
* uml: clean up the kernel config and add squashfs+ext4/f2fs supportFelix Fietkau2016-11-241-1/+1
| | | | | | Replaces plain ext4 images Signed-off-by: Felix Fietkau <nbd@nbd.name>
* x86: bump default kernel partition size to 16MFelix Fietkau2016-11-091-1/+1
| | | | | | | This leaves more room for sysupgrade config data or for having multiple kernel images to choose from Signed-off-by: Felix Fietkau <nbd@nbd.name>
* config: ext4: increase x86 rootfs size to 2GB to support online resize2fsJo-Philipp Wich2016-10-271-1/+2
| | | | | | | | | | | | | | | | | | | 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 <jo@mein.io> Acked-by: Michael Heimpold <mhei@heimpold.de>
* config: ext4: drop option to set maximum number of inodesJo-Philipp Wich2016-10-271-7/+0
| | | | | | | | | | | 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 <jo@mein.io> Acked-by: Michael Heimpold <mhei@heimpold.de>
* images: bump default rootfs size to 256 MBFelix Fietkau2016-09-081-1/+1
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* mvebu: add sdcard image creation scriptJosua Mayer2016-09-021-1/+1
| | | | | | | | | | | | | | | | Added gen_mvebu_sdcard_img.sh to facilitate creating an fixed-size sdcard image, adding the bootloader and populating it with actual data. Added the required rules for creating a 4GB sdcard image according to this layout: p0: boot (fat32) p1: rootfs (squashfs) p2: rootfs_data (ext4) This should be generic to any mvebu boards that can boot from block storage. Added the new sdcard image to the Clearfog image profile. Signed-off-by: Josua Mayer <josua.mayer97@gmail.com> Signed-off-by: Felix Fietkau <nbd@nbd.name> [cleanup]
* apm821xx: use lzma compression for the initramfs imagesChristian Lamparter2016-07-251-0/+1
| | | | | | | | | | | | | | | | | | | | | | The MR24's u-boot takes it sweet time decompressing the LZMA-packed initramfs image. A user reported that compared to the old gzip method in v2: it "takes a ton longer to decompress like 4\x the old boot time for decompression". This patch also fixes a issue with the WNDR4700's initramfs image getting to big and causing the following u-boot crash during the decompression: "Uncompressing Multi-File Image ... Error: inflate() returned -5 out-of-mem or overwrite error - must RESET board to recover" This patch fixes both issues by reverting the MR24's initramfs compression method back to gzip. And choosing to compress the initramfs within the initramfs image as LZMA by default. Cc: chrisrblake93@gmail.com Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* config: remove options for including kernel/dtb in rootfsFelix Fietkau2016-07-201-41/+0
| | | | | | These options were a big design flaw to begin with Signed-off-by: Felix Fietkau <nbd@nbd.name>
* build: make TARGET_ROOTFS_JFFS2 depend on USES_JFFS2Felix Fietkau2016-07-201-1/+1
| | | | | | | If jffs2 support was not enabled by the target, jffs2 are quite likely to be broken, so we shouldn't build them. Signed-off-by: Felix Fietkau <nbd@nbd.name>
* build: remove leftover dependenices on TARGET_rdcFelix Fietkau2016-05-121-1/+1
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* x86: clean up default grub baudrate settingsFelix Fietkau2015-03-291-4/+3
| | | | | | Signed-off-by: Felix Fietkau <nbd@openwrt.org> SVN-Revision: 45113
* build: remove leftover olpc support codeFelix Fietkau2015-03-281-4/+4
| | | | | | Signed-off-by: Felix Fietkau <nbd@openwrt.org> SVN-Revision: 45084
* x86: use PARTUUID instead explicitly specifying the device by defaultJo-Philipp Wich2015-03-241-2/+0
| | | | | | | | | | | | | This changes the x86 image generation to match x86_64, using the PARTUUID for the rootfs instead of explicitly configuring the device. It unbreaks KVM with VirtIO, which uses /dev/vda2 instead of /dev/sda2. Tested in QEMU/KVM with VirtIO, VirtualBox and VMware. Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net> SVN-Revision: 44966
* config: use PARTUUID by default on x86_64Jo-Philipp Wich2014-10-271-3/+4
| | | | | | Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 43086
* Kconfig: Various typo/grammar/line-length fixes in Config*.in filesHauke Mehrtens2014-09-131-17/+17
| | | | | | | | | | | | | Non-functional changes to config/Config-*.in files, including: * spelling mistakes * inconsistent terminology * grammar * overly long lines in "help" components Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca> SVN-Revision: 42519
* x86: add back a line accidentally removed in r41763Felix Fietkau2014-07-201-0/+1
| | | | | | Signed-off-by: Felix Fietkau <nbd@openwrt.org> SVN-Revision: 41764
* x86: remove the arbitrary limitation of vmware/virtualbox images to ext4, ↵Felix Fietkau2014-07-201-3/+2
| | | | | | | | select TARGET_IMAGES_PAD instead Signed-off-by: Felix Fietkau <nbd@openwrt.org> SVN-Revision: 41763
* config/Config-images.in: enable zlib as the default ubi compressionJohn Crispin2014-06-241-1/+1
| | | | | | | | http://patchwork.openwrt.org/patch/5686/ Signed-off-by: John Crispin <blogic@openwrt.org> SVN-Revision: 41329
* build: set default squashfs block size to 64k for low-memory systemsFelix Fietkau2014-06-021-0/+1
| | | | | | Signed-off-by: Felix Fietkau <nbd@openwrt.org> SVN-Revision: 40981
* build: make the squashfs block size configurableFelix Fietkau2014-06-021-1/+6
| | | | | | Signed-off-by: Felix Fietkau <nbd@openwrt.org> SVN-Revision: 40979
* config/Config-images.in: the ext4 series introduced a regressionJohn Crispin2014-06-021-3/+3
| | | | | | Signed-off-by: John Crispin <blogic@openwrt.org> SVN-Revision: 40951
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-19 16:18:05 +0000