aboutsummaryrefslogtreecommitdiffstats
path: root/target
Commit message (Collapse)AuthorAgeFilesLines
...
* ramips: add support for Tama W06INAGAKI Hiroshi2018-02-205-0/+129
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Tama Electric Axing W06 is a 2.4 GHz band 11n router, based on Mediatek MT7688AN. Specification: - MT7688AN (575 MHz) - 64 MB of RAM (DDR2 SDRAM) - 16 MB of Flash (SPI) - 1T1R 2.4 GHz - 1x 10/100/1000 Mbps Ethernet - 4x LEDs (GPIO connected: 3), 1x button - 1x USB 2.0 Type-A (host) - UART header on PCB (GND, RX, TX, Vcc from RJ45 side) Flash instruction using sysupgrade image: 1. Connect micro-USB cable for power supply into W06 and turn on the router 2. Connect to wifi with SSID "tama-*" with password. Complete SSID and password are listed on the back of the router 3. Access to 192.168.1.1 and login with user name "admin" and password empty 4. In firmware update（ファームウェア更新） page, click "参照" button and click "ブラウザー" button to open file browser, select the sysupgrade image and press OK button 5. Wait ~150 seconds to complete flashing Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* ramips: improve GnuBee Personal Cloud Two supportMathias Kresin2018-02-207-36/+22
| | | | | | | | | | | | | | | | | | Use the generic board detection for the GnuBee Personal Cloud Two instead of the target specific one as all recent additions are doing. Fixup the pinmux to set all pins used as GPIO to the function GPIO. Request pins where used. Drop the i2c from the dts. There is nothing connected. While at it fix an indentation issue and use references instead of duplicating the whole node path. Use the same switch config as for the GB-PC1 and drop the led trigger for the not supported IP1001 phy connected to second rgmii. Fixes: c60a21532bc9 ("ramips: Add support for the GnuBee Personal Cloud Two") Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: use generic board detection for D-Link DAP-1522 A1Mathias Kresin2018-02-205-8/+5
| | | | | | | Use the generic board detection for the D-Link DAP-1522 A1 instead of the target specific one as all recent additions are doing. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: kernel 4.14: update dts filesHauke Mehrtens2018-02-2038-159/+794
| | | | | | | | | | | | | | | | | | | | Updated the devicetree source files to make use of the following upstreamed drivers: - xrx200 ethernet phy - reset controller unit - dwc2 - fpi Use our custom xrx200 ethernet phy compatible to support boards, which have switched the vr9 revision during lifetime, with a single devicetree source file. By switching to the dwc2 driver + usb phy framework, we don't need to used our custom gpio power patch and can use a fixed regulator instead. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: kernel 4.14: cleanup dts filesMathias Kresin2018-02-2055-4194/+4033
| | | | | | | Move common used parts to dtsi. Add labels to nodes and reference nodes via labels in dts files. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: kernel 4.14: fix usbMathias Kresin2018-02-202-0/+62
| | | | | | | | | | On danube the USB0 registers are at 1e101000 similar to all other lantiq SoCs. On Danube and AR9 the USB core is connected to the AHB bus, hence we need to enable the AHB Bus as well. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: kernel 4.14: autoselect matching vr9 rev firmwareMathias Kresin2018-02-201-0/+45
| | | | | | | | | | | | Add a custom xrx200 ethernet phy compatible to load the firmware matching the vr9 revision without specifing an expected revision. We have quite a few boards in the tree were later produced ones are using a more recent vr9. It is impossible to distinguish which revision of the vr9 is used without opening the case and removing a heatsink for some of them. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: kernel 4.14: don't use CPU interrupt controller IPI IRQ domain supportMathias Kresin2018-02-201-0/+271
| | | | | | | | | | | | | | | | This reverts kernel commit 1eed40043579 ("MIPS: smp-mt: Use CPU interrupt controller IPI IRQ domain support"). With the patch applied, the kernel hangs during boot if SMP is active. The Lantiq IRQ controller gets registered first and it directly handles the MIPS native SW1/2 and HW0 - HW5 IRQs. It looks like this controller already registers IRQ 0 - 7 and the generic driver only gets the following IRQs starting later. The upstream discussion can be found at https://www.linux-mips.org/archives/linux-mips/2017-05/msg00059.html. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: kernel 4.14: select MFD SYSCON for aseMathias Kresin2018-02-201-0/+24
| | | | | | Enable syscon to use it for the RCU MFD on Amazon SE as well. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: kernel 4.14: update patches and configHauke Mehrtens2018-02-2035-3208/+333
| | | | | Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: kernel 4.14: copy patches, config and dts filesHauke Mehrtens2018-02-20114-0/+28761
| | | | | | | This just copies the patches, configuration and dts files into the directories hich are used for kernel 4.14. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* lantiq: make dts files and kernel config kernel version specificMathias Kresin2018-02-2080-2/+1
| | | | | | | | | | Move the devicetree source files to a kernel specific directory in preparation of adding kernel 4.14 support. Rename the subtarget kernel config files to match a specific kernel version. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: rename gphy firmwareMathias Kresin2018-02-2019-30/+30
| | | | | | | | | | Rename the gphy firmware to match the name requested by kernel 4.14 and update the devicetree source files to use the new name. Update the u-boot lantiq Makefile to be compatible with the new names as well. Signed-off-by: Mathias Kresin <dev@kresin.me>
* mxs: drop support for 4.9Michael Heimpold2018-02-203-486/+0
| | | | Signed-off-by: Michael Heimpold <mhei@heimpold.de>
* mxs: enable LRADC driverMichael Heimpold2018-02-201-2/+2
| | | | Signed-off-by: Michael Heimpold <mhei@heimpold.de>
* 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>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-07 16:26:57 +0000