aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/mvebu
Commit message (Collapse)AuthorAgeFilesLines
* kernel: unify CONFIG_GPIO_SYSFS in kernel configsFelix Fietkau2020-08-062-2/+0
| | | | | | Enable it for all platforms Signed-off-by: Felix Fietkau <nbd@nbd.name>
* mvebu: fix alphabetic sorting in 02_networkAdrian Schmutzler2020-07-311-6/+6
| | | | | | This has been overlooked when removing solidrun,clearfog-a1 entry. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* mvebu: increase compat version for SolidRun ClearFog BaseAdrian Schmutzler2020-07-312-1/+4
| | | | | | | | | | | | | When changing the Pro variant to DSA, the ethernet interface rename script was dropped by all devices to keep them in sync: be309bfd7445 ("mvebu: drop 06_set_iface_mac preinit script") Therefore, network config will be broken after upgrade for the Base variant as well. Increase the compat version and provide a message to signal that to the users. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* mvebu: implement compatibility version for DSA migrationAdrian Schmutzler2020-07-312-0/+44
| | | | | | | | | | | | | | | | | | | | | | | | | | This implements the newly introduced compat-version to prevent upgrade between swconfig and DSA for mvebu. Just define a compat version with minor increment and an appropriate message for both image (in Makefile) and device (in base-files). Having taken care of sysupgrade, we can put back the SUPPORTED_DEVICES that have been removed in previous patches to prevent broken config. Attention: All users that already updated to the DSA versions in master will receive the same incompatibility warning since their devices are still "1.0" as far as fwtool can tell. Those, and only those, can bypass the upgrade check by using force (-F) without having to reset config again. In addition, the new version string needs to be put into uci config manually, so the new fwtool knows that it actually deals with a "1.1": uci set "system.@system[-1].compat_version=1.1" uci commit system Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* mvebu: only disable WRT1900AC v1 and WRT32X for buildbotsAdrian Schmutzler2020-07-271-2/+4
| | | | | | | Use "DEFAULT := n" to only disable devices for buildbots, but keep them available for manual build. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* mvebu: disable WRT1900AC v1 and WRT32X images for nowJo-Philipp Wich2020-07-261-2/+2
| | | | | | | | | The kernel appears to have grown too large, breaking the build for the entire target. Disable the affected images for now until the situation is dealt with. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* kernel: bump 5.4 to 5.4.52John Audia2020-07-1712-67/+67
| | | | | | | | | update_kernel.sh refreshed all patches, no human interaction was needed Build system: x86_64 Run-tested: Netgear R7800 (ipq806x) Signed-off-by: John Audia <graysky@archlinux.us>
* mvebu: add Kobol Helios 4 deviceAlberto Bursi2020-07-179-0/+100
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The Helios 4 is a NAS from Kobol that is powered by an Armada 38x MicroSOM from Solidrun, similarly to Clearfog. This device has: -Armada 38x CPU (dual core ARMv7 1.6 Ghz) -2 GB of ECC RAM -Gigabit ethernet (Marvell) -2x USB 3.0 ports -4x Sata 3.0 ports -i2c header (J9 |>GND|SDA|SCL|VCC) -2x 3-pin fan headers with PWM -micro-usb port is a TTL/UART to USB converter connected to TTL -MicroSD card slot -System, 4xSata and 1xUSB LEDs NOT WORKING: fan control Fan Control requires a kernel patch that is available in the Armbian project (the "default firmware" of this device) and named mvebu-gpio-remove-hardcoded -timer-assignment This patch isn't acceptable by OpenWrt, it should be upstreamed. I also have that patch in my own local OpenWrt builds, in case you want a more clean and less confusing patch for upstreaming. To install, write the disk image on a micro SD card with dd or win32 disk imager, insert the card in the slot. Check that the dip switch battery for boot selection is as follows Switch 1 and 2 down/off, switches 3, 4, 5 up/on. Signed-off-by: Alberto Bursi <bobafetthotmail@gmail.com>
* mvebu: add support for MACCHIATObin Single ShotTomasz Maciej Nowak2020-07-123-6/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add support for Marvell MACCHIATObin Single Shot, cortex-a72 based Marvell ARMADA 8040 Community board. Single Shot was broken as the device tree is different on the Double Shot Board. Specifications: - Quad core Cortex-A72 (up to 2GHz) - DDR4 DIMM slot with optional ECC and single/dual chip select support - Dual 10GbE (1/2.5/10GbE) SFP+ 2.5GbE (1/2.5GbE) via SFP 1GbE via copper - SPI Flash - 3 X SATA 3.0 connectors - MicroSD connector - eMMC - PCI x4 3.0 slot - USB 2.0 Headers (Internal) - USB 3.0 connector - Console port (UART) over microUSB connector - 20-pin Connector for CPU JTAG debugger - 2 X UART Headers - 12V input via DC Jack - ATX type power connector - Form Factor: Mini-ITX (170 mm x 170 mm) More details at http://macchiatobin.net Installation: Write the Image to your Micro SD Card and insert it in the MACCHIATObin Single Shot SD Card Slot. In the U-Boot Environment: 1. reset U-Boot environment: env default -a saveenv 2. prepare U-Boot with boot script: setenv bootcmd "load mmc 1:1 0x4d00000 boot.scr; source 0x4d00000" saveenv or manually (hanging lines indicate wrapped one-line command): setenv fdt_name armada-8040-mcbin-singleshot.dtb setenv image_name Image setenv bootcmd 'mmc dev 1; ext4load mmc 1:1 $kernel_addr $image_name;ext4load mmc 1:1 $fdt_addr $fdt_name;setenv bootargs $console root=/dev/mmcblk1p2 rw rootwait; booti $kernel_addr - $fdt_addr' saveenv On newer Bootloaders (18.12) the Variables have been changed, use: setenv fdt_name armada-8040-mcbin-singleshot.dtb setenv image_name Image setenv bootcmd 'mmc dev 1; ext4load mmc 1:1 $kernel_addr_r $image_name;ext4load mmc 1:1 $fdt_addr_r $fdt_name;setenv bootargs $console root=/dev/mmcblk1p2 rw rootwait; booti $kernel_addr_r - $fdt_addr_r' Reported-by: Alexandra Alth <alexandra@alth.de> Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl> Tested-by: Alexandra Alth <alexandra@alth.de> [add specs and installation as provided by Alexandra Alth] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* mvebu: fix support for Marvell 8040 MACCHIATOBinAdrian Schmutzler2020-07-114-5/+19
| | | | | | | | | | | | | | | | | | | | | | Between kernels 4.20 and 5.0, a new variant of this board has been introduced ("Single Shot"), and the existing one has been renamed with the appendix "Double Shot". [1] This also adjusted the first compatible in the list: marvell,armada8040-mcbin -> marvell,armada8040-mcbin-doubleshot This patch updates the OpenWrt implementation of this device by adjusting the relevant references to that compatible (i.e., our board name). To still provide support for 4.19 with our setup, this adds a small patch to change the compatible there as well. [1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b1f0bbe2700051886b954192b6c1751233fe0f52 Cc: Tomasz Maciej Nowak <tomek_n@o2.pl> Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> Reviewed-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* mvebu: config define i2c pxa slaveScott Roberts2020-07-041-0/+1
| | | | | | | | | We are setting CONFIG_I2C_PXA is not set If you do set pxa to y then you have issues if you do not have CONFIG_I2C_PXA_SLAVE is not set Fixes: dd13add3ceed ("kernel: i2c-pxa: remove slave") Signed-off-by: Scott Roberts <ttocsr@gmail.com>
* mvebu: LS421DE: use automatic fan control with thermal zonesDaniel González Cabanelas2020-07-042-3/+67
| | | | | | | | | | | | | | | | The Buffalo Linkstation LS421DE has a chassis fan for cooling two internal hard drives. Currently there is no control over this fan, running always at fixed medium speed. With the recent jump to the kernel 5.4, now we can monitor the hard drive temperature and control the fan with thermal zones. Install the kmod-hwmon-drivetemp module and wire up a thermal zone on the dts file to allow automatic fan control by the kernel. Tested succesfully using a single Crucial BX500 SSD drive. Signed-off-by: Daniel González Cabanelas <dgcbueu@gmail.com>
* kernel: Update kernel 4.19 to version 4.19.131Hauke Mehrtens2020-07-043-59/+4
| | | | | | | | | | | | | Fixes: - CVE-2020-10757 The "mtd: rawnand: Pass a nand_chip object to nand_release()" commit was backported which needed some adaptations to other code. Run tested: ath79 Build tested: ath79 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* mvebu: move definition of factory.img out of Device/DefaultAdrian Schmutzler2020-06-282-1/+4
| | | | | | | | | | The Device/Default definition in mvebu defines an IMAGE/factory.img which is not included in IMAGES, and only used twice in the individual definitions. Move it out of the default definition to keep it closer to the reassignment of IMAGES and make it more consistent with respect to other values of IMAGE/factory.img Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* mvebu: remove non-existant board name solidrun,clearfog-a1Adrian Schmutzler2020-06-281-1/+0
| | | | | | | | | | | | | | In 02_network, the board name solidrun,clearfog-a1 is used in a case, but it does not seem to be used/exist anywhere else in OpenWrt. The valid strings are: - solidrun,clearfog-pro-a1 - solidrun,clearfog-base-a1 Fixes: 12795ec9f16b ("mvebu: split interface configuration for clearfog pro and base") Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* mvebu: LS421DE: dts file improvementsDaniel González Cabanelas2020-06-271-31/+22
| | | | | | | | | | | | - Delete useless HDD presence inputs: they aren't buttons, and probably they are outputs in the stock firmware. - Change the Function Button keycode: the current one isn't mapped by the kernel module. - Use the recommended property names for the ethernet stuff. - Add missing i2c pinmux. - Minor cosmetic changes. Signed-off-by: Daniel González Cabanelas <dgcbueu@gmail.com>
* mvebu: consolidate DTS filesAdrian Schmutzler2020-06-2312-837/+0
| | | | | | | | | | | | The DTS files in files-4.19 and files-5.4 are exactly identical except for one file (armada-3720-uDPU.dts), which is only present for 4.19, as it has been upstreamed before 5.4. Since there is no point in maintaining all these identical files twice, this patch moves them to the "files" directory, only keeping the named exception to files-4.19. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* mvebu: fix default EU regdomain for Linksys WRT AC devicesJose Olivera2020-06-231-1/+1
| | | | | | | | | | | | | | | | | | | | | The mwlwifi driver sets the default country code for EU (fi- rmware region code 0x30) certified devices to FR (France), not DE (Germany). Whilst this is a trivial fix, novice users may not know how mwlwifi negatively reacts to a non-matching country code and may leave the setting alone. Especially si- nce it is under the advanced settings section in LuCI. Relevant mwlwifi driver code: https://github.com/kaloz/mwlwifi/commit/0a550312ddb5a9e00e8d602d5571598f25a78158 The mwlwifi driver readme states "Please don't change country code and let mwlwifi set it for you." However, OpenWrt's current behaviour does not adhere to this with its default, 'just flashed from factory' setting for EU devices. Signed-off-by: Jose Olivera <oliverajeo@gmail.com> [rebase, extend commit message] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* mvebu: fix bootloader kernel commandline manglingPetr Štetiar2020-06-161-27/+34
| | | | | | | | | | | | Currently I'm unable to boot initramfs image with `console=ttyS0,115200` kernel commandline as the kernel commandline mangling resets kernel commandline if there is no `root=` option provided, efectively clearing whatever I pass to the kernel, making the `root=` option mandatory. So if the kernel commandline mangling is not appropriate just leave the kernel commandline as it is. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* treewide: drop shebang from non-executable target filesAdrian Schmutzler2020-06-163-3/+0
| | | | | | | | | | | | | | This drops the shebang from all target files for /lib and /etc/uci-defaults folders, as these are sourced and the shebang is useless. While at it, fix the executable flag on a few of these files. This does not touch ar71xx, as this target is just used for backporting now and applying cosmetic changes would just complicate things. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* treewide: simplify inclusion of subtarget image filesAdrian Schmutzler2020-06-111-11/+1
| | | | | | | | | | | | | | Many target use a repetitive if-include scheme for their subtarget image files, though their names are consistent with the subtarget names. This patch removes these redundant conditions and just uses the variable for the include where the target setup allows it. For sunxi, this includes a trivial rename of the subtarget image Makefiles. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* mvebu: remove ClearFog Pro SUPPORTED_DEVICESDENG Qingfang2020-06-051-1/+0
| | | | | | | | | | A direct upgrade from previous swconfig version with incompatible settings to DSA will break the internet. Remove SUPPORTED_DEVICES so users cannot upgrade directly. Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn> [rebase after Linksys rename, adjust title] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* mvebu: rename Linksys devices based on their common namesPaul Spooren2020-06-0521-77/+223
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The Linksys devices in mvebu target feature a mixed naming, where parts are based on the official product name (device node, image; e.g. WRT3200ACM) and parts are based on the internal code name (DTS file name, compatible, LED labels; e.g. rango). This inconsistent naming has been perceived as quite confusing. A recent attempt by Paul Spooren to harmonize this naming in kernel has been declined there. However, for us it still makes sense to apply at least a part of these changes locally. Primarily, this patch changes the compatible in DTS and thus the board name used in various scripts to have them in line with the device, model and image names. Due to the recent switch from swconfig to DSA, this allows us to drop SUPPORTED_DEVICES and thus prevent seamless upgrade between these incompatible setups. However, this does not include the LED label rename from Paul's initial patch: I don't think it's worth keeping the enormous diff locally for this case, as we can implement this much easier in 01_leds if we have to live with the inconsistency anyway. Signed-off-by: Paul Spooren <mail@aparcar.org> [rebase, extend to all devices, drop DT LED changes] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* mvebu: rename Linksys Mamba WAN portDENG Qingfang2020-06-032-0/+26
| | | | | | Rename it to wan to match Linksys Armada 385 series Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>
* mvebu: remove swconfig packageDENG Qingfang2020-06-031-2/+2
| | | | Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>
* mvebu: drop 06_set_iface_mac preinit scriptDENG Qingfang2020-06-031-50/+0
| | | | | | | | MAC address is set in board.d script Interface swapping is not needed anymore as switching to DSA breaks previous configuration anyway Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>
* mvebu: use ucidef to set up MAC addressDENG Qingfang2020-06-031-38/+75
| | | | | | Use ucidef to set up MAC address instead of preinit script Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>
* mvebu: use eth0 as DSA CPU port for Linksys WRTDENG Qingfang2020-06-032-0/+54
| | | | | | | | eth0 has HW MAC address while eth2 does not. Use eth0 instead so we don't have to set LAN MAC manually. Disable unused eth2, until multi CPU port is supported. Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>
* mvebu: update default config for DSADENG Qingfang2020-06-032-11/+5
| | | | | | | | Update network/LED configuration for DSA driver. sysupgrade from images prior to this commit with config preserved will break the ethernet. Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>
* mvebu: remove swconfig symbols from kernel configDENG Qingfang2020-06-032-4/+0
| | | | Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>
* mvebu: drop swconfig patchesDENG Qingfang2020-06-036-182/+0
| | | | | | Drop swconfig patches for Clearfog and Linksys WRT Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>
* mvebu: switch to kernel 5.4Adrian Schmutzler2020-06-031-1/+1
| | | | | | | | | Last reports with kernel 5.4 have all been positive [1], so let's open this to a wider range of testers. [1] https://github.com/openwrt/openwrt/pull/2804 Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* mvebu: espressobin: fix SATA and USB 3.0 ports detectionTomasz Maciej Nowak2020-06-031-0/+53
| | | | | | | | | | | | | | | | | This commit removes changes from upstream commits: 8e18c8e58da6 arm64: dts: marvell: armada-3720-espressobin: declare SATA PHY property bd3d25b07342 arm64: dts: marvell: armada-37xx: link USB hosts with their PHYs For most boards which have factory bootloader this caused that devices connected to USB 3.0 and SATA port were not detected. For them to function users would need to upgrade the bootloader to version with ARM Trusted Firmware 2.1 or later. Unfortunately there is no official bootloader image with updated ATF component, therefore drop these properties from nodes. This change was also tested briefly with bootloader with updated ATF and the ports functioned properly. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* kernel: bump 5.4 to 5.4.43Petr Štetiar2020-06-022-7/+2
| | | | | | | | | | | Refreshed patches, removed upstreamed patch: bcm27xx: 950-0642-component-Silence-bind-error-on-EPROBE_DEFER.patch Run tested: qemu-x86-64 Build tested: x86/64, imx6, sunxi/a53 Signed-off-by: Petr Štetiar <ynezz@true.cz>
* linux: mvebu: backport mvneta XDP support fixesJakov Petrina2020-05-284-0/+200
| | | | | | | | | | | | This patch backports additional fixes for XDP support in the mvneta driver. These changes are found upstream as commits: b37fa92e20ef2 net: mvneta: fix build skb for bm capable devices f383b2950070c net: mvneta: rely on page_pool_recycle_direct in mvneta_run_xdp 79572c98c554d mvneta driver disallow XDP program on hardware buffer management 44efc78d0e464 net: mvneta: fix XDP support if sw bm is used as fallback Signed-off-by: Jakov Petrina <jakov.petrina@sartura.hr>
* linux: mvebu: backport mvneta XDP supportJakov Petrina2020-05-288-4/+1322
| | | | | | | | | | | | | | | | | | | | | | This patch backports XDP support in the mvneta driver used by Marvell ARMADA 37x, 38x and 37xx series SoCs. Supported actions are: - XDP_DROP - XDP_PASS - XDP_REDIRECT - XDP_TX Patches are present upstream as following commits: * b0a43db9087a net: mvneta: add XDP_TX support * 9e58c8b41065 net: mvneta: make tx buffer array agnostic * fa383f6b77a2 net: mvneta: move header prefetch in mvneta_swbm_rx_frame * 0db51da7a8e9 net: mvneta: add basic XDP support * 8dc9a0888f4c net: mvneta: rely on build_skb in mvneta_rx_swbm poll routine * 568a3fa24a95 net: mvneta: introduce page pool API for sw buffer manager * ff519e2acd46 net: mvneta: introduce mvneta_update_stats routine Signed-off-by: Jakov Petrina <jakov.petrina@sartura.hr>
* kernel: backport the I2C bus recovery for uDPURussell King2020-05-211-0/+60
| | | | | | | Backport the I2C bus recovery DT configuration for the uDPU that has been queued for 5.8. Signed-off-by: Russell King <linux@armlinux.org.uk>
* mvebu: uDPU: switch default kernel and U-Boot PHY modeJakov Petrina2020-05-092-0/+40
| | | | | | | | | | | | | | | | Certain SFP modules (most notably Nokia GPON ones) first check connectivity on 1000base-x, and switch to 2500base-x afterwards. This is considered a quirk so the phylink switches the interface to 2500base-x as well. However, after power-cycling the uDPU device, network interface/SFP module will not work correctly until the module is re-seated. This patch resolves this issue by forcing the interface to be brought up in 2500base-x mode by default. Signed-off-by: Jakov Petrina <jakov.petrina@sartura.hr> Signed-off-by: Vladimir Vid <vladimir.vid@sartura.hr> Cc: Luka Perkov <luka.perkov@sartura.hr>
* mvebu: tidy up support for GL.iNet GL-MV1000Adrian Schmutzler2020-04-274-19/+12
| | | | | | | | | | | | | | | | | This fixes a bunch of cosmetic issues with GL.iNet GL-MV1000: - apply alphabetic sorting in multiple files - use armada-3720 prefix for DTS like for other devices - fix vendor capitalization for model in DTSes - remove trivial comment in DTS files - use DEVICE_VENDOR/DEVICE_MODEL - remove redundant SUPPORTED_DEVICES - use SOC instead of DEVICE_DTS - remove empty line at EOF Fixes: 050c24f05c85 ("mvebu: add support for GL.iNet GL-MV1000") Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* mvebu: add support for GL.iNet GL-MV1000Li Zhang2020-04-264-1/+341
| | | | | | | | | | | | | | | | | | | | | | | | This patch adds supports for GL-MV1000. Specification: - SOC: Marvell Armada 88F3720 (1GHz) - Flash: 16MB (W25Q128FWSIG) - RAM: 1GB DDR4 - Ethernet: 3x GE (1 WAN + 2 LAN) - EMMC: 8GB EMMC (KLM8G1GETF-B041) - MicroSD: 1x microSD slot - USB: 1x USB 2.0 port(TypeA),1x USB 3.0 port(TypeC) - Button: 1x reset button,1x slide switch - LED: 3x greed LED - UART: 1x UART on PCB (JP1: 3.3V, RX, TX, GND) Update firmware instructions ============================ In the compiled,please gzip -d xxx.img.gz,then update firmware on uboot web. Signed-off-by: Li Zhang <li.zhang@gl-inet.com> [Copied dts file to files-5.4] Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump 4.19 to 4.19.115Koen Vandeputte2020-04-167-24/+24
| | | | | | | | | | | | | | | | | | Refreshed all patches. Remove upstreamed: - 600-ipv6-addrconf-call-ipv6_mc_up-for-non-Ethernet-inter.patch - 184-USB-serial-option-add-Wistron-Neweb-D19Q1.patch Fixes: - CVE-2020-8647 - CVE-2020-8648 (potentially) - CVE-2020-8649 Compile-tested on: cns3xxx Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* mvebu: drop armada-37xx PCI aardvark patchesTomasz Maciej Nowak2020-04-135-353/+0
| | | | | | | | | These patches were necessarry for Atheros and some Intel WiFi cards. After short testing, the current upstream driver state is enough for these WiFi cards to work. If there are still some issues with other devices, the patches could be easily restored. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* mvebu: refresh configDENG Qingfang2020-04-133-39/+88
| | | | Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>
* mvebu: refresh patchesDENG Qingfang2020-04-1334-1671/+39
| | | | Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>
* mvebu: set kernel testing version to 5.4DENG Qingfang2020-04-131-0/+1
| | | | Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>
* mvebu: copy files and patches to 5.4DENG Qingfang2020-04-1353-0/+5140
| | | | Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>
* mvebu: add support for Buffalo LinkStation LS421DEDaniel González Cabanelas2020-04-135-0/+397
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Buffalo LinkStation LS421DE is a dual bay NAS, based on Marvell Armada 370 Hardware: SoC: Marvell Armada 88F6707-A1 CPU: Cortex-A9 1200 MHz, 1 core Flash: SPI-NOR 1 MiB, NAND 512 MiB RAM: DDR3 512 MiB Ethernet: 1x 10/100/1000 Mbps USB: 1x 2.0, 1x 3.0 SATA: 2x 3.0 Gbps LEDs/Input : 5x / 2x (1x button, 1x slide-switch) RTC: Ricoh RS5C372A, I2C, no battery Flash instruction (UART+TFTP): 1. Downgrade the OEM firmware to 1.34 version (BUFFALO_BOOTVER=0.13) 2. Remove any hard drive from inside the bays. 3. Boot the Openwrt initramfs image using the U-Boot serial console: tftpboot 0x1200000 buffalo_ls421de-initramfs-kernel.bin bootm 0x1200000 4. Flash the sysupgrade image using the Openwrt console: sysupgrade -n buffalo_ls421de-squashfs-sysupgrade.bin 5. Wait until it finish, the device will reboot with Openwrt installed on the NAND flash. Note: - Device shuting down doesn't work, even if the power slide switch is used. We must first, via MDIO, set the unused LED2 at the ethernet phy0 to off state. Reboot works ok. Signed-off-by: Daniel González Cabanelas <dgcbueu@gmail.com> Reviewed-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* mvebu: cortexa9: correct cpu subtypeTomasz Maciej Nowak2020-03-281-1/+1
| | | | | | | | | | | | | | | Armada 370 processors have only 16 double-precision registers. The change introduced by 8dcc1087602e ("toolchain: ARM: Fix toolchain compilation for gcc 8.x") switched accidentally the toolchain for mvebu cortexa9 subtarget to cpu type with 32 double-precision registers. This stems from gcc defaults which assume "vfpv3-d32" if only "vfpv3" as mfpu is specified. That change resulted in unusable image, in which kernel will kill userspace as soon as it causing "Illegal instruction". Ref: https://forum.openwrt.org/t/gcc-was-broken-on-mvebu-armada-370-device-after-commit-on-2019-03-25/43272 Fixes: 8dcc1087602e ("toolchain: ARM: Fix toolchain compilation for gcc 8.x") Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* treewide: gather DEVICE_VARS into one placeSungbo Eo2020-03-211-1/+1
| | | | | | | | | | | Place DEVICE_VARS assignments at the top of the file or above Device/Default to make them easier to find. For ramips, remove redundant values already present in parent file. Signed-off-by: Sungbo Eo <mans0n@gorani.run> [do not touch ar71xx, extend commit message] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* 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>