aboutsummaryrefslogtreecommitdiffstats
path: root/target
Commit message (Collapse)AuthorAgeFilesLines
...
* mxs: bump to use 4.14 by defaultZoltan HERPAI2018-02-201-1/+1
| | | | Signed-off-by: Zoltan HERPAI <wigyori@uid0.hu>
* mxs: add support for 4.14Zoltan HERPAI2018-02-202-0/+370
| | | | Signed-off-by: Zoltan HERPAI <wigyori@uid0.hu>
* kernel: ar83xx: remove stray leading spaceJohn Crispin2018-02-201-3/+3
| | | | Signed-off-by: John Crispin <john@phrozen.org>
* kernel: ar83xx: add support to configure per port VLAN priorityTan Hong Hui2018-02-203-0/+55
| | | | | | | | | Add support to allow for per switch port VLAN priority (PCP) bits for the ar8327/8337 chip using the swconfig utility. Tested on Netgear R7800 Signed-off-by: Tan Hong Hui <hhtan72@yahoo.com>
* kernel: backport pcie enumeration fix to kernel 4.9Koen Vandeputte2018-02-201-0/+62
| | | | | | | This issue is also present in kernel 4.9 starting from 4.9.71 Adapted the patch, as the fixed function is in another location here. Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* Revert "brcm2708: fix sdcard image"Stijn Tintel2018-02-191-2/+2
| | | | | | | | | | | This reverts commit 6c2e1ff80f52b939405fe0c14577c584602ae432. GNU gzip does not fail when the image filename already contains the .gz extension, this is a problem specific to pigz. Revert the commit, as we now gzip the image twice. Reported-by: Martin Schleier <drahemmaps@gmx.net> Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* kernel: backport patches simplifying mtd_device_parse_register codeRafał Miłecki2018-02-197-3/+335
| | | | | | These 2 patches were recently queued for 4.17. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* kernel: order mtd backported patches by kernel releaseRafał Miłecki2018-02-194-0/+0
| | | | Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* imx6: remove support for 4.9Tim Harvey2018-02-198-1242/+0
| | | | | Signed-off-by: Tim Harvey <tharvey@gateworks.com> Tested-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* imx6: switch to Linux 4.14Tim Harvey2018-02-191-1/+1
| | | | | Signed-off-by: Tim Harvey <tharvey@gateworks.com> Tested-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* imx6: add support for Linux 4.14Tim Harvey2018-02-193-0/+549
| | | | | Signed-off-by: Tim Harvey <tharvey@gateworks.com> Tested-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: backport dwc pci enumeration fixTim Harvey2018-02-191-0/+62
| | | | | | | Backport of: http://patchwork.ozlabs.org/patch/860701/ Signed-off-by: Tim Harvey <tharvey@gateworks.com> Tested-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: add missing symbols for v4.14John Crispin2018-02-191-0/+2
| | | | Signed-off-by: John Crispin <john@phrozen.org>
* brcm2708: Fix compile after adding kernel 4.9.82Hauke Mehrtens2018-02-181-0/+8
| | | | | Fixes: f621b539512e ("kernel: bump 4.9 to 4.9.82") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* x86: Use kernel 4.14 by defaultHauke Mehrtens2018-02-181-1/+1
| | | | | | | | Support for kernel 4.14 was added 2 months ago, make it now the default kernel to use for the x86 target. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> Tested-by: Stijn Segers <francesco.borromini@inventati.org>
* kernel: add missing config symbolsStijn Tintel2018-02-181-0/+2
| | | | | | | | They were introduced for arm64 in 4.14.20. Fixes: 88ba41453dbc ("kernel: bump 4.14 to 4.14.20") Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* kernel: add missing symbolJohn Crispin2018-02-181-0/+1
| | | | | | this caused v4.14.20 based builds so fail on aarch64 Signed-off-by: John Crispin <john@phrozen.org>
* kernel: bump 4.9 to 4.9.82Stijn Tintel2018-02-1826-324/+84
| | | | | | | | | | | | | | | | | | | | | | Refresh patches. Remove upstreamed patches: - ar7/002-MIPS-AR7-ensure-the-port-type-s-FCR-value-is-used.patch - backport/040-crypto-fix-typo-in-KPP-dependency-of-CRYPTO_ECDH.patch Remove layerscape/819-Revert-dmaengine-dmatest-move-callback-wait-queue-to.patch, it is superseded by upstream commit 297c7cc4b5651b174a62925b6c961085f04979fd. Remove pending/650-pppoe_header_pad.patch, it is superseded by upstream commit 1bd21b158e07e0b8c5a2ce832305a0ebfe42c480. Update patches that no longer apply: - ar71xx/004-register_gpio_driver_earlier.patch - hack/204-module_strip.patch - pending/493-ubi-set-ROOT_DEV-to-ubiblock-rootfs-if-unset.patch Fixes CVE-2017-8824. Compile-tested: ar71xx. Runtime-tested: ar71xx. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* kernel: bump 4.14 to 4.14.20Stijn Tintel2018-02-1830-223/+68
| | | | | | | | | | | | | | | | Refresh patches. Remove upstreamed patches: - backport/080-v4.15-0001-arch-define-weak-abort.patch - backport/081-v4.15-0002-kernel-exit.c-export-abort-to-modules.patch Update patch that no longer applies: pending/493-ubi-set-ROOT_DEV-to-ubiblock-rootfs-if-unset.patch Fixes CVE-2017-8824. Compile-tested: octeon, x86/64. Runtime-tested: octeon, x86/64. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* brcm2708: fix sdcard imageStijn Tintel2018-02-171-2/+2
| | | | | | | | | | | | The gzip step in the sdcard image build fails because the image filename already has the gzip extension. This results in an empty image file, to which the metadata is finally appended. Remove the .gz extension from the image filename to fix this. Fixes: e79b096ee175 ("brcm2708: convert to metadata") Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* archs38: add HSDK board to network configure scriptsEvgeniy Didin2018-02-172-1/+4
| | | | | | | | | | | | In the initial patch which adds HSDK board there were no update of network configuration scripts. Without it by default static IP is set for br-lan and there is no access to internet. This patch fixes the issue. Signed-off-by: Evgeniy Didin <Evgeniy.Didin@synopsys.com> CC: Alexey Brodkin <abrodkin@synopsys.com> CC: Hauke Mehrtens <hauke@hauke-m.de> CC: John Crispin <john@phrozen.org>
* sunxi: Add Xunlong Orange Pi Zero PlusHauke Mehrtens2018-02-172-0/+204
| | | | | | | This is based on a patch from armbian: https://github.com/armbian/build/blob/master/patch/kernel/sunxi-next/sunxi-add-orangepi-zero-plus.patch Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* sunxi: Add Realtek PHY driver or ARM64 devicesHauke Mehrtens2018-02-171-0/+1
| | | | | | | The Orange Pi Zero Plus uses a RTL8211E, add the driver for this PHY. This is probably used on more boards with a Allwinner SoC. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* sunxi: add support for NanoPi NEO Plus2 boardAntony Antony2018-02-171-0/+10
| | | | | | | | | | | | | | arm64: allwinner: h5: NanoPi NEO Plus2 DT support Add initial DT for NanoPi NEO Plus2 by FriendlyARM - Allwinner quad core H5 Cortex A53 with an ARM Mali-450MP GPU - 1 GB DDR3 RAM - 8GB eMMC flash (Samsung KLM8G1WEPD-B031) - micro SD card slot - Gigabit Ethernet (external RTL8211E-VB-CG chip) - 802.11 b/g/n WiFi, Bluetooth 4.0 (Ampak AP6212A module) - 2x USB 2.0 host ports & 2x USB via headers Signed-off-by: Antony Antony <antony@phenome.org>
* sunxi: add kernel DT for NanoPi NEO Plus2 boardAntony Antony2018-02-171-0/+224
| | | | | | Linux Kernel upstream commit d73413058 Signed-off-by: Antony Antony <antony@phenome.org>
* ar71xx: fix sysupgrade syntax errorMathias Kresin2018-02-161-1/+1
| | | | | | | Fix syntax error introduced with 188328111b46 ("treewide: move nand_do_upgrade call to platform_do_upgrade"). Signed-off-by: Mathias Kresin <dev@kresin.me>
* treewide: move nand_do_upgrade call to platform_do_upgradeMathias Kresin2018-02-168-75/+69
| | | | | | | | | | Calling nand_do_upgrade() from platform_pre_upgrade() was deprecated with 30f61a34b4cf ("base-files: always use staged sysupgrade"). Update the platform upgrade code to use platform_do_upgrade() for NAND images as well. Signed-off-by: Mathias Kresin <dev@kresin.me>
* treewide: remove obsolete sysupgrade watchdog killMathias Kresin2018-02-1611-111/+0
| | | | | | | | | The watchdog kill command was meant for busybox watchdog. Busybox watchdog was replaced by the procd watchdog mid 2013 with commit df7ce9301a25 ("busybox: disable the watchdog utility by default"), which makes the kill command obsolete since quite some time. Signed-off-by: Mathias Kresin <dev@kresin.me>
* sunxi: switch to kernel 4.14Zoltan HERPAI2018-02-161-1/+1
| | | | Signed-off-by: Zoltan HERPAI <wigyori@uid0.hu>
* kernel: add missing symbolsJohn Crispin2018-02-162-0/+2
| | | | | | These cause mediatek arm to fail full builds Signed-off-by: John Crispin <john@phrozen.org>
* ramips: preliminary support for 4.14Roman Yeryomin2018-02-1577-24/+27451
| | | | | | | | - removed upstreamed patches - 0901-spansion_nand_id_fix.patch is disabled, not clear if it's needed Signed-off-by: Roman Yeryomin <roman@advem.lv> Signed-off-by: John Crispin <john@phrozen.org>
* ramips: fix reporting effective VLAN ID on MT7621 switchesJo-Philipp Wich2018-02-141-2/+21
| | | | | | | | | | | | On MT7621, the REG_ESW_VLAN_VTIM reads are undefined, causing swconfig to always report `vid: 0` in swconfig show output. Since a 4K VLAN table is used on this platform, the VLAN ID always correponds to the actual VLAN table index so provide a specific MT7621 implementation of the get_vid callback which returns the table index as VLAN ID. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* ramips: properly map pvid for vlans with remapped vid on mt7530/762x switchesJo-Philipp Wich2018-02-141-1/+7
| | | | | | | | | | | | | Currently, untagged port primary vlan IDs are set to the VLAN table index, and not the actual VLAN ID, breaking configurations with IDs deviating from the VLAN index. Fix the issue by resolving the per-port pvid property to the target VLAN ID value before committing to the hardware. Fixes FS#991, FS#1147, FS#1341 Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* ramips: don't clobber vlans with remapped vid on mt7530/762x switchesJo-Philipp Wich2018-02-141-36/+53
| | | | | | | | | | | | | Avoid overwriting vlan entries with remapped vid in later iterations of the vlan enumeration loop of mt7530_apply_config(). Fix the problem by refactoring the code to first reset the entire table, then reprogram only vlans with members to prevent overwriting configured vlans with unconfigured ones. Fixes FS#1147, FS#1341 Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* at91: fix image building with CONFIG_TARGET_MULTI_PROFILEJo-Philipp Wich2018-02-142-11/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | The current image build code has a number of race conditions and interface contract violations in the custom image build steps: - Build/install-zImage, solely used by at91, relies on $(PROFILE_SANITIZED) which is not available when building with CONFIG_TARGET_MULTI_PROFILE - Build/at91-sdcard, which may run concurrently, creates scratch files at fixed locations and manipulates target files directly which can lead to file corruption and other unexpected failures Rename the install-zImage macro to at91-install-zImage and move it to the at91 image Makefile since this target is the sole user. Also utilize "$@" as output file name and switch the usage of $(PROFILE_SANITIZED) to $(DEVICE_NAME) in order to fix naming under multi profile builds. Fix the at91-sdcard macro to construct scratch file paths relative to "$@", which is guaranteed to be unique and store the final artifact output in "$@" as well, instead of inside $(BIN_DIR). The generic image build code takes care of moving a build steps "$@" output to the final destination in a concurrency-safe manner. Finally remove the broken install-zImage from the generic image-commands Makefile. Fixes: d7a679a036 ("at91: Install zImage.") Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* mediatek: bump to v4.14John Crispin2018-02-1491-19755/+1482
| | | | | | | This drops support for all the !emmc EVB and adds banannaPi-R2 Also drop mtkhnat until the nftables offoad driver is ready Signed-off-by: John Crispin <john@phrozen.org>
* ipq806x: add support for GL.iNet GL-B1300Dongming Han2018-02-146-1/+339
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds support for GL.iNet GL-B1300 Specification: - SOC: IPQ4028 / QCA Dakota - RAM: 256 MiB - FLASH: 32 MiB - ETH: Qualcomm Atheros QCA8075 Gigabit Switch (2 x LAN, 1 x WAN) - USB: 1 x 3.0 (via Synopsys DesignWare DWC3 controller in the SoC) - WLAN1: Qualcomm Atheros QCA4028 2.4GHz 802.11bgn 2:2x2 - WLAN2: Qualcomm Atheros QCA4028 5GHz 802.11a/n/ac 2:2x2 - INPUT: one reset and one WPS button - LEDS: 3 leds: Power, WIFI(only for 2.4G currently), and one reserved - UART: 1 x UART on PCB (3.3V, TX, RX, GND) - 115200 8N1 Installation: Method 1: - use serial port to stop uboot - uboot command: run lf Method 2: - push down reset button and power on - wait until three leds constantly on then release - upgrade by uboot web at http://192.168.1.1 Note: - the sysupgrade image need to be renamed to lede-gl-b1300.bin in both method. - the sysupgrade image can be automatically downloaded if tftp server at 192.168.1.2 have that file. - the wifi led will be flashing when writing image. Signed-off-by: Dongming Han <handongming@gl-inet.com>
* archs38: add HSDK boardEvgeniy Didin2018-02-143-4/+38
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Synopsys DesignWare HSDK (which stands for ARC HS Development Kit) is the latest and greatest development platform that sports quad-core ARC HS38 in real silicon. Most noticeable features of the board are: * Quad-core ARC HS38 CPU running at 1GHz * 4Gb of DDR * Built-in Vivante GPU (well supported via open source Etnaviv drivers) * Built-in Wi-Fi/Bluetooth module (RedPine RS-9113) And as usual we have: * [micro] SD-card slot * 2 USB 2.0 ports * 1Gbit Ethernet port * Built-in Digilent JTAG probe * Serial port accessible via micro-USB port For more information about HSDK board visit: https://www.synopsys.com/dw/ipdir.php?ds=arc-hs-development-kit Signed-off-by: Evgeniy Didin <Evgeniy.Didin@synopsys.com> CC: Alexey Brodkin <abrodkin@synopsys.com> CC: Hauke Mehrtens <hauke@hauke-m.de> CC: John Crispin <john@phrozen.org>
* archs38: switch to kmod-usb2Evgeniy Didin2018-02-141-1/+1
| | | | | | | | | | | We have managed to get USB 2.0 working good enough on all archs38 platforms so we're ready to switch to much faster USB 2.0. Signed-off-by: Evgeniy Didin <Evgeniy.Didin@synopsys.com> CC: Alexey Brodkin <abrodkin@synopsys.com> CC: Hauke Mehrtens <hauke@hauke-m.de> CC: John Crispin <john@phrozen.org>
* generic: swconfig: reduce lock duration on sysfs filesKevin Darbyshire-Bryant2018-02-141-8/+12
| | | | | | | | sysfs attributes 'port_mask' & 'speed_mask' held locks whilst doing mundane tasks such as sprintf. Refactor code to reduce length of time locks are held unnecessarily. Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* generic: swconfig: add mode led attributeKevin Darbyshire-Bryant2018-02-141-12/+125
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add sysfs 'mode' attribute to swconfig controlled LEDs. swconfig 'link state' LEDs blink in the presence of port traffic. This behaviour becomes more obvious as switches start to support get_port_stats() e.g. commits 0369e358916ef092a1644334f5dd1412051b68a4, 3056d09b4046e0eb0f6de0f3f5432cd9fa86fc51, 4ddbc43cc15c2fa128a2f169964ef7eb508cf2c5, 4d8a66d9346373c2a7fcac5bdae3f662a9dbd9df. This blinking can be confusing/distracting if the switch has other LEDs used to indicate traffic. Provide a 'mode' sysfs attribute that controls the blink on traffic behaviour. mode - either "none" (LED is off) or a space separated list of one or more: link: LED's normal state reflects whether the link is up (has carrier) or not tx: LED blinks on transmitted data rx: LED blinks on receive data Note that 'link' considers any port speed mask that may be applicable. e.g. if an LED is configured to indicate 1Gbit link speed and mode is set to 'link rx tx' but the port is connected at 100Mbit then the LED will not light or blink. A mode of 'tx rx' will blink in the presence of traffic only if the port matches the rate (if configured) This maintains compatibility with existing behaviour. Attribute is 'link tx rx' by default for backwards compatible behaviour. Many thanks to Thibaut Varene for providing a more sensible led_event routine after I had mangled the original, and other coding style hints. Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk> Acked-by: Thibaut VARENE <hacks@slashdirt.org>
* mvebu: Migrate uci config to new PCIe pathHauke Mehrtens2018-02-131-0/+41
| | | | | | | | | | | | | | | | | | | | The name of the PCIe controller node in device tree changed between kernel 4.9 and kernel 4.14. Migrate the configuration when an update from kernel 4.9 to 4.14 or back is done to the new name to make the existing wifi configuration compatible with the new names. This replaces the "pcie-controller" part with "pcie" on all nodes if the file exists in sys fs. This is not done in the uci-defualts, because they are getting executed to late in the boot process. The kernel module gets loaded before the uci-defaults scripts are executed. When the mwlwifi driver gets loaded it will trigger an event via hotplug to detect new devices and as the paths are not in the uci configuration they will be added again. When the migration is done before the script will detect that they are already there. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* mvebu: Add support for kernel 4.14Hauke Mehrtens2018-02-1329-0/+3893
| | | | | | | | | | Add support for kernel 4.14 to the mvebu target. This also replaces the old sfp and phylink patches with new versions from Russell's clearfog-4.13 branch http://git.arm.linux.org.uk/cgit/linux-arm.git/log/?h=clearfog-4.13 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* mvebu: move files to files-4.9 and files-4.4 folderHauke Mehrtens2018-02-134-0/+568
| | | | | | | | This is needed to prevent copying it into kernel 4.14. These device tree files are already integrated into kernel 4.14 and we would like to use the upstream versions only. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: ubifs: create use file system format 4 by defaultHauke Mehrtens2018-02-132-0/+64
| | | | | | | | | | | | | | | | | | | Instead of creating an ubifs file system with format version 5 by default on empty UBI volumes use the older format 4 by default. This will make it possible to mount these file systems also on older kernel versions. When a user wants to do a sysupgrade from kernel 4.14 to kernel 4.9 the old kernel has to read the file system created by the more recent kernel which currently does not work for ubifs. This fixes the problem by creating file systems which are compatible with older kernel versions by default. Kernel 4.14 will still be able to read and write UBI FS file system version 5, it will just not be used when a ubifs partition is created implicitly on an empty UBI volume. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: Add missing config optionsHauke Mehrtens2018-02-131-0/+5
| | | | | | These were found when compiling the new octeontx target. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* brcm63xx: drop root parameter from cmdlineJonas Gorski2018-02-1388-88/+88
| | | | | | | | | | | The root= parameter overrides the automatic rootfs detection by partition name, so drop it. Fixes boot from flash after renumeration changes of partitions due to parser changes. Fixes FS#1350. Fixes: a27d59bb4274 ("brcm63xx: switch to new partition layout specification") Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* ipq806x: switch to full dual-boot for the nbg6817 sysupgrade supportStefan Lippers-Hollmann2018-02-131-3/+23
| | | | | | | | | | | | | | Instead of writing to the currently booted partition set, this implements full dual-boot support for sysupgrade by always writing to the other, currently inactive, partition set and toggling the dualflag after a successful flash. The currently active/ booted partition set is determined by parsing /proc/cmdline for its rootfs parameter (supplied by the DTS), instead of reading from the 0:DUAL_FLAG mtd, in order to prevent (potentially) bricking both partition sets. Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
* ipq806x: request the first free loop device dynamically for the nbg6817 ↵Stefan Lippers-Hollmann2018-02-131-4/+5
| | | | | | | | | | | | sysupgrade Instead of hardcoding /dev/loop0, it's safer to query for the first free loop device and assign that dynamically. While /dev/loop0 is a reasonable assumption immediately following "losetup --detach-all", detaching the mounted overlay is no longer strictly necessary once dual-boot support has been added for the nbg6817. Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
* ipq806x: use absolute the device path in $kernel for the nbg6817 sysupgradeStefan Lippers-Hollmann2018-02-131-4/+4
| | | | | | | Harmonize the variable usage for $kernel and $rootfs to always contain the full device path, instead of just its basename. Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-06 13:07:15 +0000