aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* ipq806x: remove skeleton definitionAnsuel Smith2020-03-031-4/+7
| | | | | | This was already deprecated. With kernel 5.4 it has been removed. Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
* ipq806x: copy files to kernel 5.4Ansuel Smith2020-03-0374-0/+16474
| | | | | | Copy files to kernel 5.4 to start porting. Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
* kirkwood: switch kernel version to 5.4Pawel Dembicki2020-03-031-3/+1
| | | | | | | | | | | | | 5.4 support is ready and tested. Compile tested: all target devices Run tested: pogoplug v4, nsa310b and two unofficial supported devices Tested-by: Sungbo Eo <mans0n@gorani.run> Tested-by: Alberto Bursi <alberto.bursi@outlook.it> [pogoplug v4 and nsa310b] Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com> [fixed the switch, removed maintainer variable] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* kirkwood: fix switch dts node in EA4500 and EA3500Pawel Dembicki2020-03-032-77/+22
| | | | | | | | | | | | Changes made in switch nodes in d42c9ce commit causes problem with correct mvsw61xx detection. This commit undo that changes. mvsw61xx is platform driver, so it need to be in main root of dts. Fixes: d42c9ce326aa ("kirkwood: add kernel 4.19 support") Tested-by: Marcin Fedan <mfedan@gmail.com> [EA4500] Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* kirkwood: initial refresh of 5.4 patchesPawel Dembicki2020-03-033-70/+21
| | | | | | | | | | Refreshed all patches. Changed: 105-ea4500.patch-> Upstream DSA driver was updated. Patch was fixed 202-linksys-find-active-root.patch -> Upstream driver was moved. Patch was fixed Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* kirkwood: initial refresh 5.4 configPawel Dembicki2020-03-031-16/+38
| | | | | | Refreshed kernel config with updated NAND config. Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* kirkwood: copy files and config from 4.19 to 5.4Pawel Dembicki2020-03-0317-0/+1721
| | | | | | | This commit is simple copy config, files and patches from 4.19 to 5.4 kernel. No changes was done. Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* mediatek: update uci-defaults for renamed smp packet steering optionAlan Swanson2020-03-031-4/+1
| | | | | | | | Leave as enabled by default for mediatek. Also remove obsolete settings from when packet steering was moved from netifd to a simplified hotplug script. Signed-off-by: Alan Swanson <reiver@improbability.net>
* netifd: rename 20-smp-tune to 20-smp-packet-steeringAlan Swanson2020-03-031-0/+0
| | | | | | | Rename the script to be more obvious that this is for packet steering only. Signed-off-by: Alan Swanson <reiver@improbability.net>
* netifd: change RPS/XPS handling to all CPUs and disable by defaultAlan Swanson2020-03-031-9/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The current implementation is significantly lowering lantiq performace [1][2] by using RPS with non-irq CPUs and XPS with alternating CPUs. The previous netifd implementation (by default but could be configured) simply used all CPUs and this patch essentially reverts to this behaviour. The only document suggesting using non-interrupt CPUs is Red Hat [3] where if the network interrupt rate is extremely high excluding the CPU that handles network interrupts *may* also improve performance. The original packet steering patches [4] advise that optimal settings for the CPU mask seems to depend on architectures and cache hierarcy so one size does not fit all. It also advises that the overhead in processing for a lightly loaded server can cause performance degradation. Ideally, proper IRQ balancing is a better option with the irqbalance daemon or manually. The kernel does not enable packet steering by default, so also disable in OpenWRT by default. (Though mvebu with its hardware scheduling issues [5] might want to enable packet steering by default.) Change undocumented "default_ps" parameter to clearer "packet_steering" parameter. The old parameter was only ever set in target/linux/mediatek/base-files/etc/uci-defaults/99-net-ps and matched the default. [1] https://forum.openwrt.org/t/18-06-4-speed-fix-for-bt-homehub-5a [2] https://openwrt.ebilan.co.uk/viewtopic.php?f=7&t=1105 [3] https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/performance_tuning_guide/network-rps [4] https://marc.info/?l=linux-netdev&m=125792239522685&w=2 [5] https://git.openwrt.org/?p=openwrt/openwrt.git;a=commitdiff;h=2e1f6f1682d3974d8ea52310e460f1bbe470390f Fixes: #1852 Fixes: #2573 Signed-off-by: Alan Swanson <reiver@improbability.net>
* ramips: mt7530: more detailed output for unexpected etag_ctrlYousong Zhou2020-03-031-1/+2
| | | | Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com>
* ramips: mt7530: remove redundant global attrs for port mirroringYousong Zhou2020-03-031-88/+0
| | | | | | | | | | | | | | | | | | | | Global attributes enable_mirror_tx/enable_mirror_rx depend on runtime value of another global attribute mirror_source_port which just resides in the memory The same functionality can be achieved by directly setting port attribute of the same names. E.g. the following two groups of commands achieve the same thing swconfig dev switch0 set mirror_source_port 3 swconfig dev switch0 set enable_mirror_tx 1 swconfig dev switch0 set mirror_source_port 4 swconfig dev switch0 set enable_mirror_tx 1 swconfig dev switch0 port 3 set enable_mirror_tx 1 swconfig dev switch0 port 4 set enable_mirror_tx 1 Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com>
* bcm53xx: fix ASUS firmwares to use vendor formatRafał Miłecki2020-03-021-6/+13
| | | | | | | | Image building process was missing "asus-trx" step which resulted in raw TRX files (without ASUS footer with device id). Fixes: 0b9de8daa70e ("bcm53xx: add profiles for all other (SoftMAC) devices") Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* kernel: iio: fix st-accel dependencies properlyPetr Štetiar2020-03-021-2/+2
| | | | | | Add missing register map access SPI/I2C modules. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* build: simplify gnu-getopt searchKevin Darbyshire-Bryant2020-03-021-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | getopt is the only command where /usr/local/bin is specified explicitly. All other commands are assumed to exist in the PATH in one form or another. Remove this exception and require gnugetopt/getopt to be in the user's PATH. In the case of macos Homebrew, getopt is 'keg only' hence not linked into /usr/local/bin whilst other commands are linked and likely found by virtue of /usr/local/bin being in PATH. Since 2019 Homebrew is very reluctant to install links that have potential to override default OS behaviour, eg: following instructions on our current 'how to build on macos' wiki page: $ brew ln gnu-getopt --force Warning: Refusing to link macOS-provided software: gnu-getopt If you need to have gnu-getopt first in your PATH run: echo 'export PATH="/usr/local/opt/gnu-getopt/bin:$PATH"' >> ~/.zshrc A better option for macos is to link getopt as 'gnugetopt' in /usr/local/bin, thus the build system will find 'gnugetopt' but other applications looking for just 'getopt' will find the original macos binary. Ultimately it makes sense that 'GNU' dependencies are placed in /usr/local/bin and /usr/local/bin is included in the user's PATH. Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* kernel: x86_64: drop CALGARY IOMMU on 5.4Kevin Darbyshire-Bryant2020-03-021-2/+2
| | | | | | It's snuck back in on kernel 5.4 configs, so drop it there too. Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* kernel: iio: fix st-accel missing dependencyPetr Štetiar2020-03-021-1/+1
| | | | | | | | | | Fixes following build error on mpc85xx/p2020: Package kmod-iio-st_accel is missing dependencies for the following libraries: regmap-core.ko Fixes: 2d8f4c4fbd46 ("kernel: iio: add st-accel driver modules") Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ramips: mt7620: disable images for Netgear 2700Petr Štetiar2020-03-021-0/+1
| | | | | | Because openwrt-ramips-mt7620-netgear_ex2700-squashfs-factory.bin is too big. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ar71xx: add missing LED migration for Archer C7David Bauer2020-03-011-0/+3
| | | | | | | | | | | | When changing the LED names for the Archer C7 to represent the correct color, a migration for existing UCI entries was not created. Add a migration to keep existing LED configurations working. Fixes commit c79c001b593b ("ar71xx: Archer C7 v1 LED names and RFKILL fixes") Signed-off-by: David Bauer <mail@david-bauer.net>
* x86: add preinit hook for bootloader upgradeTomasz Maciej Nowak2020-03-012-1/+21
| | | | | | | | | | | | | | | | This commit fills the void for current OpenWrt installations which will be still on old bootloader version even after "x86: add bootloader upgrade on sysupgrade", since it performs bootloader upgrade only on sysupgrade. To keep all OpenWrt deploynents on the same GRUB version, add preinit hook, which will perform upgrade of the bootloader on first boot after sysupgrade. It's temporary solution and should be deleted, when the first release including this hook will no longer be supported by OpenWrt team. We can assume that all installations should be on current bootolader version and from there sysupgrade routine will be sufficient. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* x86: add bootloader upgrade on sysupgradeTomasz Maciej Nowak2020-03-013-3/+33
| | | | | | | | | | | | | | Currently bootloader always stays on the same version as when first written to boot medium (not true if partition layout changed, which will trigger sysupgrade process to write full disk image). That creates inconveniences as it always stays with same features or/and bugs. Users wishing to add support to additional modules or new version, would need to write the whole image, potentially destroying previous system configuration. To fix these, this commit adds additional routine to sysupgrade which upgrades unconditionally the bootloader to the latest state provided by OpenWrt. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* x86: image: cleanup before creating imageTomasz Maciej Nowak2020-03-011-0/+2
| | | | | | | | | There can be some leftovers from other image recipes, if the same directory names are used and multiply image types are selected. Therefore remove directories used in the recipe, before contents for the image are prepared. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* kernel: iio: add fxos8700 driver supportTim Harvey2020-03-011-0/+50
| | | | | | | | Adds various kernel modules for Freescale FXOS8700 3-axis accelerometer. Signed-off-by: Tim Harvey <tharvey@gateworks.com> [added missing commit description] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* kernel: iio: add st-accel driver modulesTim Harvey2020-03-011-0/+54
| | | | | | | | Adds kernel modules for various STMicroelectronics accelerometers. Signed-off-by: Tim Harvey <tharvey@gateworks.com> [added missing commit description] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* imx6: 5.4: dts: backport lsm9ds1 imu support for GW553xTim Harvey2020-03-011-0/+73
| | | | | | | | | Add one node for the accel/gyro i2c device and another for the separate magnetometer device in the lsm9ds1. Signed-off-by: Tim Harvey <tharvey@gateworks.com> [commit subject/description tweaks, kernel version in patch filename] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* kernel: 5.4: backport fxos8700 accel support from 5.5Tim Harvey2020-03-011-0/+912
| | | | | | | | | | | | Backport kernel module from 5.5 for FXOS8700CQ, which is a small, low-power, 3-axis linear accelerometer and 3-axis magnetometer combined into a single package. The device features a selectable I2C or point-to-point SPI serial interface with 14-bit accelerometer and 16-bit magnetometer ADC resolution along with smart-embedded functions. Signed-off-by: Tim Harvey <tharvey@gateworks.com> [added commit description] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* kernel: can: add MCP251x CAN controller module supportTim Harvey2020-03-011-0/+17
| | | | | | | | Adds kernel module for Microchip MCP251x SPI CAN controller. Signed-off-by: Tim Harvey <tharvey@gateworks.com> [added missing commit description] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* mkrasimage: fix segmentation faultMichael T Farnworth2020-03-011-9/+10
| | | | | | | | | | | | | Code was attempting to determine the size of the file before it was actually known and allocating insufficient memory space. Images above a certain size caused a segmentation fault. Moving the calloc() ensured ensured that large images didn't result in a buffer overflow on memcpy(). Signed-off-by: Michael T Farnworth <michael@turf.org> [fixed name in From to match one in SoB] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* tools/pkgconf: Run pkg-config wrapper through shellcheckRosen Penev2020-03-011-1/+4
| | | | | | | | Mainly quoting fixes. Separated parameters by \ for easier readability. Signed-off-by: Rosen Penev <rosenp@gmail.com>
* tools/pkg-config: Replace with pkgconfRosen Penev2020-03-014-16/+46
| | | | | | | | | | | | | | | | | | | | | | pkgconf is a newer, actively maintained implementation of pkg-config that supports more aspects of the pkg-config file specification and provides a library interface that applications can use to incorporate intelligent handling of pkg-config files into themselves (such as build file generators, IDEs, and compilers). Through its pkg-config compatibility interface (activated when it is run as "pkg-config"), it also can completely replace the original implementation. It is also lighterweight and does not require glib2, as pkg-config does. On other distros, pkgconf is symlinked to pkg-config. For simplicity here, it is renamed to pkg-config.real, as in the original package. Initial results have been positive. As before, pkgconf works as long as the pkg-config files point to the proper paths. Signed-off-by: Rosen Penev <rosenp@gmail.com> [backported upstream fix for Meson] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* uboot-mvebu: point to UBOOT_CONFIG when setting optionsTomasz Maciej Nowak2020-03-011-4/+4
| | | | | | | | | The BUILD_VARIANT might differ from UBOOT_CONFIG, so point to a file we are actually changing. Being here let's call 'Build/Configure/U-Boot' definition, instead of definig the same command. This'll be more future proof, if U-Boot configuration procedure will change. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* mvebu: uDPU: drop patch compiling dtbTomasz Maciej Nowak2020-03-012-11/+1
| | | | | | | | | If device recipe has specified DEVICE_DTS variable, the dtb is built anyway by OpenWrt buildroot image rules. Drop the patch and adjust the location of compiled dtb. Cc: Scott Roberts <ttocsr@gmail.com> Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* mvebu: image: rework uDPU-firmware recipeTomasz Maciej Nowak2020-03-011-3/+9
| | | | | | | | | Tar has ability to change current dir, so use that instead additional command invocation. Also being here, change tar arguments to make final archive reproducible. Cc: Scott Roberts <ttocsr@gmail.com> Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* mvebu: uDPU: clean package selectionTomasz Maciej Nowak2020-03-011-3/+1
| | | | | | | | | This device receipe selects bunch of packages which some are re-defined, unnecessary or irrelevant. Clean them up, so only basic functionality persist. Cc: Scott Roberts <ttocsr@gmail.com> Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* mvebu: image: keep global DTS_DIR intactTomasz Maciej Nowak2020-03-011-1/+2
| | | | | | | | Don't rewrite global DTS_DIR, instead, use proper variable for specifying devices dts directory. For consistency, also specify the variable in default profile, as suggested by Adrian Schmutzler. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* tools: Fix "lib" symlink created inside $(STAGING_DIR_HOST)/libJeffery To2020-03-011-1/+1
| | | | | | | | | | | | | | | | | | | Currently, if "make tools/install" is called after tools have already been installed, a symbolic link named "lib" will be created inside $(STAGING_DIR_HOST)/lib, pointing to "lib" (i.e. itself). During tools/prepare, a "lib64" symlink is created inside $(STAGING_DIR_HOST) that points to "lib" (also inside $(STAGING_DIR_HOST)). If tools/prepare is called and the "lib64" symlink already exists, then ln will treat it as a directory and instead create a symlink named "lib" inside of that directory. This adds the -n option for ln so that $(STAGING_DIR_HOST)/lib64 is always treated as a normal file (the link name), not as a directory. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
* build: Fix directory symlinks not removed when cleaning STAGING_DIRJeffery To2020-03-011-1/+1
| | | | | | | | | | | | | | | | | | Currently, a symbolic link whose target is a directory will not be removed when cleaning packages from STAGING_DIR. In the first cleaning pass in scripts/clean-package.sh, the -f test for a directory symlink returns false (because the link target is a directory) and so the symlink is not removed. In the second pass, the -d test returns true for a directory symlink, but the symlink is not removed by rmdir because rmdir only removes (real) directories. This updates clean-package.sh to remove all non-directories (including symbolic links) in the first pass. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
* build: Remove STAGING_DIR_HOST references for InstallDev/UninstallDevJeffery To2020-03-011-3/+3
| | | | | | | | | | | | | Build/InstallDev no longer places a file list in $(STAGING_DIR_HOST)/packages; this change removes the creation of $(STAGING_DIR_HOST)/packages and the attempted removal of a STAGING_DIR_HOST file list during package clean. This also changes the host directory passed to Build/UninstallDev from $(STAGING_DIR_HOST) to $(STAGING_DIR)/host, to match the directory passed to Build/InstallDev. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
* base-files: Add /etc/shinit for non-login shell initJeffery To2020-03-014-20/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Because /etc/profile (and ~/.profile) are read by login shells only, aliases and functions defined there are not available to non-login shells, e.g. when using screen or tmux. If the ENV environment variable exists (exported by /etc/profile or ~/.profile) and references an existing file, then all interactive shells (login or non-login) will read that file as well. This sets the ENV environment variable in /etc/profile, pointing to /etc/shinit. This also adds /etc/shinit, which: * Contains alias and function definitions originally in /etc/profile * Sources /etc/mkshrc if the user is using mksh (also originally in /etc/profile), as /etc/mkshrc is meant for all interactive shells * Sources ~/.mkshrc if the user is using mksh, to compensate for the fact that mksh will not read ~/.mkshrc if ENV is set * Sources ~/.shinit if the user is not using mksh This also removes the shebang from /etc/profile, as the file is sourced, not executed. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
* ppp: activate PIE ASLR by defaultPetr Štetiar2020-03-011-0/+1
| | | | | | | | | | | | | | This activates PIE ASLR support by default when the regular option is selected. Size increase on imx6: 112681 ppp_2.4.8-2_arm_cortex-a9_neon.ipk 121879 ppp_2.4.8-2_arm_cortex-a9_neon.ipk = 9198 diff Acked-by: Alexander Couzens <lynxis@fe80.eu> Signed-off-by: Petr Štetiar <ynezz@true.cz>
* libpcap: activate PIE ASLR by defaultStijn Tintel2020-03-011-0/+1
| | | | | | | | | | | This activates PIE ASLR support by default when the regular option is selected. This is required to enable PIE ASLR support by default in ppp, as it fails to build without it, on x86/64. The .so file size stays identical. Suggested-by: Felix Fietkau <nbd@nbd.name> Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* ar71xx: correct AVM FRITZ Repeater 450E WPS button flagDavid Bauer2020-03-011-1/+1
| | | | | | | | | The AVM FRITZ!WLAN Repeater 450E's WPS button is not active low. Correct the active low flag to avoid unintenional activation of failsafe mode on boot. Signed-off-by: David Bauer <mail@david-bauer.net>
* linux-5.4: backport ARM symbol export fixÁlvaro Fernández Rojas2020-03-011-0/+60
| | | | | | | Fixes the following warning for ARM targets: WARNING: "return_address" [vmlinux] is a static EXPORT_SYMBOL_GPL Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* linux-5.4: backport modpost upstream patchesÁlvaro Fernández Rojas2020-03-014-11/+121
| | | | | | | | | Fixes modpost Segmentation Fault with bcm2708 and bcm2709: MODPOST vmlinux.o Segmentation fault make[6]: *** [scripts/Makefile.modpost:66: __modpost] Error 139 Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm27xx: bcm2708: refresh linux 5.4 configÁlvaro Fernández Rojas2020-03-011-18/+30
| | | | | | I missed this when adding linux 5.4 support Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* mpc85xx: disable kernel uImage generationDavid Bauer2020-03-012-31/+42
| | | | | | | | | | The previous workaround for the unsupported mkimage xz compression leads to the TP-Link TL-WDR4900s simpleImage bootwrapper being gzip compressed, which does not fit the kernel partition. Removing the uImage gerneration works around this problem. Signed-off-by: David Bauer <mail@david-bauer.net>
* treewide: move commonly disabled symbols to generic configDavid Bauer2020-03-019-22/+6
| | | | | | | Move new commonly disabled kernel 5.4 symbols to the generic kernel configuration. Signed-off-by: David Bauer <mail@david-bauer.net>
* mpc85xx: add missing kernel symbolsDavid Bauer2020-03-013-0/+6
| | | | | | | These symbols were previously not set. Define their state to avoid potentially breaking builds. Signed-off-by: David Bauer <mail@david-bauer.net>
* build: add xargs as prerequisiteKevin Darbyshire-Bryant2020-02-291-0/+5
| | | | | | | | | | | | | Build system needs an 'xargs' that supports '-r' which darwin doesn't. Homebrew installs a 'gxargs' with the findutils package so look for 'gxargs' as well as 'xargs' This is a bit of a 'fun' corner case anyway. xargs is only required by the build if 'CONFIG_AUTOREMOVE' is set and after the build system has built 'tools/findutils' we have a fully working xargs for host anyway. Until that time we have to rely on the host's xargs implementation. Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* apm821xx: remove gpio-interrupt cruftChristian Lamparter2020-02-291-6/+0
| | | | | | | | | | | This hunk became obsolete the moment when our gpio-button-hotplug learned how to deal with interrupt-supported gpio buttons. The gpio driver never supported interrupt handling, so these properties never served any use (outside of a enhanced ppc4xx-gpio driver that was dropped). Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-30 19:48:05 +0000