aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/lantiq
Commit message (Collapse)AuthorAgeFilesLines
...
* lantiq: use wpad-basic for boards with enough storageJohann Neuhauser2019-07-301-2/+2
| | | | | | | | | This commit selects wpad-basic for the FRITZ!Box 7312 and 7412 as wpad-mini is only selected on boards with small flash. Signed-off-by: Johann Neuhauser <johann@it-neuhauser.de> [add short description] Signed-off-by: David Bauer <mail@david-bauer.net>
* treewide: sysupgrade: don't use $ARGV in platform_do_upgrade()Rafał Miłecki2019-07-171-1/+1
| | | | | | | stage2 passes image path to platform_do_upgrade() as an argument so it can be simply accessed using $1 Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* lantiq: fix etop compiler warningsMathias Kresin2019-07-072-10/+14
| | | | | | | | | | | | | | The following warnings are introduced by our own patches: lantiq_etop.c:173:1: warning: no semicolon at end of struct or union }; ^ lantiq_etop.c: In function 'ltq_etop_change_mtu': lantiq_etop.c:725:2: warning: ISO C90 forbids mixed declarations and code [-Wdeclaration-after-statement] int max = ETH_HLEN + VLAN_HLEN + new_mtu + ETH_FCS_LEN; ^~~ Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: dts: use generic node namesPetr Štetiar2019-07-0765-161/+155
| | | | | | | | | | | | | | | | | | In DTS Checklist[1] we're now demanding proper generic node names, as the name of a node should reflect the function of the device and use generic name for that[2]. Everybody seems to be copy&pasting from DTS files available in the repository today, so let's unify that naming there as well and provide proper examples. 1. https://openwrt.org/submitting-patches#dts_checklist 2. https://github.com/devicetree-org/devicetree-specification/blob/master/source/devicetree-basics.rst#generic-names-recommendation Signed-off-by: Petr Štetiar <ynezz@true.cz> [split out treewide patch, integrated P2812HNUF1 rename patch] Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [merged key and led changes, use generic node name for flash, wifi and gpio] Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: dts: drop falcon clock nodeMathias Kresin2019-07-071-26/+0
| | | | | | | | | It is pretty ovbious a misuse of the simple-bus binding as no child has a address. Luckly the clock node isn't used at all so it is safe to get rid of it. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: dts: drop empty falcon devicetree nodeMathias Kresin2019-07-071-6/+2
| | | | Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: dts: fix unit address mismatch warningMathias Kresin2019-07-071-2/+2
| | | | | | | | | Set a unit address matching the reg property for the EASY98000 ethernet node. Fixes a unit mismatch devicetree compiler warning. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: dts: move localbus childs to dtsMathias Kresin2019-07-079-52/+80
| | | | | | | | The localbus childs are highly board specific and need to be part of the board dts. Otherwise we run into duplicate unit address issues if a board has something else (NAND) connected to the bus id. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: dts: fix vmmc unit and register addressMathias Kresin2019-07-072-3/+3
| | | | | | | | | | The register address is the same for danube und vr9. The register size is 0x400 byte for danube and 0x300 byte for vr9. The change doesn't have an impact as the vmmc driver doesn't use the devicetree and has hardcoded register offsets. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: dts: use lower case for hex valuesMathias Kresin2019-07-075-42/+42
| | | | | | Use only lower case for hex values to keep it consistent. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: dts: drop superfluous address and size cellsMathias Kresin2019-07-0752-172/+3
| | | | | | | | Fixes the following devicetree compiler warning: unnecessary #address-cells/#size-cells without "ranges" or child "reg" property Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: dts: move partitions into partition nodeMathias Kresin2019-07-074-88/+103
| | | | Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: dts: add missing size and address cellsMathias Kresin2019-07-074-0/+8
| | | | | | | | | | Add size and address cells where missing to fix the following devicetree compiler warning: Warning (avoid_default_addr_size): Relying on default #address-cells value Warning (avoid_default_addr_size): Relying on default #size-cells value Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: dts: fix size cellsMathias Kresin2019-07-0711-11/+11
| | | | | | SPI nodes only need an address and no size. Drop the size everywhere. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: dts: fix malformed unit addressesMathias Kresin2019-07-071-1/+1
| | | | | | | | Fixes: Warning (unit_address_format): unit name should not have leading "0x" Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: dts: drop superfluous unit addressMathias Kresin2019-07-0720-68/+48
| | | | | | | | | | | | | The cpu temperature driver has the register offset hardcode and doesn't need a reg. The mdio bus node is only used as a well known name and doesn't need a reg or unit address. syscon-reboot doesn't have a unit address or a reg either. The unit name collides with reset-controller@10 anyway. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: dts: add reg if unit address is setMathias Kresin2019-07-075-0/+29
| | | | | | | | | Add the reg property if the node has an unit address. Fixes the following device tree compiler warning: Warning (unit_address_vs_reg): node has a unit name, but no reg property Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: dts: move memory node to board dtsMathias Kresin2019-07-0747-16/+43
| | | | | | | The memory node is highly board specific and should be only defined in the board dts. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: drop kernel 4.14 supportMathias Kresin2019-07-0434-14836/+0
| | | | | | | The current state of the kernel 4.14 support is in the openwrt-19.07 branch. No need to keep a not default used kernel in this branch. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: switch to kernel 4.19Martin Blumenstingl2019-07-041-1/+1
| | | | | | Use kernel 4.19 by default. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
* lantiq: 4.19: fix panic when using the DMA APIMartin Blumenstingl2019-07-045-32/+127
| | | | | | | | | | | With kernel 4.19 the DMA API relies on a struct device to work properly. Backport upstream patches which passed a struct device instead of NULL to the DMA API. Fixes kernel panics during boot. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: 4.19: load PCIe driver after PCI driverMathias Kresin2019-07-041-4/+29
| | | | | | | | | | | | | | | | | | | | | | | | | In case a PCI device is physical present, the Lantiq PCI driver need to be loaded prior to the Lantiq PCIe driver. Otherwise none of them will work because updating the BAR 0 of a device attached to the PCIe Bus will fail. Till kernel commit 9667bb039bf6 ("MIPS: lantiq: remove unnecessary of_platform_default_populate call"), the Lantiq PCI driver was probed early in the boot process via plat_of_setup(). Since the mentioned commit, both drivers are probed via of_platform_default_populate_init() and they are probed according to their order in the devicetree source file. If the Lantiq PCI driver is enabled in the devicetree, defer the probing og the Lantiq PCIe driver till the Lantiq PCI driver is probed. Use the presence of a PCU bus as indicater for a loaded Lantiq PCI driver. This way we don't need to shuffle the PCI/PCIe nodes in the devicetree source file, as they are already (correctly) ordered based on the unit address. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: 4.19: increase usb reset timeoutsMartin Blumenstingl2019-07-042-0/+64
| | | | | | | | | | | With kernel 4.19 dwc2 would not want to initialize due to reset timeouts, while it worked fine with 4.14. Increase the reset timeouts to 1 second, as it was used by the old lantiq ifxhcd usb driver. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: make patches applyHauke Mehrtens2019-07-0422-282/+106
| | | | | | | | | | | | | | | | | | | | | | | | | | The following patches are dropped because they are now upstreamed: - 0002-gpio-stp-xway-Implement-get-callback.patch upstreamed with commit 5b9b2b5284f819 ("gpio: stp-xway: Implement get callback") - 0027-01-net-phy-intel-xway-add-VR9-version-number.patch upstreamed with commit 5b73d9955fb4b0 ("net: phy: intel-xway: add VR9 version number") - 0027-02-net-phy-intel-xway-add-VR9-v1.1-phy-ids.patch upstreamed with commit f452518c982e57 ("net: phy: intel-xway: add VR9 v1.1 phy ids") The following patches were updated: - 0018-MTD-nand-lots-of-xrx200-fixes.patch the mainline driver now resides in drivers/mtd/nand/raw/xway_nand.c (instead of drivers/mtd/nand/xway_nand.c) - 0025-NET-MIPS-lantiq-adds-xrx200-net.patch the DMA API now requires a valid device to be passed to all operations - 0028-NET-lantiq-various-etop-fixes.patch the DMA API now requires a valid device to be passed to all operations Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: copy target to kernel 4.19Hauke Mehrtens2019-07-04116-0/+14836
| | | | | | | | This just copies the files from the kernel 4.14 specific folders into the kernel 4.19 specific folder, no changes are done to the files in this commit. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* lantiq: enable STP where referencedMathias Kresin2019-07-032-0/+2
| | | | | | | | | | | While moving common used parts to dtsi files, the was disabled by default but not enabled for all boards using the STP. Fixes: f519fea4c6db ("lantiq: kernel 4.14: cleanup dts files") Reported-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> Signed-off-by: Mathias Kresin <dev@kresin.me> Reviewed-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
* kernel: bump 4.14 to 4.14.122Koen Vandeputte2019-06-031-1/+1
| | | | | | | | | Refreshed all patches. Compile-tested on: ar71xx, cns3xxx, imx6, x86_64 Runtime-tested on: ar71xx, cns3xxx, imx6, x86_64 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* lantiq: BTHOMEHUBV5A: don't power off with restart buttonAlan Swanson2019-05-301-1/+1
| | | | | | | | | | | The restart button is currently assigned to KEY_POWER power script but an easily accessible button immediately powering off the device is undesirable. Switch to using new KEY_POWER2 reboot script with 5 second seen delay. Fixes: FS#1965 Signed-off-by: Alan Swanson <reiver@improbability.net> Signed-off-by: Petr Štetiar <ynezz@true.cz> [long line wrap]
* lantiq/xrx200: enable initramfs imagesStijn Segers2019-05-151-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | 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]
* kernel: bump 4.14 to 4.14.118Koen Vandeputte2019-05-131-1/+1
| | | | | | | | | | | | | | | Refreshed all patches. Remove upstreamed: - 060-v5.1-serial-ar933x_uart-Fix-build-failure-with-disabled-c.patch Altered: - 143-gpio-fix-device-tree-gpio-hogs-on-dual-role-gpio-pin.patch Compile-tested on: ar71xx, cns3xxx, imx6, x86_64 Runtime-tested on: ar71xx, cns3xxx, imx6 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* lantiq: tdw90x0: Fix WLAN LED on TP-Link W8970 v1.2 (FS#2232)Petr Štetiar2019-04-171-0/+1
| | | | | | | | | | This patch fixes disfunctional WLAN LED on TP-Link W8970. The LED was reported working in the CC release[1], but doesn't work anymore in 18.06.2. 1. https://github.com/openwrt/chaos_calmer/commit/420cb24d41fcd650795f09d2b26e0e1d2cf21165 Tested-by: Damian Janarek <dzanar18@o2.pl> Signed-off-by: Petr Štetiar <ynezz@true.cz>
* lantiq: kernel 4.14: fix usb_phy1 reset status bit in vr9.dtsMartin Schiller2019-03-181-1/+1
| | | | | | The status of USB PHY 1 Reset Domain is also in bit 5 of RST_STAT2. Signed-off-by: Martin Schiller <ms@dev.tdt.de>
* fritz-tools: add support for IPQ40xx platformDavid Bauer2019-03-131-2/+2
| | | | | | | | AVM devices based on Qualcomm IPQ40xx do not store sector health information in the OOB area. Make this check optional to support this platform. Signed-off-by: David Bauer <mail@david-bauer.net>
* lantiq: Refresh kernel 4.14 configurationHauke Mehrtens2019-03-101-0/+2
| | | | | | | This adds two configuration options which are getting automatically added. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* ltq-atm/ltq-ptm: re-enable/fix reset_ppe() functionality for VR9Martin Schiller2019-03-101-0/+2
| | | | | | | | | | | | | | | This patch re-enables the reset_ppe() functionality for VR9 targets by using the new lantiq rcu subsystem. The reset sequence in the reset_ppe() function was taken from the ppa datapath driver of lantiq UGW 7.4.1. Additionally it adds the required reset definitions to the vr9 dtsi file. It also prepares the reset_ppe() function calls for the other lantiq targets. This feature is needed to be able to switch between ltq-atm/ltq-ptm driver in ATM/PTM Auto-Mode at runtime. Signed-off-by: Martin Schiller <ms@dev.tdt.de>
* lantiq: add support for AVM FRITZ!Box 7362 SLDanijel Tudek2019-03-105-1/+157
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Hardware: - SoC: Lantiq VRX288 - RAM: Winbond W971GG6JB 1 Gb (128 MiB) - Flash: - SPI: 8 Mb (1 MiB) for bootloader and tffs - NAND: 1 Gb (128 MiB) for OS - xDSL: Lantiq VRX208 - WLAN: Atheros AR9381 - DECT: Dialog Semiconductors SC14441 Everything except FXS/DECT works (no drivers for AVM's FXS implementation with SC14441). Installation via FTP: 1. Use scripts/flashing/eva_ramboot.py to send initramfs-kernel.bin to the device when powering on. Standard AVM procedures with finding the correct IP address and the right moment to open FTP apply here (approx. 4 seconds on 7362SL). IMPORTANT: set lzma compression in ramdisk options, bootloader stalls when receiving uncompressed images. 2. Transfer sysupgrade.bin image with scp to /tmp directory and run sysupgrade 3. First boot might take a bit longer if linux_fs_start was set to 1, in that case the device will reboot twice, first time it will fail to load second kernel (overwritten by ubifs), set linux_fs_start to 0 and reboot. OpenWrt uses the entire NAND flash. Kernel uses 4 MiB and rootfs uses the rest of 124 MiB, overwriting everything related to FRITZ!OS - both OS images, config and answering machine/media server data. To return to FRITZ!OS, use AVM's recovery image. Signed-off-by: Danijel Tudek <danijel.tudek@gmail.com>
* lantiq: move common FRITZ736X bits into dtsiDanijel Tudek2019-03-102-181/+228
| | | | | | | Move common FRITZ736X bits into dtsi file as a preparation for FRITZ7362SL support. Signed-off-by: Danijel Tudek <danijel.tudek@gmail.com>
* lantiq: add support for AVM FRITZ!Box 7412Andy Binder2019-03-105-0/+254
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Hardware: SoC: Lantiq VRX 220 CPU Cores: 2x MIPS 34Kc at 500 MHz RAM: 128 MiB 250 MHz Storage: 128 MiB NAND flash Ethernet: built-in Fast Ethernet switch, only port 2 is used Wireless: Atheros AR9287-BL1A b/g/n with 2 pcb antennas Modem: built-in A/VDSL2 modem DECT: Dialog SC14441 LEDs: 1 two-color, 4 one-color Buttons: 2 FXS: 1 port via TAE or RJ12 connector Everything except FXS/DECT works (no drivers for AVM's FXS implementation with SC14441). Installation: Use the eva_ramboot.py script to load an initramfs image on the device. Run it a few seconds after turning the device on. $ scripts/flashing eva_ramboot 192.168.178.1 bin/targets/lantiq/xrx200/openwrt-lantiq-xrx200-avm_fritz7412-initramfs-kernel.bin If it fails to find the device try the ip address 169.254.120.1. (Firmware updates or the recovery tool apparently change it.) IMPORTANT: set lzma compression in ramdisk options, bootloader stalls when receiving uncompressed images. The device will load it in ram and boot it. You can reach it under the openwrt default ip address 192.168.1.1. Check if the key linux_fs_start is not set to 1 in tffs: $ fritz_tffs_nand -d /dev/mtd1 -n linux_fs_start If it is set to 1, the bootloader will select the wrong set of partitions. Restart the box and install an FritzOS upgrade or do a recovery. Afterwards start again at step 1. Run sysupgrade to persistently install OpenWRT. Signed-off-by: Valentin Spreckels <Valentin.Spreckels@Informatik.Uni-Oldenburg.de> Signed-off-by: Andy Binder <AndyBinder@gmx.de>
* lantiq: enlarge ZyXEL P-2812HNU-F1 kernel partition (FS#2124)Christian Lamparter2019-03-062-3/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The current snapshot release kernel with it's 2119245 Byte size is too big to fit into the 2097152 (2MiB) area that was set aside for the kernel. Which causes the device to fail to boot (after an update or even during a fresh install) NAND read: device 0 offset 0x60000, size 0x200000 2097152 bytes read: OK ## Booting kernel from Legacy Image at 80800000 ... Image Name: MIPS OpenWrt Linux-4.14.98 Created: 2019-02-13 9:37:36 UTC Image Type: MIPS Linux Kernel Image (lzma compressed) Data Size: 2119245 Bytes = 2 MiB Load Address: 80002000 Entry Point: 80002000 Verifying Checksum ... Bad Data CRC ERROR: can't get kernel image! This patch fixes the problem by enlarging the kernel partition at the cost of the ubi/data partition behind it. The patch also adds a KERNEL_SIZE variable to the image Makefile to prevent silent corruptions from happening in the future. Please note: The u-boot environment for the router also needs to be updated. So please attach an appropriate serial converter cable and enter the following commands into the u-boot prompt: setenv nboot 'nand read 0x80800000 0x60000 0x300000; bootm 0x80800000' saveenv The wiki has been updated accordingly: <https://openwrt.org/toh/zyxel/p2812hnu-f1> Fixes: FS#2124 Suggested-by: Mafketel (User on bugs.openwrt.org) Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* kernel: bump 4.14 to 4.14.96Koen Vandeputte2019-01-281-1/+1
| | | | | | | | | | | | Refreshed all patches. Remove upstreamed patches: - 142-jffs2-Fix-use-of-uninitialized-delayed_work-lockdep-.patch Compile-tested on: ar71xx, cns3xxx, imx6, x86_64 Runtime-tested on: ar71xx, cns3xxx, imx6 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* lantiq/led_dsl: Fix netdev led triggerMartin Schiller2019-01-271-1/+3
| | | | | | | | | | | In the upstream netdev led trigger the one mode file was replaced by 3 files named rx, tx and link. Fix the netdev trigger configuration code to use the modified API. This fix is based on 201058b35ce ("base-files: Fix netdev led trigger") Fixes: aa3b6a08c56 ("kernel: Replace ledtrig-netdev with upstream backport") Signed-off-by: Martin Schiller <ms@dev.tdt.de>
* lantiq: Add support for 2nd USB port on Fritz!Box 7320 and 7330Robert Resch2019-01-261-0/+8
| | | | | | | | Enable support for 2nd USB port, which is available on Fritz!Box 7320 and 7330. It was run-tested on 7320 and 7330 as well. Signed-off-by: Robert Resch <openwrt@webnmail.de> Signed-off-by: Petr Štetiar <ynezz@true.cz>
* lantiq: make AVM FRITZ!Box naming consistentDavid Bauer2019-01-267-12/+12
| | | | | | | | | | | | | | This commit changes the model string and device title of all AVM boards to fit the naming of the manufacturer. Drop all provider-specific titles as they are re-used for every device generation by 1&1. The original AVM model name is printed on the bottom of every devices. Exception applies for boards which are only supported by a specific sub-revision. Signed-off-by: David Bauer <mail@david-bauer.net>
* kernel: bump 4.14 to 4.14.95Koen Vandeputte2019-01-241-271/+0
| | | | | | | | | | | | | | Refreshed all patches. Removed superseded patches: - 0400-Revert-MIPS-smp-mt-Use-CPU-interrupt-controller-IPI-.patch Compile-tested on: ar71xx, cns3xxx, imx6, lantiq (xrx200, AVM 3370), x86_64 Runtime-tested on: ar71xx, cns3xxx, imx6, lantiq (xrx200, AVM 3370) Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com> Tested-by: Mathias Kresin <dev@kresin.me> Tested-by: Robert Resch <openwrt@webnmail.de>
* treewide: dts: Remove default-state=off property from all gpio LED nodesPetr Štetiar2018-12-173-23/+0
| | | | | | | | | | | | | | | | | | >From the Documentation/devicetree/bindings/leds/common.txt: - default-state : The initial state of the LED. Valid values are "on", "off", and "keep". If the LED is already on or off and the default-state property is set the to same value, then no glitch should be produced where the LED momentarily turns off (or on). The "keep" setting will keep the LED at whatever its current state is, without producing a glitch. The default is off if this property is not present. So setting the default-state of the LEDs to `off` is redundant as `off` is default LED state anyway. We should remove it as almost every new PR/patch submission contains this property by default which seems to be just copy&paste from some DTS file already present in the tree. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* lantiq: add integer latency stat for lantiq-dslAndre Heider2018-12-161-0/+8
| | | | | | | The current stats always have a 'ms' suffix, and they're used by luci. Introduce dsl.latency_[down|up] values, exported in µs without suffix. Signed-off-by: Andre Heider <a.heider@gmail.com>
* apm821xx, ath79, ipq40xx, ipq806x, lantiq, ramips: base-files: Use generic ↵Petr Štetiar2018-12-061-46/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | diag.sh I wanted to add status LEDs support to my imx6 based board and have found out, that I could use diag.sh script found in ramips platform, which seems to be also shared in a few other platforms: 4801276bc2078c5bcf03003c831e3b0a target/linux/ramips/base-files/etc/diag.sh 4801276bc2078c5bcf03003c831e3b0a target/linux/ipq40xx/base-files/etc/diag.sh 4801276bc2078c5bcf03003c831e3b0a target/linux/ath79/base-files/etc/diag.sh And @chunkeey suggested to me, that I can also add lantiq, ipq806x and apm821xx to the list of platforms which could share this generic diag.sh. I've extended the base diag.sh in a way, that if it detects any of the DTS LED aliases, then it would use the generic DTS set_led_state code. The code in platform's diag.sh has moved to base-files package in this commit: base-files: diag.sh: Make it more generic towards DTS so it could be reused Signed-off-by: Petr Štetiar <ynezz@true.cz> Tested-by: Christian Lamparter <chunkeey@gmail.com> (apm821xx and ipq40xx)
* lantiq: enable FXS ports on VR200vKevin Schmidt2018-11-265-220/+341
| | | | | | | Disables SMP support. Add VR200 target to keep SMP on FXS-less device variant. Signed-off-by: Kevin Schmidt <kevin.patrick.schmidt@googlemail.com>
* lantiq/basefiles: use shutdown instead of stop when the system goes downMartin Schiller2018-11-251-1/+1
| | | | | | I can't see any reason why we shouldn't use shutdown for lantiq as well. Signed-off-by: Martin Schiller <ms@dev.tdt.de>
* kernel: bump 4.14 to 4.14.82Koen Vandeputte2018-11-221-1/+1
| | | | | | | | | | | Refreshed all patches. Compile-tested: ar71xx, cns3xxx, imx6, x86_64 Runtime-tested: ar71xx, cns3xxx, imx6, x86_64 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com> Tested-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk> Tested-by: Stijn Tintel <stijn@linux-ipv6.be>