RepoMirrors
/
openwrt
mirror of git://git.openwrt.org/openwrt/openwrt.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
openwrt/config/Config-images.in

326 lines
8.5 KiB
Plaintext
Raw Normal View History

build: use SPDX license tags 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>
2020-09-22 02:48:37 +00:00
# SPDX-License-Identifier: GPL-2.0-only
move menuconfig options into separate files Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 38895
2013-11-22 14:30:40 +00:00
#
build: use SPDX license tags 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>
2020-09-22 02:48:37 +00:00
# Copyright (C) 2006-2013 OpenWrt.org
move menuconfig options into separate files Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 38895
2013-11-22 14:30:40 +00:00
menu "Target Images"
menuconfig TARGET_ROOTFS_INITRAMFS
bool "ramdisk"
default y if USES_INITRAMFS
help
Kconfig: Various typo/grammar/line-length fixes in Config*.in files 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
2014-09-13 20:27:25 +00:00
Embed the root filesystem into the kernel (initramfs).
move menuconfig options into separate files Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 38895
2013-11-22 14:30:40 +00:00
choice
prompt "Compression"
apm821xx: use lzma compression for the initramfs images 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>
2016-07-23 12:20:52 +00:00
default TARGET_INITRAMFS_COMPRESSION_LZMA if TARGET_apm821xx
ath79: add support for MikroTik RouterBOARD 493G (rb4xx series) 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>
2020-05-26 01:10:00 +00:00
default TARGET_INITRAMFS_COMPRESSION_LZMA if TARGET_ath79_mikrotik
lantiq/xrx200: enable initramfs images 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]
2019-04-27 16:23:21 +00:00
default TARGET_INITRAMFS_COMPRESSION_LZMA if TARGET_lantiq
mpc85xx: Enable initramfs for p1020 subtarget The following patch enables building of initramfs images by default for the P1020 subtarget in mpc85xx. Signed-off-by: Chris Blake <chrisrblake93@gmail.com>
2017-09-30 16:13:35 +00:00
default TARGET_INITRAMFS_COMPRESSION_LZMA if TARGET_mpc85xx
lantiq/xrx200: enable initramfs images 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]
2019-04-27 16:23:21 +00:00
default TARGET_INITRAMFS_COMPRESSION_LZMA if TARGET_ramips
ipq807x: rename target to qualcommax Currently, ipq807x only covers Qualcomm IPQ807x SoC-s. However, Qualcomm also has IPQ60xx and IPQ50xx SoC-s under the AX WiSoC-s and they share a lot of stuff with IPQ807x, especially IPQ60xx so to avoid duplicating kernel patches and everything lets make a common target with per SoC subtargets. Start doing that by renaming ipq807x to qualcommax so that dependencies on ipq807x target can be updated. Signed-off-by: Robert Marko <robimarko@gmail.com>
2023-06-11 17:32:52 +00:00
default TARGET_INITRAMFS_COMPRESSION_ZSTD if TARGET_qualcommax
treewide: fix spelling 'seperate' -> 'separate' This popular spelling mistake was also introduced by myself lately. Fix it everywhere. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
2021-02-28 23:58:10 +00:00
default TARGET_INITRAMFS_COMPRESSION_XZ if USES_SEPARATE_INITRAMFS
move menuconfig options into separate files Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 38895
2013-11-22 14:30:40 +00:00
default TARGET_INITRAMFS_COMPRESSION_NONE
depends on TARGET_ROOTFS_INITRAMFS
help
Select ramdisk compression.
config TARGET_INITRAMFS_COMPRESSION_NONE
bool "none"
config TARGET_INITRAMFS_COMPRESSION_GZIP
bool "gzip"
config TARGET_INITRAMFS_COMPRESSION_BZIP2
bool "bzip2"
config TARGET_INITRAMFS_COMPRESSION_LZMA
bool "lzma"
config TARGET_INITRAMFS_COMPRESSION_LZO
bool "lzo"
config TARGET_INITRAMFS_COMPRESSION_LZ4
bool "lz4"
config TARGET_INITRAMFS_COMPRESSION_XZ
bool "xz"
build: make zstd initramfs selectable fix typo in kernel initramfs zstd compression option Signed-off-by: Felix Fietkau <nbd@nbd.name>
2020-10-23 09:48:11 +00:00
config TARGET_INITRAMFS_COMPRESSION_ZSTD
bool "zstd"
move menuconfig options into separate files Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 38895
2013-11-22 14:30:40 +00:00
endchoice
config EXTERNAL_CPIO
string
prompt "Use external cpio" if TARGET_ROOTFS_INITRAMFS
default ""
help
Kconfig: Various typo/grammar/line-length fixes in Config*.in files 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
2014-09-13 20:27:25 +00:00
Kernel uses specified external cpio as INITRAMFS_SOURCE.
move menuconfig options into separate files Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 38895
2013-11-22 14:30:40 +00:00
config: support new symbol intro'd in kernel 4.12 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>
2018-01-11 11:55:02 +00:00
config TARGET_INITRAMFS_FORCE
image: allow building FIT and uImage with ramdisk Instead of embedding the initrd cpio archive into the kernel, allow for having an external ramdisk added to the FIT or uImage. This is useful to overcome kernel size limitations present in many stock bootloaders, as the ramdisk is then loaded seperately and doesn't add to the kernel size. Hence we can have larger ramdisks to host ie. installers with all binaries to flash included (or a web-based firmware selector). In terms of performance and total size the differences are neglectible. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
2021-02-21 14:19:26 +00:00
bool "Force"
depends on TARGET_ROOTFS_INITRAMFS
help
Ignore the initramfs passed by the bootloader.
treewide: fix spelling 'seperate' -> 'separate' This popular spelling mistake was also introduced by myself lately. Fix it everywhere. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
2021-02-28 23:58:10 +00:00
config TARGET_ROOTFS_INITRAMFS_SEPARATE
bool "separate ramdisk"
depends on USES_SEPARATE_INITRAMFS && TARGET_ROOTFS_INITRAMFS && !TARGET_INITRAMFS_FORCE
default y if USES_SEPARATE_INITRAMFS
image: allow building FIT and uImage with ramdisk Instead of embedding the initrd cpio archive into the kernel, allow for having an external ramdisk added to the FIT or uImage. This is useful to overcome kernel size limitations present in many stock bootloaders, as the ramdisk is then loaded seperately and doesn't add to the kernel size. Hence we can have larger ramdisks to host ie. installers with all binaries to flash included (or a web-based firmware selector). In terms of performance and total size the differences are neglectible. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
2021-02-21 14:19:26 +00:00
help
treewide: fix spelling 'seperate' -> 'separate' This popular spelling mistake was also introduced by myself lately. Fix it everywhere. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
2021-02-28 23:58:10 +00:00
Generate separate initrd.cpio instead of embedding it.
image: allow building FIT and uImage with ramdisk Instead of embedding the initrd cpio archive into the kernel, allow for having an external ramdisk added to the FIT or uImage. This is useful to overcome kernel size limitations present in many stock bootloaders, as the ramdisk is then loaded seperately and doesn't add to the kernel size. Hence we can have larger ramdisks to host ie. installers with all binaries to flash included (or a web-based firmware selector). In terms of performance and total size the differences are neglectible. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
2021-02-21 14:19:26 +00:00
This is useful for generating images with a dedicated
ramdisk e.g. in U-Boot's uImage and uImage.FIT formats.
config: support new symbol intro'd in kernel 4.12 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>
2018-01-11 11:55:02 +00:00
move menuconfig options into separate files Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 38895
2013-11-22 14:30:40 +00:00
comment "Root filesystem archives"
config TARGET_ROOTFS_CPIOGZ
bool "cpio.gz"
default y if USES_CPIOGZ
help
Kconfig: Various typo/grammar/line-length fixes in Config*.in files 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
2014-09-13 20:27:25 +00:00
Build a compressed cpio archive of the root filesystem.
move menuconfig options into separate files Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 38895
2013-11-22 14:30:40 +00:00
config TARGET_ROOTFS_TARGZ
bool "tar.gz"
default y if USES_TARGZ
help
Kconfig: Various typo/grammar/line-length fixes in Config*.in files 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
2014-09-13 20:27:25 +00:00
Build a compressed tar archive of the root filesystem.
move menuconfig options into separate files Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 38895
2013-11-22 14:30:40 +00:00
comment "Root filesystem images"
image: ext4: move ext4 specific options into submenu Signed-off-by: Michael Heimpold <mhei@heimpold.de> SVN-Revision: 40923
2014-06-02 12:43:53 +00:00
menuconfig TARGET_ROOTFS_EXT4FS
move menuconfig options into separate files Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 38895
2013-11-22 14:30:40 +00:00
bool "ext4"
default y if USES_EXT4
help
Kconfig: Various typo/grammar/line-length fixes in Config*.in files 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
2014-09-13 20:27:25 +00:00
Build an ext4 root filesystem.
image: ext4: move ext4 specific options into submenu Signed-off-by: Michael Heimpold <mhei@heimpold.de> SVN-Revision: 40923
2014-06-02 12:43:53 +00:00
image: ext4: rename config options as these are only used for ext4 image creation Signed-off-by: Michael Heimpold <mhei@heimpold.de> SVN-Revision: 40926
2014-06-02 12:44:10 +00:00
config TARGET_EXT4_RESERVED_PCT
image: ext4: move ext4 specific options into submenu Signed-off-by: Michael Heimpold <mhei@heimpold.de> SVN-Revision: 40923
2014-06-02 12:43:53 +00:00
int "Percentage of reserved blocks in root filesystem"
depends on TARGET_ROOTFS_EXT4FS
default 0
help
Kconfig: Various typo/grammar/line-length fixes in Config*.in files 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
2014-09-13 20:27:25 +00:00
Select the percentage of reserved blocks in the root filesystem.
move menuconfig options into separate files Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 38895
2013-11-22 14:30:40 +00:00
image: ext4: allow to choose a block size for the rootfs Signed-off-by: Michael Heimpold <mhei@heimpold.de> SVN-Revision: 40924
2014-06-02 12:44:04 +00:00
choice
config/Config-images.in: the ext4 series introduced a regression Signed-off-by: John Crispin <blogic@openwrt.org> SVN-Revision: 40951
2014-06-02 13:03:15 +00:00
prompt "Root filesystem block size"
image: ext4: allow to choose a block size for the rootfs Signed-off-by: Michael Heimpold <mhei@heimpold.de> SVN-Revision: 40924
2014-06-02 12:44:04 +00:00
default TARGET_EXT4_BLOCKSIZE_4K
config/Config-images.in: the ext4 series introduced a regression Signed-off-by: John Crispin <blogic@openwrt.org> SVN-Revision: 40951
2014-06-02 13:03:15 +00:00
depends on TARGET_ROOTFS_EXT4FS
image: ext4: allow to choose a block size for the rootfs Signed-off-by: Michael Heimpold <mhei@heimpold.de> SVN-Revision: 40924
2014-06-02 12:44:04 +00:00
help
Kconfig: Various typo/grammar/line-length fixes in Config*.in files 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
2014-09-13 20:27:25 +00:00
Select the block size of the root filesystem.
image: ext4: allow to choose a block size for the rootfs Signed-off-by: Michael Heimpold <mhei@heimpold.de> SVN-Revision: 40924
2014-06-02 12:44:04 +00:00
config TARGET_EXT4_BLOCKSIZE_4K
bool "4k"
config TARGET_EXT4_BLOCKSIZE_2K
bool "2k"
config TARGET_EXT4_BLOCKSIZE_1K
bool "1k"
endchoice
config TARGET_EXT4_BLOCKSIZE
int
default 4096 if TARGET_EXT4_BLOCKSIZE_4K
default 2048 if TARGET_EXT4_BLOCKSIZE_2K
default 1024 if TARGET_EXT4_BLOCKSIZE_1K
config/Config-images.in: the ext4 series introduced a regression Signed-off-by: John Crispin <blogic@openwrt.org> SVN-Revision: 40951
2014-06-02 13:03:15 +00:00
depends on TARGET_ROOTFS_EXT4FS
image: ext4: allow to choose a block size for the rootfs Signed-off-by: Michael Heimpold <mhei@heimpold.de> SVN-Revision: 40924
2014-06-02 12:44:04 +00:00
image: ext4: allow creation of a journaling filesystem Signed-off-by: Michael Heimpold <mhei@heimpold.de> SVN-Revision: 40925
2014-06-02 12:44:07 +00:00
config TARGET_EXT4_JOURNAL
bool "Create a journaling filesystem"
depends on TARGET_ROOTFS_EXT4FS
config: Enable ext4 journaling by default. Not having a journal by default is a major "gotcha". Because openwrt does not fsck on boot, a power loss without journaling can result in a dirty filesystem that openwrt will mount as read-only which requires intervention to restore the router to working order. Signed-off-by: Jordan Woyak <jordan.woyak@gmail.com>
2024-03-26 01:56:06 +00:00
default y
image: ext4: allow creation of a journaling filesystem Signed-off-by: Michael Heimpold <mhei@heimpold.de> SVN-Revision: 40925
2014-06-02 12:44:07 +00:00
help
Kconfig: Various typo/grammar/line-length fixes in Config*.in files 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
2014-09-13 20:27:25 +00:00
Create an ext4 filesystem with a journal.
image: ext4: allow creation of a journaling filesystem Signed-off-by: Michael Heimpold <mhei@heimpold.de> SVN-Revision: 40925
2014-06-02 12:44:07 +00:00
move menuconfig options into separate files Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 38895
2013-11-22 14:30:40 +00:00
config TARGET_ROOTFS_JFFS2
bool "jffs2"
build: make TARGET_ROOTFS_JFFS2 depend on USES_JFFS2 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>
2016-07-19 10:21:29 +00:00
depends on USES_JFFS2
move menuconfig options into separate files Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 38895
2013-11-22 14:30:40 +00:00
help
Kconfig: Various typo/grammar/line-length fixes in Config*.in files 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
2014-09-13 20:27:25 +00:00
Build a JFFS2 root filesystem.
move menuconfig options into separate files Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 38895
2013-11-22 14:30:40 +00:00
config TARGET_ROOTFS_JFFS2_NAND
bool "jffs2 for NAND"
default y if USES_JFFS2_NAND
depends on USES_JFFS2_NAND
help
Kconfig: Various typo/grammar/line-length fixes in Config*.in files 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
2014-09-13 20:27:25 +00:00
Build a JFFS2 root filesystem for NAND flash.
move menuconfig options into separate files Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 38895
2013-11-22 14:30:40 +00:00
build: make the squashfs block size configurable Signed-off-by: Felix Fietkau <nbd@openwrt.org> SVN-Revision: 40979
2014-06-02 17:04:34 +00:00
menuconfig TARGET_ROOTFS_SQUASHFS
move menuconfig options into separate files Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 38895
2013-11-22 14:30:40 +00:00
bool "squashfs"
default y if USES_SQUASHFS
help
build: images: squashfs: add help, fix description add help text for `TARGET_SQUASHFS_BLOCK_SIZE` to match the only valid settings accepted by `mksquashfs4` ("block size not power of two or not between 4096 and 1Mbyte") thus for this setting in "KB", the set: `4, 8, 16, 32, 64, 128, 256, 512, 1024` replace `squashfs-lzma` with `squashfs` in the description for `TARGET_ROOTFS_SQUASHFS` because it has various compressions, and not just lzma as it did in the past cosmetic change with no functional effect Signed-off-by: Tony Butler <spudz76@gmail.com>
2022-11-28 12:00:02 +00:00
Build a squashfs root filesystem.
move menuconfig options into separate files Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 38895
2013-11-22 14:30:40 +00:00
build: make the squashfs block size configurable Signed-off-by: Felix Fietkau <nbd@openwrt.org> SVN-Revision: 40979
2014-06-02 17:04:34 +00:00
config TARGET_SQUASHFS_BLOCK_SIZE
int "Block size (in KiB)"
depends on TARGET_ROOTFS_SQUASHFS
build: set default squashfs block size to 64k for low-memory systems Signed-off-by: Felix Fietkau <nbd@openwrt.org> SVN-Revision: 40981
2014-06-02 17:04:41 +00:00
default 64 if LOW_MEMORY_FOOTPRINT
config: extend small_flash feature 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>
2018-07-09 17:09:05 +00:00
default 1024 if (SMALL_FLASH && !LOW_MEMORY_FOOTPRINT)
build: make the squashfs block size configurable Signed-off-by: Felix Fietkau <nbd@openwrt.org> SVN-Revision: 40979
2014-06-02 17:04:34 +00:00
default 256
build: images: squashfs: add help, fix description add help text for `TARGET_SQUASHFS_BLOCK_SIZE` to match the only valid settings accepted by `mksquashfs4` ("block size not power of two or not between 4096 and 1Mbyte") thus for this setting in "KB", the set: `4, 8, 16, 32, 64, 128, 256, 512, 1024` replace `squashfs-lzma` with `squashfs` in the description for `TARGET_ROOTFS_SQUASHFS` because it has various compressions, and not just lzma as it did in the past cosmetic change with no functional effect Signed-off-by: Tony Butler <spudz76@gmail.com>
2022-11-28 12:00:02 +00:00
help
Select squashfs block size, must be one of:
4, 8, 16, 32, 64, 128, 256, 512, 1024
build: make the squashfs block size configurable Signed-off-by: Felix Fietkau <nbd@openwrt.org> SVN-Revision: 40979
2014-06-02 17:04:34 +00:00
move menuconfig options into separate files Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 38895
2013-11-22 14:30:40 +00:00
menuconfig TARGET_ROOTFS_UBIFS
bool "ubifs"
default y if USES_UBIFS
depends on USES_UBIFS
help
Kconfig: Various typo/grammar/line-length fixes in Config*.in files 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
2014-09-13 20:27:25 +00:00
Build a UBIFS root filesystem.
move menuconfig options into separate files Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 38895
2013-11-22 14:30:40 +00:00
choice
prompt "compression"
config/Config-images.in: enable zlib as the default ubi compression http://patchwork.openwrt.org/patch/5686/ Signed-off-by: John Crispin <blogic@openwrt.org> SVN-Revision: 41329
2014-06-24 18:14:05 +00:00
default TARGET_UBIFS_COMPRESSION_ZLIB
move menuconfig options into separate files Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 38895
2013-11-22 14:30:40 +00:00
depends on TARGET_ROOTFS_UBIFS
help
Select compression type
config TARGET_UBIFS_COMPRESSION_NONE
bool "none"
config TARGET_UBIFS_COMPRESSION_LZO
bool "lzo"
config TARGET_UBIFS_COMPRESSION_ZLIB
bool "zlib"
endchoice
config TARGET_UBIFS_FREE_SPACE_FIXUP
bool "free space fixup" if TARGET_ROOTFS_UBIFS
default y
help
Kconfig: Various typo/grammar/line-length fixes in Config*.in files 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
2014-09-13 20:27:25 +00:00
The filesystem free space has to be fixed up on first mount.
move menuconfig options into separate files Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 38895
2013-11-22 14:30:40 +00:00
config TARGET_UBIFS_JOURNAL_SIZE
string
prompt "journal size" if TARGET_ROOTFS_UBIFS
default ""
move most of the x86 image generation options to the main file Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 39206
2014-01-07 10:18:55 +00:00
config GRUB_IMAGES
bool "Build GRUB images (Linux x86 or x86_64 host only)"
build: remove leftover dependenices on TARGET_rdc Signed-off-by: Felix Fietkau <nbd@nbd.name>
2016-05-12 15:43:17 +00:00
depends on TARGET_x86
x86: switch image generation to new code 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>
2020-03-20 10:10:55 +00:00
depends on TARGET_ROOTFS_EXT4FS || TARGET_ROOTFS_JFFS2 || TARGET_ROOTFS_SQUASHFS
move most of the x86 image generation options to the main file Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 39206
2014-01-07 10:18:55 +00:00
select PACKAGE_grub2
grub2: make grub2-bios-setup as a separate package The grub2 and grub2-efi packages should only contain boot-related code. grub-bios-setup is the same as grub-editenv, they are both grub2 tools and should be placed in a separate package. Signed-off-by: 李国 <uxgood.org@gmail.com> [use AUTORELEASE and update to SPDX] Signed-off-by: Paul Spooren <mail@aparcar.org>
2020-07-25 04:04:05 +00:00
select PACKAGE_grub2-bios-setup
move most of the x86 image generation options to the main file Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 39206
2014-01-07 10:18:55 +00:00
default y
x86: generate EFI platform bootable images 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>
2020-03-26 06:05:33 +00:00
config GRUB_EFI_IMAGES
loongarch64: new target Add target for Loongson LoongArch64-based boards. LoongArch is a new RISC ISA developed by Loongson. It's a bit like MIPS or RISC-V. LoongArch includes both 32-bit and 64-bit versions (LoongArch32/LoongArch64). Loongson 3A5000 and 3A6000 are the two existing CPUs of LoongArch64 and is used for PC products. It's BIOS supports ACPI and UEFI-only boot. These CPUs supports SMP and SMT. At present only LoongArch64 is supported by linux kernel. Toolchain requirement: binutils >= 2.40 gcc >= 13.1 For details, please check the following links: https://lwn.net/Articles/861951/ https://loongson.github.io/LoongArch-Documentation/README-EN.html Signed-off-by: Weijie Gao <hackpascal@gmail.com>
2024-01-06 19:10:45 +00:00
bool "Build GRUB EFI images"
depends on TARGET_x86 || TARGET_armsr || TARGET_loongarch64
x86: generate EFI platform bootable images 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>
2020-03-26 06:05:33 +00:00
depends on TARGET_ROOTFS_EXT4FS || TARGET_ROOTFS_JFFS2 || TARGET_ROOTFS_SQUASHFS
grub2: enable EFI for armvirt This adds a separate package for EFI on Arm SystemReady compatible machines. 32-bit Arm UEFI is supported as well. It is very similar to x86-64 EFI setup, without the need for BIOS backward compatibility and slightly different default modules. Signed-off-by: Mathew McBride <matt@traverse.com.au>
2021-02-24 04:53:40 +00:00
select PACKAGE_grub2 if TARGET_x86
select PACKAGE_grub2-efi if TARGET_x86
select PACKAGE_grub2-bios-setup if TARGET_x86
config: change references from armvirt to armsr armvirt target has been renamed to armsr (Arm SystemReady), so the config defaults need to be changed as well. Signed-off-by: Mathew McBride <matt@traverse.com.au>
2023-06-06 23:22:01 +00:00
select PACKAGE_grub2-efi-arm if TARGET_armsr
loongarch64: new target Add target for Loongson LoongArch64-based boards. LoongArch is a new RISC ISA developed by Loongson. It's a bit like MIPS or RISC-V. LoongArch includes both 32-bit and 64-bit versions (LoongArch32/LoongArch64). Loongson 3A5000 and 3A6000 are the two existing CPUs of LoongArch64 and is used for PC products. It's BIOS supports ACPI and UEFI-only boot. These CPUs supports SMP and SMT. At present only LoongArch64 is supported by linux kernel. Toolchain requirement: binutils >= 2.40 gcc >= 13.1 For details, please check the following links: https://lwn.net/Articles/861951/ https://loongson.github.io/LoongArch-Documentation/README-EN.html Signed-off-by: Weijie Gao <hackpascal@gmail.com>
2024-01-06 19:10:45 +00:00
select PACKAGE_grub2-efi-loongarch64 if TARGET_loongarch64
x86: generate EFI platform bootable images 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>
2020-03-26 06:05:33 +00:00
select PACKAGE_kmod-fs-vfat
default y
move most of the x86 image generation options to the main file Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 39206
2014-01-07 10:18:55 +00:00
config GRUB_CONSOLE
bool "Use Console Terminal (in addition to Serial)"
x86: generate EFI platform bootable images 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>
2020-03-26 06:05:33 +00:00
depends on GRUB_IMAGES || GRUB_EFI_IMAGES
move most of the x86 image generation options to the main file Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 39206
2014-01-07 10:18:55 +00:00
default y
config GRUB_BAUDRATE
int "Serial port baud rate"
x86: generate EFI platform bootable images 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>
2020-03-26 06:05:33 +00:00
depends on GRUB_IMAGES || GRUB_EFI_IMAGES
x86: clean up default grub baudrate settings Signed-off-by: Felix Fietkau <nbd@openwrt.org> SVN-Revision: 45113
2015-03-29 04:31:21 +00:00
default 38400 if TARGET_x86_generic
default 115200
move most of the x86 image generation options to the main file Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 39206
2014-01-07 10:18:55 +00:00
build: allow specifying flow-control to grub on serial console 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>
2017-02-07 03:33:36 +00:00
config GRUB_FLOWCONTROL
bool "Use RTE/CTS on serial console"
target: Make TARGET_SERIAL independent of GRUB configuration GRUB_SERIAL is also used for the default serial on the target and not only in grub. When no grub was build it was not available and the build fails. Rename GRUB_SERIAL to TARGET_SERIAL and make it always available on x86 and armsr targets. Fixes: #14063 Fixes: b10768476f9d ("x86,armsr: interpolate GRUB_SERIAL into /etc/inittab") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
2023-11-26 22:04:04 +00:00
depends on GRUB_IMAGES || GRUB_EFI_IMAGES
depends on TARGET_SERIAL != ""
build: allow specifying flow-control to grub on serial console 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>
2017-02-07 03:33:36 +00:00
move most of the x86 image generation options to the main file Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 39206
2014-01-07 10:18:55 +00:00
config GRUB_BOOTOPTS
string "Extra kernel boot options"
x86: generate EFI platform bootable images 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>
2020-03-26 06:05:33 +00:00
depends on GRUB_IMAGES || GRUB_EFI_IMAGES
move most of the x86 image generation options to the main file Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 39206
2014-01-07 10:18:55 +00:00
help
If you don't know, just leave it blank.
config GRUB_TIMEOUT
string "Seconds to wait before booting the default entry"
x86: generate EFI platform bootable images 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>
2020-03-26 06:05:33 +00:00
depends on GRUB_IMAGES || GRUB_EFI_IMAGES
move most of the x86 image generation options to the main file Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 39206
2014-01-07 10:18:55 +00:00
default "5"
help
If you don't know, 5 seconds is a reasonable default.
x86: add support to set GRUB menu entry title $ make menuconfig Target Images -> Title for the menu entry in GRUB Signed-off-by: Kjel Delaey <kjel_delaey@hotmail.com>
2018-06-05 13:47:05 +00:00
config GRUB_TITLE
string "Title for the menu entry in GRUB"
x86: generate EFI platform bootable images 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>
2020-03-26 06:05:33 +00:00
depends on GRUB_IMAGES || GRUB_EFI_IMAGES
x86: add support to set GRUB menu entry title $ make menuconfig Target Images -> Title for the menu entry in GRUB Signed-off-by: Kjel Delaey <kjel_delaey@hotmail.com>
2018-06-05 13:47:05 +00:00
default "OpenWrt"
help
This is the title of the GRUB menu entry.
If unspecified, it defaults to OpenWrt.
x86: switch image generation to new code 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>
2020-03-20 10:10:55 +00:00
config ISO_IMAGES
bool "Build LiveCD image (ISO)"
depends on TARGET_x86
x86: generate EFI platform bootable images 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>
2020-03-26 06:05:33 +00:00
depends on GRUB_IMAGES || GRUB_EFI_IMAGES
x86: switch image generation to new code 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>
2020-03-20 10:10:55 +00:00
move most of the x86 image generation options to the main file Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 39206
2014-01-07 10:18:55 +00:00
config VDI_IMAGES
bool "Build VirtualBox image files (VDI)"
build: remove leftovers from previous x86 commits 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>
2019-01-13 20:37:47 +00:00
depends on TARGET_x86
x86: generate EFI platform bootable images 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>
2020-03-26 06:05:33 +00:00
depends on GRUB_IMAGES || GRUB_EFI_IMAGES
virtualbox emulates the e1000 for a long time now Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 39207
2014-01-07 10:21:31 +00:00
select PACKAGE_kmod-e1000
move most of the x86 image generation options to the main file Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 39206
2014-01-07 10:18:55 +00:00
config VMDK_IMAGES
bool "Build VMware image files (VMDK)"
config: change references from armvirt to armsr armvirt target has been renamed to armsr (Arm SystemReady), so the config defaults need to be changed as well. Signed-off-by: Mathew McBride <matt@traverse.com.au>
2023-06-06 23:22:01 +00:00
depends on TARGET_x86 || TARGET_armsr
x86: generate EFI platform bootable images 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>
2020-03-26 06:05:33 +00:00
depends on GRUB_IMAGES || GRUB_EFI_IMAGES
move most of the x86 image generation options to the main file Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 39206
2014-01-07 10:18:55 +00:00
select PACKAGE_kmod-e1000
x86: added support to generate VHDX images Added support to generate dynamic-sized VHDX images for Hyper-V. Compile-tested on x86 and run-tested on Windows 10 21H2 (Hyper-V). Signed-off-by: Oldřich Jedlička <oldium.pro@gmail.com>
2021-01-09 21:23:09 +00:00
config VHDX_IMAGES
bool "Build Hyper-V image files (VHDX)"
depends on TARGET_x86
depends on GRUB_IMAGES || GRUB_EFI_IMAGES
select PACKAGE_kmod-e1000
target: Make TARGET_SERIAL independent of GRUB configuration GRUB_SERIAL is also used for the default serial on the target and not only in grub. When no grub was build it was not available and the build fails. Rename GRUB_SERIAL to TARGET_SERIAL and make it always available on x86 and armsr targets. Fixes: #14063 Fixes: b10768476f9d ("x86,armsr: interpolate GRUB_SERIAL into /etc/inittab") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
2023-11-26 22:04:04 +00:00
config TARGET_SERIAL
string "Serial port device"
loongarch64: new target Add target for Loongson LoongArch64-based boards. LoongArch is a new RISC ISA developed by Loongson. It's a bit like MIPS or RISC-V. LoongArch includes both 32-bit and 64-bit versions (LoongArch32/LoongArch64). Loongson 3A5000 and 3A6000 are the two existing CPUs of LoongArch64 and is used for PC products. It's BIOS supports ACPI and UEFI-only boot. These CPUs supports SMP and SMT. At present only LoongArch64 is supported by linux kernel. Toolchain requirement: binutils >= 2.40 gcc >= 13.1 For details, please check the following links: https://lwn.net/Articles/861951/ https://loongson.github.io/LoongArch-Documentation/README-EN.html Signed-off-by: Weijie Gao <hackpascal@gmail.com>
2024-01-06 19:10:45 +00:00
depends on TARGET_x86 || TARGET_armsr || TARGET_loongarch64
target: Make TARGET_SERIAL independent of GRUB configuration GRUB_SERIAL is also used for the default serial on the target and not only in grub. When no grub was build it was not available and the build fails. Rename GRUB_SERIAL to TARGET_SERIAL and make it always available on x86 and armsr targets. Fixes: #14063 Fixes: b10768476f9d ("x86,armsr: interpolate GRUB_SERIAL into /etc/inittab") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
2023-11-26 22:04:04 +00:00
default "ttyS0"
move most of the x86 image generation options to the main file Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 39206
2014-01-07 10:18:55 +00:00
config TARGET_IMAGES_GZIP
bool "GZip images"
loongarch64: new target Add target for Loongson LoongArch64-based boards. LoongArch is a new RISC ISA developed by Loongson. It's a bit like MIPS or RISC-V. LoongArch includes both 32-bit and 64-bit versions (LoongArch32/LoongArch64). Loongson 3A5000 and 3A6000 are the two existing CPUs of LoongArch64 and is used for PC products. It's BIOS supports ACPI and UEFI-only boot. These CPUs supports SMP and SMT. At present only LoongArch64 is supported by linux kernel. Toolchain requirement: binutils >= 2.40 gcc >= 13.1 For details, please check the following links: https://lwn.net/Articles/861951/ https://loongson.github.io/LoongArch-Documentation/README-EN.html Signed-off-by: Weijie Gao <hackpascal@gmail.com>
2024-01-06 19:10:45 +00:00
depends on TARGET_ROOTFS_EXT4FS || TARGET_x86 || TARGET_armsr || TARGET_malta || TARGET_loongarch64
move most of the x86 image generation options to the main file Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 39206
2014-01-07 10:18:55 +00:00
default y
move menuconfig options into separate files Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 38895
2013-11-22 14:30:40 +00:00
comment "Image Options"
source "target/linux/*/image/Config.in"
build: fix for sourcing targets image config installed via feeds Sourcing of image/Config.in will not happen When a target is installed from target/linux/feeds/ Signed-off-by: Prasun Maiti <prasunmaiti87@gmail.com> Acked-by: Petr Štetiar <ynezz@true.cz>
2022-11-16 11:03:33 +00:00
source "target/linux/*/*/image/Config.in"
move menuconfig options into separate files Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 38895
2013-11-22 14:30:40 +00:00
move most of the x86 image generation options to the main file Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 39206
2014-01-07 10:18:55 +00:00
config TARGET_KERNEL_PARTSIZE
build: Config-images: fix unit of partition sizes The code interprets these config values as Mebibytes rather than Megabytes so modify the description accordingly. Signed-off-by: Paul Fertser <fercerpav@gmail.com> [fix commit title prefix] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2021-06-16 14:15:59 +00:00
int "Kernel partition size (in MiB)"
x86: switch image generation to new code 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>
2020-03-20 10:10:55 +00:00
depends on USES_BOOT_PART
apm821xx: sata: boot-part feature integration 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>
2018-12-27 18:12:23 +00:00
default 8 if TARGET_apm821xx_sata
brcm2708: rename target to bcm27xx 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>
2020-02-08 20:58:55 +00:00
default 64 if TARGET_bcm27xx
config: change references from armvirt to armsr armvirt target has been renamed to armsr (Arm SystemReady), so the config defaults need to be changed as well. Signed-off-by: Mathew McBride <matt@traverse.com.au>
2023-06-06 23:22:01 +00:00
default 128 if TARGET_armsr
x86: bump default kernel partition size to 16M 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>
2016-11-09 11:17:22 +00:00
default 16
move most of the x86 image generation options to the main file Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 39206
2014-01-07 10:18:55 +00:00
move menuconfig options into separate files Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 38895
2013-11-22 14:30:40 +00:00
config TARGET_ROOTFS_PARTSIZE
build: Config-images: fix unit of partition sizes The code interprets these config values as Mebibytes rather than Megabytes so modify the description accordingly. Signed-off-by: Paul Fertser <fercerpav@gmail.com> [fix commit title prefix] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2021-06-16 14:15:59 +00:00
int "Root filesystem partition size (in MiB)"
uml: make use of 'rootfs-part' feature Use 'rootfs-part' feature instead of referencing the TARGET_uml in Config-images.in. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
2022-01-22 00:26:52 +00:00
depends on USES_ROOTFS_PART || TARGET_ROOTFS_EXT4FS
loongarch64: new target Add target for Loongson LoongArch64-based boards. LoongArch is a new RISC ISA developed by Loongson. It's a bit like MIPS or RISC-V. LoongArch includes both 32-bit and 64-bit versions (LoongArch32/LoongArch64). Loongson 3A5000 and 3A6000 are the two existing CPUs of LoongArch64 and is used for PC products. It's BIOS supports ACPI and UEFI-only boot. These CPUs supports SMP and SMT. At present only LoongArch64 is supported by linux kernel. Toolchain requirement: binutils >= 2.40 gcc >= 13.1 For details, please check the following links: https://lwn.net/Articles/861951/ https://loongson.github.io/LoongArch-Documentation/README-EN.html Signed-off-by: Weijie Gao <hackpascal@gmail.com>
2024-01-06 19:10:45 +00:00
default 232 if TARGET_loongarch64
mediatek: increase size of the sdcard image to 512 MiB Increasing the size of the rootfs_data filesystem has become a ever repeating discussion and seems to be the most important thing for users of the MediaTek-based BananaPi boards. Using the whole remaining size of a microSD or the eMMC for rootfs_data doesn't make sense for many reasons, but neither does the current default of 104 MiB for the 'rootfs' partition size. Increase the 'rootfs' partition size to 448 MiB which will result in the sdcard image being exactly 512 MiB. Finding a microSD card smaller than 512 MiB and still working could anyway be difficult in 2024. That will allow users to install even bloatware written in Go or other space-hungry languages while still leaving most of the space unallocated for additional partitions or volumes to be used for persistent user data. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
2024-04-30 21:21:16 +00:00
default 448 if TARGET_mediatek
build: set TARGET_ROOTFS_PARTSIZE to make combined image fit in 128MB 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>
2019-09-21 11:21:36 +00:00
default 104
move menuconfig options into separate files Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 38895
2013-11-22 14:30:40 +00:00
help
Kconfig: Various typo/grammar/line-length fixes in Config*.in files 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
2014-09-13 20:27:25 +00:00
Select the root filesystem partition size.
move menuconfig options into separate files Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 38895
2013-11-22 14:30:40 +00:00
move most of the x86 image generation options to the main file Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 39206
2014-01-07 10:18:55 +00:00
config TARGET_ROOTFS_PARTNAME
string "Root partition on target device"
x86: generate EFI platform bootable images 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>
2020-03-26 06:05:33 +00:00
depends on GRUB_IMAGES || GRUB_EFI_IMAGES
move most of the x86 image generation options to the main file Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 39206
2014-01-07 10:18:55 +00:00
help
config: use PARTUUID by default on x86_64 Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 43086
2014-10-27 14:35:39 +00:00
Override the root partition on the final device. If left empty,
it will be mounted by PARTUUID which makes the kernel find the
appropriate disk automatically.
move most of the x86 image generation options to the main file Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 39206
2014-01-07 10:18:55 +00:00
base-files: add option to make /var persistent In OpenWrt, /var is symlinked to /tmp by default. This is done to reduce the amount of writes to the flash chip, which often have not the greatest durability. As a result, things like DHCP or UPnP lease files, are not persistent across reboots. Since OpenWrt can run on devices with more durable storage, it makes sense to have an option for a persistent /var. Add an option to make /var persistent. When enabled, /var will no longer be symlinked to /tmp, but /var/run will be symlink to /tmp/run, as it should contains only files that should not be kept during reboot. The option is off by default, to maintain the current behaviour. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
2019-02-25 13:05:07 +00:00
config TARGET_ROOTFS_PERSIST_VAR
bool "Make /var persistent"
help
Do not symlink /var to /tmp, so that its content will persist
across reboots. When enabled, /var/run will still be linked
to /tmp/run.
move menuconfig options into separate files Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 38895
2013-11-22 14:30:40 +00:00
endmenu