aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/armvirt
Commit message (Collapse)AuthorAgeFilesLines
* generic: enable CRYPTO_LIB_BLAKE2S[_X86|_ARM]Tomasz Maciej Nowak2022-06-272-0/+4
| | | | | | | | | | | | | This is now built-in, enable so it won't propagate on target configs. Link: https://lkml.org/lkml/2022/1/3/168 Fixes: 79e7a2552e89 ("kernel: bump 5.15 to 5.15.44") Fixes: 0ca93670693b ("kernel: bump 5.10 to 5.10.119") Signed-off-by: Tomasz Maciej Nowak <tmn505@gmail.com> (Link to Kernel's commit taht made it built-in, CRYPTO_LIB_BLAKE2S[_ARM|_X86] as it's selectable, 5.10 backport) Signed-off-by: Christian Lamparter <chunkeey@gmail.com> (cherry picked from commit 539e60539a2fde6531bd179c94bb9c7f8f490f2b)
* kernel: 5.10: consolidate mac80211 crypto optionsSergey Ryazanov2021-12-172-8/+0
| | | | | | | | | | | | | | | | | | | | | | Each of - CRYPTO_AEAD2 - CRYPTO_AEAD - CRYPTO_GF128MUL - CRYPTO_GHASH - CRYPTO_HASH2 - CRYPTO_HASH - CRYPTO_MANAGER2 - CRYPTO_MANAGER - CRYPTO_NULL2 either directly required for mac80211 crypto support, or directly selected by such options. Support for the mac80211 crypto was enabled in the generic config since c7182123b9 ("kernel: make cryptoapi support needed by mac80211 built-in"). So move the above options from the target configs to the generic config to make it clear why do we need them. CC: Felix Fietkau <nbd@nbd.name> Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com>
* kernel: filter out both Clang and LLD versionsSergey Ryazanov2021-12-171-1/+0
| | | | | | | | Both CLANG_VERSION and LLD_VERISON are autogenerated runtime configuration options, so add them to the kernel configuration filter and remove from generic and per-target configs to keep configs clean. Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com>
* armvirt: enable MMIO_CMDLINE_DEVICES for firecracker supportPaul Spooren2021-10-121-0/+1
| | | | | | | | | | | | | This Kernel option allows to run OpenWrt witin a `firecracker` micro VM. Firecracker is a KVM-based tool for superfast booting VMs on x86_64 and aarch64. It makes rootfs available to the guest as a virtio-mmio device and passes its address via the kernel cmdline. A kernel without CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES will not recognize the rootfs virtio-mmio device. Suggested-by: Packet Please <pktpls@systemli.org> Signed-off-by: Paul Spooren <mail@aparcar.org>
* armvirt: remove obsolete Kernel 5.4Paul Spooren2021-10-023-385/+0
| | | | | | | With the upgrade to Kernel 5.10 per default the old version is no longer required to be in tree. Signed-off-by: Paul Spooren <mail@aparcar.org>
* armvirt: switch to Kernel 5.10Paul Spooren2021-10-011-2/+1
| | | | | | | | | | | | Armvirt is a development and testing platform and should therefore use the latest OpenWrt Kernel by default. Tested via qemu. Acked-by: Rosen Penev <rosenp@gmail.com> Acked-by: Yousong Zhou <yszhou4tech@gmail.com> Signed-off-by: Paul Spooren <mail@aparcar.org>
* kernel: move two symbols to the generic kconfigsRui Salvaterra2021-08-292-4/+0
| | | | | | | CONFIG_RCU_{NEED_SEGCBLIST,STALL_COMMON} are set basically everywhere. Move them to the generic kconfigs. And resort the generic kconfigs while at it. Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com>
* treewide: switch the timer frequency to 100 HzRui Salvaterra2021-04-214-8/+0
| | | | | | | | Some targets select HZ=100, others HZ=250. There's no reason to select a higher timer frequency (and 100 Hz are available in every architecture), so change all targets to 100 Hz. Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com>
* armvirt: add 5.10 testing kernelAleksander Jan Bajkowski2021-04-031-0/+1
| | | | | | | Add 5.10 as testing kernel. Builds successfully with CONFIG_ALL_KMODS=y enabled. Signed-off-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl>
* armvirt: refresh 5.10 configAleksander Jan Bajkowski2021-04-033-19/+20
| | | | | | | | | | This was done by executing these commands: $ make kernel_oldconfig CONFIG_TARGET=subtarget $ make kernel_oldconfig CONFIG_TARGET=subtarget_platform Some common symbols have been moved to target config. Signed-off-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl>
* armvirt: copy config files for 5.10Aleksander Jan Bajkowski2021-04-033-0/+391
| | | | | | Copy config and patches for 5.10. Signed-off-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl>
* armvirt: refresh 5.4 configAleksander Jan Bajkowski2021-04-033-203/+14
| | | | | | | | This was done by executing these commands: $ make kernel_oldconfig CONFIG_TARGET=subtarget $ make kernel_oldconfig CONFIG_TARGET=subtarget_platform Signed-off-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl>
* kernel: move some disabled symbols to genericAleksander Jan Bajkowski2021-03-192-11/+0
| | | | | | Move some disabled symbols found in armvirt target to generic. Signed-off-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl>
* treewide: remove execute bit and shebang from board.d filesAdrian Schmutzler2021-03-061-1/+0
| | | | | | | | | | | | | | | | So far, board.d files were having execute bit set and contained a shebang. However, they are just sourced in board_detect, with an apparantly unnecessary check for execute permission beforehand. Replace this check by one for existance and make the board.d files "normal" files, as would be expected in /etc anyway. Note: This removes an apparantly unused '#!/bin/sh /etc/rc.common' in target/linux/bcm47xx/base-files/etc/board.d/01_network Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* target: use SPDX license identifiers on MakefilesAdrian Schmutzler2021-02-102-8/+4
| | | | | | Use SPDX license tags to allow machines to check licenses. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* armvirt: README: rename it from LEDE to OpenWrtJosef Schlehofer2020-12-141-1/+1
| | | | Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com>
* armvirt/64: change it to cortex-a53 instead of genericJosef Schlehofer2020-12-141-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Package architecture aarch64_generic [1] can be used just with three devices. One is NanoPI R2S and then there are two development boards from NXP. Let's change armvirt/64 to Cortex A53 (aarch64_cortex-a53) [2]. It has wider support by multiple devices like NanoPI Neo Plus2/Core2, ESPRESSObin, Pine64, and Raspberry Pi 2&3. While looking at ARMvirt/32 it has set CPU_TYPE and CPU_SUBTYPE to be arm_cortex-a15_neon-vfpv4 [3]. It has support to devices like Linksys EA8500 v1, Linksys EA7500 v1, Netgear D7800, Netgear R7500 and so on. Tested with: qemu-system-aarch64 -m 1024 -smp 2 -cpu cortex-a57 -M virt -nographic \ -kernel openwrt-armvirt-64-Image-initramfs Successfully compiled and booted. Here goes the output: root@OpenWrt:/# uname -a Linux OpenWrt 5.4.82 #0 SMP Sun Dec 13 12:52:10 2020 aarch64 GNU/Linux root@OpenWrt:/# cat /etc/openwrt_release DISTRIB_ID='OpenWrt' DISTRIB_RELEASE='SNAPSHOT' DISTRIB_REVISION='r15207-96fca0f807' DISTRIB_TARGET='armvirt/64' DISTRIB_ARCH='aarch64_cortex-a53' DISTRIB_DESCRIPTION='OpenWrt SNAPSHOT r15207-96fca0f807' DISTRIB_TAINTS='no-all' Also, change BOARDNAME to be the same as it is in armvirt/32. [1] https://openwrt.org/docs/techref/instructionset/aarch64_generic [2] https://openwrt.org/docs/techref/instructionset/aarch64_cortex-a53 [3] https://openwrt.org/docs/techref/instructionset/arm_cortex-a15_neon-vfpv4 Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com>
* kernel: remove support for kernel 4.19Adrian Schmutzler2020-10-303-539/+0
| | | | | | | We use 5.4 on all targets by default, and 4.19 has never been released in a stable version. There is no reason to keep it. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* kernel: move CONFIG_F2FS_CHECK_FS to generic kernel configHauke Mehrtens2020-10-112-2/+0
| | | | Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: Move CONFIG_F2FS_FS_SECURITY to generic kernel configHauke Mehrtens2020-10-112-2/+0
| | | | | | | Move the CONFIG_F2FS_FS_SECURITY kernel configuration option to the generic kernel configuration. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: move F2FS_FS_XATTR and F2FS_STAT_FS symbols to genericDaniel Golle2020-10-092-3/+0
| | | | | | | | Similar to how it was already done for other filesystems' *_FS_XATTR kernel config symbols, also move CONFIG_F2FS_FS_XATTR=y and CONFIG_F2FS_STAT_FS=y to target/linux/generic. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* kernel: clean up XATTR config symbolsPaul Spooren2020-10-091-1/+0
| | | | | | | | | | | | | Extended attributes are required for overlayfs and have hence been long ago enabled for jffs2, but should be enabled unconditionally for all other filesystems which may potentially serve as overlayfs' upper directory. Previously it was inconsistently added in multiple targets. Add symbols to generic kernel config and remove all *_XATTR symbols from target configs. Signed-off-by: Paul Spooren <mail@aparcar.org> [keep things as they are for squashfs, improve commit message] Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* kernel: set WATCHDOG_CORE dependency in kmod-hwmon-sch5627Adrian Schmutzler2020-08-241-1/+0
| | | | | | | | | | | | | | | | | | For many target we have added CONFIG_WATCHDOG_CORE=y to the target config due to the following error: Package kmod-hwmon-sch5627 is missing dependencies for the following libraries: watchdog.ko However, actually the proper way appears to be setting the dependency for the kmod-hwmon-sch5627 package, as the error message demands. Do this in this patch and remove the target config entries added due to this issue. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* kernel: Move CONFIG_IONIC to generic kernel configHauke Mehrtens2020-08-101-1/+0
| | | | | | | It is deactivated everywhere, just set this in the generic config. Acked-by: Yousong Zhou <yszhou4tech@gmail.com> Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* armvirt,x86: fix build breakage of crypto ccp modulePetr Štetiar2020-06-231-0/+1
| | | | | | | | | Upstream in commit f9f8f0c24203 ("crypto: ccp -- don't "select" CONFIG_DMADEVICES") removed dependency on CONFIG_DMADEVICES symbol which leads to build breakage of ccp crypto module, so fix this by adding that symbol back in the kernel config. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* kernel: remove non-existant symbolsAleksander Jan Bajkowski2020-04-132-8/+0
| | | | | | These symbols exist only in older kernels and can be removed. Signed-off-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl>
* kernel: move TEO governor to generic configTomasz Maciej Nowak2020-03-171-1/+0
| | | | | | | | This new symbol popped up in few places. Disable it in generic config. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl> [fixed merge conflict in generic/config-5.4] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* treewide: remove maintainer variable from targetsPetr Štetiar2020-03-161-1/+0
| | | | | | | | | | | | | There is no such role as target maintainer anymore, one should always send corresponding changes for the review and anyone from the commiters is allowed to merge them or eventually use the hand break and NACK them. Lets make it clear, that it is solely a community doing the maintenance tasks. Signed-off-by: Petr Štetiar <ynezz@true.cz> Acked-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> Acked-by: Piotr Dymacz <pepe2k@gmail.com>
* armvirt: Remove kernel 4.14 supportHauke Mehrtens2020-03-123-481/+0
| | | | | | | | | | This target was switched to kernel 4.19 more than 6 months ago in commit f342ffd300da ("treewide: kernel: bump some targets to 4.19") and now with kernel 5.4 support being added it gets harder to support kernel 4.14 in addition to kernel 4.19 and 5.4. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> Acked-by: Yousong Zhou <yszhou4tech@gmail.com>
* armvirt: fix missing watchdog core dependency for hwmon-sch5627Petr Štetiar2020-03-111-0/+1
| | | | | | | | | | | | | | | | Fixes following error uncovered while building armvirt/64 on 5.4: Package kmod-hwmon-sch5627 is missing dependencies for the following libraries: watchdog.ko That dependency was introduced in upstream via 2d8c7ff52c24 ("hwmon/sch56xx: Depend on watchdog for watchdog core functions") in v3.5. The issue emerged in 5.4 because the kconfig symbol CONFIG_WATCHDOG_CORE is now a tristate value. Previously it was a bool. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* armvirt: switch to kernel 5.4Yousong Zhou2020-03-101-1/+1
| | | | Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com>
* armvirt: 5.4: kconfig syncYousong Zhou2020-03-103-25/+78
| | | | | | | "make kernel_menuconfig CONFIG_TARGET=subtarget_platform" first, then move common ones to platform level config Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com>
* armvirt: add config-5.4Yousong Zhou2020-03-103-0/+547
| | | | | | Copied from config-4.19 Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com>
* kernel: remove non-existant symbols from 4.19 configAleksander Jan Bajkowski2020-02-221-3/+0
| | | | | | These symbols only exist in kernel version <= 4.15 Signed-off-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl>
* treewide: Remove self from MAINTAINER entriesFlorian Fainelli2019-12-231-2/+1
| | | | Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
* armvirt: fix overlay support by updating to f2fs/ext4 based overlaysPetr Štetiar2019-06-252-2/+10
| | | | | | | | | | | | | | | | | | Current snapshot images doesn't provide images with usable overlay filesystems: mount_root: no usable overlay filesystem found, using tmpfs overlay So this patch fixes this by updating support to current f2fs/ext4 based overlays and providing squashfs with proper rootfs TARGET_ROOTFS_PARTSIZE size. While at it, I've also added support for optional gzipping of the images, and renamed the output rootfs image filenames to match the more common naming pattern $(IMG_PREFIX)-rootfs-$(FS-TYPE).img. Cc: Yousong Zhou <yszhou4tech@gmail.com> Signed-off-by: Petr Štetiar <ynezz@true.cz>
* armvirt: configure kernel for f2fs and ext4 based overlaysPetr Štetiar2019-06-251-0/+7
| | | | | | | | jffs2/mtdblock overlays are long time gone, and as we switch to the new f2fs/ext4 based overlays, we need to add missing support for loop block device and f2fs to kernel. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* treewide: kernel: bump some targets to 4.19Petr Štetiar2019-06-181-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Lets bump kernel to 4.19 on targets which were run tested or got ACKed so we've enough time to make it ready for next release: armvirt/32 (runtested in qemu) armvirt/64 (runtested in qemu) ath79/generic (runtested on Carambola2) gemini/generic (runtested on DIR-685, DNS-313, SQ201, SL93512R) imx6/generic (runtested on Apalis) ipq40xx/generic (runtested on nbg6617) malta/be64 (runtested in qemu) malta/be (runtested in qemu) malta/le (runtested in qemu) malta/le64 (runtested in qemu) mpc85xx/generic (runtested on TL-WDR4900) mpc85xx/p2020 (runtested on P2020RDB) mvebu/cortexa53 mvebu/cortexa72 mvebu/cortexa10 octeon/generic (runtested on EdgeRouter Lite) sunxi/cortexa53 (build tested only) sunxi/cortexa7 (runtested on Lime2-K) sunxi/cortexa8 (build tested only) tegra/generic x86/64 (runtested in qemu) Acked-by: Zoltan HERPAI <wigyori@uid0.hu> [sunxi] Tested-by: Linus Walleij <linus.walleij@linaro.org> [gemini] Tested-by: Tomasz Maciej Nowak <tomek_n@o2.pl> [mvebu, tegra] Tested-by: Daniel Engberg <daniel.engberg.lists@pyret.net> [octeon] Tested-by: Pawel Dembicki <paweldembicki@gmail.com> [mpc85xx/generic mpc85xx/p2020] Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be> Signed-off-by: Petr Štetiar <ynezz@true.cz>
* armvirt: refresh 4.19 kernel configPetr Štetiar2019-06-183-80/+142
| | | | | | | Refresh kernel configs with 4.19 bits, while at it, add common symbols into the target config. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* armvirt: add kernel configs for 4.19Petr Štetiar2019-06-185-0/+481
| | | | | | | It's just copy of 4.14 and will be refreshed in the upcoming commit, renamed config-default to config-4.14 as well. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* kernel: Remove CONFIG_COMPATHauke Mehrtens2019-05-111-10/+0
| | | | | | | | | | | | | This removes support for executing old 32 bit applications on 64 bit ARM and MIPS kernels. On OpenWrt we normally compile all the user space applications on our own and do not support third party binary only modules especial not 32 bit applications on 64 bit CPUs. This reduces the attack surface on such systems and should also save some memory. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: Activate CONFIG_ARM64_SW_TTBR0_PANHauke Mehrtens2019-05-111-1/+0
| | | | | | | | | | This activates "Emulate Privileged Access Never using TTBR0_EL1 switching" on ARM64. This should prevent the kernel from reading code from user space in kernel context. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* armvirt64: enable qemu drm driversLucian Cristian2019-04-181-0/+4
| | | | | | | adds the qemu video drivers and also fixes the build failure introduced with drm-kms-helper Signed-off-by: Lucian Cristian <lucian.cristian@gmail.com>
* armvirt: 32: enable CONFIG_ARM_LPAEYousong Zhou2019-02-191-2/+10
| | | | | | | | | | | | | | | | | | | | | | This is required for running armvirt_32 on QEMU 3.0 [1], otherwise the kernel will emit the following complaint and virtio-net-pci devices will fail to be initialized [ 1.124214] OF: PCI: host bridge /pcie@10000000 ranges: [ 1.125093] OF: PCI: IO 0x3eff0000..0x3effffff -> 0x00000000 [ 1.125942] OF: PCI: MEM 0x10000000..0x3efeffff -> 0x10000000 [ 1.126403] OF: PCI: MEM 0x8000000000..0xffffffffff -> 0x8000000000 [ 1.127748] pci-host-generic 4010000000.pcie: can't claim ECAM area [mem 0x10000000-0x1fffffff]: address conflict with /pcie@10000000 [mem 0x10000000-0x3efeffff] [ 1.129752] pci-host-generic: probe of 4010000000.pcie failed with error -16 Running QEMU with "-M virt,highmem=off" is an option, but "highmem" was only introduced as a default on flag since QEMU 2.5.0 and QEMU will fail and quit on encounter of unknown flags [1] Armv7 guest fails to boot with qemu-3.0.0-1, https://bugzilla.redhat.com/show_bug.cgi?id=1633328#c5 Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com>
* armvirt: 32: refresh kernel configYousong Zhou2019-02-191-2/+24
| | | | | | | | | | | | | | | | | | | | | | | The diff was genereated by running the following command without actually changing any kernel config options make kernel_menuconfig CONFIG_TARGET=subtarget Here are some initial findings on the change - CONFIG_ARCH_OPTIONAL_KERNEL_RWX is now arch default - CONFIG_ARM_GIC_V3_ITS is selected by CONFIG_ARCH_VIRT - CONFIG_CPU_SPECTRE is select by CONFIG_CPU_V7 - CONFIG_TIMER_OF is now a arch default - CONFIG_TIMER_PROBE is select by CONFIG_TIMER_OF The following options should probably be moved to generic config - CONFIG_MIGRATION is a default on option - CONFIG_TREE_SRCU is a default on option for !PREEMPT && SMP system - CONFIG_RCU_NEED_SEGCBLIST Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com>
* kernel: bump 4.14 to 4.14.77Koen Vandeputte2018-10-191-0/+1
| | | | | | | | | | | | | | | Refreshed all patches. Altered patches: - 666-Add-support-for-MAP-E-FMRs-mesh-mode.patch New symbol for arm targets: - HARDEN_BRANCH_PREDICTOR Compile-tested on: ar71xx, cns3xxx, imx6 Runtime-tested on: ar71xx, cns3xxx, imx6 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: enable memory compactionFelix Fietkau2018-10-091-0/+1
| | | | | | | | | | | Compaction is the only memory management component to form high order (larger physically contiguous) memory blocks reliably. The page allocator relies on compaction heavily and the lack of the feature can lead to unexpected OOM killer invocations for high order memory requests. You shouldn't disable this option unless there really is a strong reason for it. Signed-off-by: Felix Fietkau <nbd@nbd.name> Signed-off-by: Michal Hrusecky <michal.hrusecky@nic.cz>
* armvirt: remove linux 4.9 supportFelix Fietkau2018-09-291-180/+0
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* kernel: add missing ARM64_SSBD symbolStijn Tintel2018-07-311-0/+1
| | | | | | | | | In 4.14.57, a new symbol for Spectre v4 mitigation was introduced for ARM64. Add this symbol to all ARM64 targets using kernel 4.14. This mitigates CVE-2018-3639 on ARM64. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* arm64: enable harden branch predictorMathias Kresin2018-04-271-0/+2
| | | | | | Enable the harden branch predictor for arm64 as it is recommend. Signed-off-by: Mathias Kresin <dev@kresin.me>