aboutsummaryrefslogtreecommitdiffstats
path: root/target
Commit message (Collapse)AuthorAgeFilesLines
* lantiq/xrx200: make WLAN button responsive on Fritzbox 7360 & 7362Dustin Gathmann2020-07-202-2/+2
| | | | | | | | | | | | | Pressing the 'WLAN' button should enable/disable wireless activity. Currently, the button is mapped to the KEY_WLAN, which will not have this effect. This patch changes the mapping of the WLAN button, so a button press will emit an action for the 'rfkill' key instead of 'wlan'. Apparently, this is what stock OpenWRT expects. This fix is analogous to the preceding patch for Fritzbox 3370. Signed-off-by: Dustin Gathmann <dzsoftware@posteo.org>
* lantiq/xrx200: fix WLAN button actions for Fritzbox 3370Dustin Gathmann2020-07-202-2/+2
| | | | | | | | | | | | The WLAN button actions are reversed, i.e. pressing the button emits a 'released' action, and vice versa. This can easily be checked by adding logger -t button_action "$BUTTON $ACTION" as the second line of /etc/rc.button/rfkill, and using logread to read the events (assuming the preceding patch has been applied). Defining the GPIO as ACTIVE_LOW corrects this behavior. Signed-off-by: Dustin Gathmann <dzsoftware@posteo.org>
* lantiq/xrx200: make WLAN button responsive on Fritzbox 3370Dustin Gathmann2020-07-202-2/+2
| | | | | | | | | | | Pressing the 'WLAN' button should enable/disable wireless activity. However, on the Fritzbox 3370 this doesn't have an effect. This patch changes the mapping of the physical WLAN button, so a button press will emit an action for the 'rfkill' key instead of 'wlan'. Apparently, this is what stock OpenWRT expects, and also what is implemented for most other devices. Signed-off-by: Dustin Gathmann <dzsoftware@posteo.org>
* ramips: fix flash layout for TP-Link TL-WR841N v14Alexander Müller2020-07-192-2/+8
| | | | | | | | | | | | | | | | The config partition was missing from the flash layout of the device. Although the stock firmware resets a corrupted config partition to the default values, the TFTP flash with an image bigger than 0x3d0000 will truncate the image as the bootloader only copies 0x3d0000 bytes to flash during TFTP flashing. Fixed by adding the config partition and shrinking the firmware partition. Fixes: 3fd97c522bb7 ("ramips: add support for TP-Link TL-WR841n v14") Signed-off-by: Alexander Müller <donothingloop@gmail.com>
* ramips: remove incorrect mtd-eeprom for TP-Link TL-WR841N v14Adrian Schmutzler2020-07-191-1/+1
| | | | | | | | | | | | | | | | | The factory partition on this device is only 64k in size, so having mediatek,mtd-eeprom = <&factory 0x10000> would place the EEPROM data after the end of the flash. As can be verified against the TP-Link GPL sources, which contain the EEPROM data as binary blob, the actual address for the EEPROM data is 0x0. Since 0x0 is default for MT7628, the incorrect line is just removed. This error is the reason for the abysmal Wifi performance that people are complaining about for the WR841Nv14. Fixes: 3fd97c522bb7 ("ramips: add support for TP-Link TL-WR841n v14") Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: don't create switch config for VIXMINIDavid Bauer2020-07-181-5/+2
| | | | | | | | | Don't create UCI switch config for the GL.iNet microuter-N300 and VIXMINI. These devices only have a single LAN port. Creating the switch config makes usage of VLANs more complicated, as they would have to be configured on the MAC as well as the "switch". Signed-off-by: David Bauer <mail@david-bauer.net>
* lantiq: move 01_led_migration script to subtargetsAdrian Schmutzler2020-07-173-7/+61
| | | | | | | | | | | | Split the /etc/uci-defaults/01_led_migration scripts into subtargets as already done for most of the other base-files. While this introduces a minor amount of code duplication, it still is considered an improvement, as device-specific settings are kept together in the subtargets' base-files and the script at hand can be removed entirely for two of the subtargets not needing it. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: move dsl related base-files into own packageMartin Schiller2020-07-174-824/+0
| | | | | | | | | | It does not make sense to install this components on lantiq systems where the dsl subsystem is not needed/used. This also makes it possible to use the files also on other targets. (hopefully ipq401x / FritzBox 7530 in the near future) Signed-off-by: Martin Schiller <ms.3headeddevs@gmail.com>
* ramips: move redundant console setup to mt7621 SoC DTSIAdrian Schmutzler2020-07-1747-181/+4
| | | | | | | | | | | | | | | | | For mt7621, console is set up via DTS bootargs individually in device DTS/DTSI files. However, 44 of 74 statements use the following setting: chosen { bootargs = "console=ttyS0,57600"; }; Therefore, don't repeat ourselves and move that definition to the SoC DTSI file to serve as a default value. This patch is cosmetic. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* kernel: bump 5.4 to 5.4.52John Audia2020-07-1724-133/+103
| | | | | | | | | 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>
* ramips: add arl_table support for MT7530Salvatore Mesoraca2020-07-171-0/+119
| | | | | | | Use switch.h API to expose MT7530's ARL table to user space. Signed-off-by: Salvatore Mesoraca <salvatore@samknows.com>
* 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>
* ramips: add support for D-Link DIR-867/DIR-882 A1Mateus B. Cassiano2020-07-166-152/+275
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds support for D-Link DIR-867 A1 and D-Link DIR-882 A1. Given the similarity of these devices, this patch also introduces a common DTS shared between DIR-867 A1, DIR-878 A1 and DIR-882 A1. Specifications: * Board: AP-MTKH7-0002 * SoC: MediaTek MT7621AT * RAM: 128 MB (DDR3) * Flash: 16 MB (SPI NOR) * WiFi: MediaTek MT7615N (x2) * Switch: 1 WAN, 4 LAN (Gigabit) * Ports: 1 USB 2.0, 1 USB 3.0 * Buttons: Reset, WiFi Toggle, WPS * LEDs: Power (green/orange), Internet (green/orange), WiFi 2.4G (green), WiFi 5G (green), USB 2.0 (green), USB 3.0 (green) Notes: * WiFi 2.4G and WiFi 5G LEDs are wired directly to the wireless chips * DIR-867 wireless chips are limited to 3x3 streams at hardware level * USB ports and related LEDs available only on DIR-882 Serial port: * Parameters: 57600, 8N1 * Location: J1 header (close to the Reset, WiFi and WPS buttons) * Pinout: 1 - VCC 2 - RXD 3 - TXD 4 - GND Installation: * D-Link Recovery GUI: power down the router, press and hold the reset button, then re-plug it. Keep the reset button pressed until the power LED starts flashing orange, manually assign a static IP address under the 192.168.0.xxx subnet (e.g. 192.168.0.2) and go to http://192.168.0.1 * Some modern browsers may have problems flashing via the Recovery GUI, if that occurs consider uploading the firmware through cURL: curl -v -i -F "firmware=@file.bin" 192.168.0.1 Signed-off-by: Mateus B. Cassiano <mbc07@live.com> [move DEVICE_VARIANT to individual definitions] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: add support for Linksys EA7300 v1Santiago Rodriguez-Papa2020-07-169-159/+238
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Specifications: * SoC: MediaTek MT7621A (880 MHz 2c/4t) * RAM: Nanya NT5CC128M16IP-DIT (256M DDR3-1600) * Flash: Macronix MX30LF1G18AC-TI (128M NAND) * Eth: MediaTek MT7621A (10/100/1000 Mbps x5) * Radio: MT7615N (2.4 GHz & 5 GHz) 4 antennae: 1 internal and 3 non-deatachable * USB: 3.0 (x1) * LEDs: White (x1 logo) Green (x6 eth + wps) Orange (x5, hardware-bound) * Buttons: Reset (x1) WPS (x1) Everything works! Been running it for a couple weeks now and haven't had any problems. Please let me know if you run into any. Installation: Flash factory image through GUI. This might fail due to the A/B nature of this device. When flashing, OEM firmware writes over the non-booted partition. If booted from 'A', flashing over 'B' won't work. To get around this, you should flash the OEM image over itself. This will then boot the router from 'B' and allow you to flash OpenWRT without problems. Reverting to factory firmware: Hard-reset the router three times to force it to boot from 'B.' This is where the stock firmware resides. To remove any traces of OpenWRT from your router simply flash the OEM image at this point. Signed-off-by: Santiago Rodriguez-Papa <contact@rodsan.dev> [use v1 only, minor DTS adjustments, use LINKSYS_HWNAME and add it to DEVICE_VARS, wrap DEVICE_PACKAGES, adjust commit message/title] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: provide common definition for ELECOM WRC GS devicesAdrian Schmutzler2020-07-167-35/+24
| | | | | | | | | | | | | | Add a common definition for ELECOM WRC "GS" devices to mt7621.mk to not repeat the same assignments five times. To keep the naming consistent, slightly rename the DTSI and the factory image recipe as well. Note that elecom_wrc-1167ghbk2-s uses a slightly different build recipe for the factory image, so we keep it separate. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> Tested-by: INAGAKI Hiroshi <musashino.open@gmail.com> [WRC-1750GSV]
* ramips: add support for ELECOM WRC-1750GS/GSVINAGAKI Hiroshi2020-07-163-0/+106
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ELECOM WRC-1750GS is a 2.4/5 GHz band 11ac (Wi-Fi 5) router, based on MT7621A. WRC-1750GSV has the same hardware with WRC-1750GS. Specification: - SoC : MediaTek MT7621A - RAM : DDR3 128 MiB - Flash : SPI-NOR 16 MiB - WLAN : 2.4/5 GHz 3T3R (2x MediaTek MT7615) - Ethernet : 10/100/1000 Mbps x5 - Switch : MediaTek MT7530 (SoC) - LED/keys : 4x/6x (2x buttons, 1x slide-switch) - UART : through-hole on PCB - J4: 3.3V, GND, TX, RX from ethernet port side - 57600n8 - Power : 12VDC, 1.5A Flash instruction using factory image: 1. Boot WRC-1750GS (or WRC-1750GSV) normally 2. Access to "http://192.168.2.1/" and open firmware update page ("ファームウェア更新") 3. Select the OpenWrt factory image and click apply ("適用") button for WRC-1750GS : wrc-1750gs-squashfs-factory.bin for WRC-1750GSV: wrc-1750gsv-squashfs-factory.bin 4. Wait ~120 seconds to complete flashing Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* mediatek: backport latest pci/e driver from upstreamJohn Crispin2020-07-167-24/+1932
| | | | Signed-off-by: John Crispin <john@phrozen.org>
* mediatek: generate UBI images for the rev boardJohn Crispin2020-07-163-2/+48
| | | | Signed-off-by: John Crispin <john@phrozen.org>
* mediatek: minor fix to eip97 driverJohn Crispin2020-07-161-2/+2
| | | | | | This patch makes the driver work on the newer v2.3 core. Signed-off-by: John Crispin <john@phrozen.org>
* ath79: harmonize model names for Ubiquiti devicesAdrian Schmutzler2020-07-1517-27/+26
| | | | | | | | | | | | | | | | | | | | This harmonizes the model names for the ath79 Ubiquiti devices by applying a few minor cosmetic adjustments: - Removes hyphens where they are not found in the product names (Ubiquiti uses hyphens only for the abbreviated version names like UAP-AC-PRO which we don't use anyway.) - Add (XM) suffix for DTS model strings to help with distinguishing them from their XW counterparts. - Remove DEVICE_VARIANT for LAP-120 which actually was an alternate device name. - Generally make DTS model names and those from generic-ubnt.mk more consistent. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: add support for Ubiquiti PowerBridge MVieno Hakkerinen2020-07-155-0/+28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds support for the Ubiquiti PowerBridge M, which has the same board/LEDs as the Bullet M XM, but different case and antennas. Specifications: - AR7241 SoC @ 400 MHz - 64 MB RAM - 8 MB SPI flash - 1x 10/100 Mbps Ethernet, 24 Vdc PoE-in - Internal antenna: 25 dBi - POWER/LAN green LEDs - 4x RSSI LEDs (red, orange, green, green) - UART (115200 8N1) on PCB Flashing via WebUI: Upload the factory image via the stock firmware web UI. Attention: airOS firmware versions >= 5.6 have a new bootloader with an incompatible partition table! Please downgrade to <= 5.5 _before_ flashing OpenWrt! Refer to the device's Wiki page for further information. Flashing via TFTP: Same procedure as other Bullet M (XM) boards. - Use a pointy tool (e.g., pen cap, paper clip) and keep the reset button on the device or on the PoE supply pressed - Power on the device via PoE (keep reset button pressed) - Keep pressing until LEDs flash alternatively LED1+LED3 => LED2+LED4 => LED1+LED3, etc. - Release reset button - The device starts a TFTP server at 192.168.1.20 - Set a static IP on the computer (e.g., 192.168.1.21/24) - Upload via tftp the factory image: $ tftp 192.168.1.20 tftp> bin tftp> trace tftp> put openwrt-ath79-generic-xxxxx-ubnt_powerbridge-m-squashfs-factory.bin Signed-off-by: Vieno Hakkerinen <vieno@hakkerinen.eu>
* ipq40xx: fix ethernet vlan double taggingJohn Crispin2020-07-142-11/+36
| | | | | | | | As the the SoC uses implicit vlan tagging for dual MAC support, the offload feature breaks when using double tagging. Signed-off-by: Sven Eckelmann <sven@narfation.org> Signed-off-by: John Crispin <john@phrozen.org>
* ipq40xx: merge all ar40xx patches into one single patchJohn Crispin2020-07-142-30/+22
| | | | Signed-off-by: John Crispin <john@phrozen.org>
* ipq806x: really fix aliases node for Qualcomm IPQ8064/DB149Adrian Schmutzler2020-07-142-2/+12
| | | | | | | | | | | | | | | Having looked at this again, it appears that only gsbi2_serial is actually enabled for this device, so the entry in the broken aliases node was correct. Therefore, this needs to set its own serial0 instead of inheriting "serial0 = &gsbi4_serial;" from DTSI. Do this with the correctly named aliases node now. Fixes: c83f7b6d217f ("ipq806x: fix aliases node name for Qualcomm IPQ8064/DB149") Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ipq806x: use consistent DT labels for gsbiX_serialAdrian Schmutzler2020-07-142-4/+4
| | | | | | | | | | Kernel uses the label gsbiX_serial, so let's adjust our labels to this naming scheme. This is cosmetic, and actually only already existing gsbi4_serial has been used at all. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ipq806x: fix aliases node name for Qualcomm IPQ8064/DB149Adrian Schmutzler2020-07-142-11/+1
| | | | | | | | | | | | | | | | | | | | | | | This device uses a node incorrectly named "alias" instead of "aliases" since it was introduced. Remove it without replacement, as the definitions in it don't seem to be required anyway: The serial0 definition has never been effective anyway and this would be the only device deviating from the common setting "serial0 = &gsbi4_serial;" for ipq8064. (So, maybe the wrong node prevented us from finding out about the wrong serial definition?) The mdio-gpio0 alias was supposed to be removed in d2a2eb7e48f6 anyway, the redundant definition in the alias node was just overlooked back then. Fixes: 0fd202f3e563 ("ipq806x: add db149 dts files") Fixes: d2a2eb7e48f6 ("ipq806x: replace caf nss-gmac driver by upstream stmmac") Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: use rgmii-id instead of rgmii in ubnt,lap-120Roger Pueyo Centelles2020-07-131-3/+2
| | | | | | | | | | | Since commit 6f2e1b7485 (ath79: disable delays on AT803X config init) the incoming incoming traffic on the ubnt,lap-120 devices Ethernet port was not making it through. Using rgmii-id instead of rgmii (same configuration as ubnt,litebeam-ac-gen2) fixes it. Fixes FS#2893. Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>
* ramips: add support for D-Link DIR-878 A1Mathieu Martin-Borret2020-07-133-1/+198
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Specifications: SoC: MT7621AT RAM: 128MB Flash: 16MB NOR SPI flash WiFi: MT7615N (2.4GHz) and MT7615N (5Ghz) LAN: 5x1000M Firmware layout is Uboot with extra 96 bytes in header Base PCB is AP-MTKH7-0002 LEDs Power Green,Power Orange,Internet Green,Internet Orange LEDs "2.4G" Green & "5G" Green connected directly to wifi module Buttons Reset,WPS,WIFI Flashing instructions: Upload image via emergency recovery mode Push and hold reset button (on the back of the device) until power led starts flashing (about 10 secs or so) while powering the device on. Give it ~30 seconds, to boot the recovery mode GUI Connect your client computer to LAN1 of the device Set your client IP address manually to 192.168.0.2 / 255.255.255.0. Call the recovery page for the device at http://192.168.0.1 Use the provided emergency web GUI to upload and flash a new firmware to the device. Some browsers/OS combinations are known not to work, so if you don't see the percentage complete displayed and moving within a few seconds, restart the procedure from scratch and try anoher one, or try the command line way. Alternative method using command line on Linux: curl -v -i -F "firmware=@openwrt-xxxx-squashfs-factory.bin" 192.168.0.1 Signed-off-by: Mathieu Martin-Borret <mathieu.mb@protonmail.com> [use of generic uimage-padhdr in image generation code] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* kernel: mtdsplit_uimage: add SGE parserMathieu Martin-Borret2020-07-131-0/+38
| | | | | | | Adding SGE parser for SGE (T&W) Shenzhen Gongjin Electronics to add 96 bytes padding the the firmware image Signed-off-by: Mathieu Martin-Borret <mathieu.mb@protonmail.com>
* rockchip: don't disable timer LED triggerDavid Bauer2020-07-131-1/+0
| | | | | | | | The timer LED trigger is enabled in all targets (except for lantiq xway-legacy). It's necessary for the OpenWrt preinit LED pattern to work. Signed-off-by: David Bauer <mail@david-bauer.net>
* rockchip: use downstream GPIO button implementationDavid Bauer2020-07-132-2/+1
| | | | | | | | Use the OpenWrt netlink GPIO button implementation to forward button presses to procd. This is necessary to make failsafe-mode access using a button possible. Signed-off-by: David Bauer <mail@david-bauer.net>
* bcm47xx: disable image for Linksys WRT160n v3Adrian Schmutzler2020-07-131-0/+1
| | | | | | | | | | | | The device can only hold 3.6 MB, but newer images (since 18.06) are bigger, so flashing a new version fails. This disables default build for this device based on the bug report referenced below. Fixes: FS#1963 Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: consolidate Netgear devices for mt7628Adrian Schmutzler2020-07-137-283/+151
| | | | | | | | | | | | | | | This creates a common DTSI and shared image definition for the relatively similar Netgear devices for mt7628 platform. As a side effect, this raises SPI flash frequency for the R6120, as it's expected to work there as well if it works for R6080 and R6020. Based on the data from the other devices, it also seems probable the 5g MAC address for R6120 could be extracted from the caldata, and the mtd-mac-address there could be dropped. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: fix dsa binding for TP-Link TL-WR941ND v2Chuanhong Guo2020-07-122-13/+9
| | | | | | | | | upstream changed dt-bindings for marvell 88e6060 to use mdio-device and dropped support for legacy bindings. fix it in our local dts. Fixes: FS#2524 Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
* ath79: qihoo,c301: use phy-supply for usb vbusChuanhong Guo2020-07-121-2/+2
| | | | | | | | Linux phy subsystem provides support for a phy regulator defined via phy-supply property. Use it to turn on usb power only when usb is probed. Signed-off-by: Chuanhong Guo <gch981213@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>
* ramips: consolidate recipes with uimage_padhdrAdrian Schmutzler2020-07-113-13/+8
| | | | | | | | | | | There are already two very similar recipes using uimage_padhdr in ramips target, and a third one is about to be added. Make the recipe more generic, so redefinitions are not necessary anymore. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> Tested-by: Bjørn Mork <bjorn@mork.no> [Zyxel WAP6805]
* 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>
* bcm63xx: R5010UNv2: fix flash partitions for 16MB flashDaniel González Cabanelas2020-07-111-5/+5
| | | | | | | | | | | The router Nucom R5010UN v2 has the partitions defined for a 8MB flash, but the flash chip is 16MB size. We are wasting half of the flash. Fix it and use generic names for partitions. Fixes: 474cde61234c ("brcm63xx: probe SPI flash through DT") Signed-off-by: Daniel González Cabanelas <dgcbueu@gmail.com>
* build: improve ccache supportRoman Yeryomin2020-07-112-7/+3
| | | | | | | | | | | | | | | | | | Set CCACHE_DIR to $(TOPDIR)/.ccache and CCACHE_BASEDIR to $(TOPDIR). This allows to do clean and dirclean. Cache hit rate for test build after dirclean is ~65%. If CCACHE is enabled stats are printed out at the end of building process. CCACHE_DIR config variable allows to override default, which could be useful when sharing cache with many builds. cacheclean make target allows to clean the cache. Changes from v1: - remove ccache directory using CCACHE_DIR variable - remove ccache leftovers from sdk and toolchain make files - introduce CONFIG_CCACHE_DIR variable - introduce cacheclean make target Signed-off-by: Roman Yeryomin <roman@advem.lv>
* ramips: mt7621: refactor set affinity scriptDENG Qingfang2020-07-111-19/+7
| | | | | | | | The current one only looks for mt76x2e and mt7603e, and does not work for 2 or more same Wi-Fi chips. Refactor the script to cover those cases. Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>
* layerscape: define IMAGE_SIZE and LS_SYSUPGRADE_IMAGE_SIZEYangbo Lu2020-07-113-10/+18
| | | | | | | | | Define 64m IMAGE_SIZE for flash firmware.bin since the flash size is 64MB. Define 48m LS_SYSUPGRADE_IMAGE_SIZE for flash sysupgrade.bin which contains maximum 16MB kernel and 32MB rootfs according to memory map. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: support sysupgrade for SD card ext4 rootfsYangbo Lu2020-07-114-6/+141
| | | | | | Support sysupgrade for SD card ext4 rootfs. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: support sysupgrade for squashfs rootfsYangbo Lu2020-07-113-7/+29
| | | | | | | Support sysupgrade for all Layerscape boards with squashfs rootfs. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: fix board name for SD card bootYangbo Lu2020-07-111-0/+13
| | | | | | | | | Many Layerscape boards support both flash boot and SD card boot. And different firmware and sysupgrade.bin are built for the two boot methods. To identify them, a fix could be done on board name by adding a postfix "-sdboot" for SD card boot. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: add compatible for board ls1043ardbYangbo Lu2020-07-111-0/+28
| | | | | | Backport a dts patch which added compatible for ls1043ardb. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: convert to squashfs rootfs for QSPI NOR bootYangbo Lu2020-07-111-17/+5
| | | | | | | | | | | There had been an issue in Layerscape QSPI driver for very long time, which made squashfs,jffs2 rootfs not work on QSPI NOR. And the ubifs had been used as a workaround. Now the issue has been fixed. So convert to use squashfs,jffs2 rootfs on QSPI NOR for Layerscape boards (LS1012ARDB/LS1046ARDB/ LS1088ARDB), and update u-boot bootargs for booting. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* toolchain/wrapper.sh: fix remaining shellcheck warningsPetr Štetiar2020-07-111-8/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixes following warnings: In target/toolchain/files/wrapper.sh line 18: REALNAME=$(readlink -f $0) ^-- SC2086: Double quote to prevent globbing and word splitting. -- In target/toolchain/files/wrapper.sh line 20: REALNAME_BASE=$(basename $REALNAME) ^-------^ SC2086: Double quote to prevent globbing and word splitting. -- In target/toolchain/files/wrapper.sh line 21: REALNAME_DIR=$(dirname $REALNAME) ^-------^ SC2086: Double quote to prevent globbing and word splitting. -- In target/toolchain/files/wrapper.sh line 74: exec $TARGET_TOOLCHAIN_TRIPLET-$BINARY.bin $GCC_SYSROOT_FLAGS $TARGET_FUNDAMENTAL_CFLAGS $TARGET_ROOTFS_CFLAGS "$@" ^-----------------------^ SC2086: Double quote to prevent globbing and word splitting. -- In target/toolchain/files/wrapper.sh line 77: exec $TARGET_TOOLCHAIN_TRIPLET-$BINARY.bin $LD_SYSROOT_FLAGS $TARGET_FUNDAMENTAL_LDFLAGS "$@" ^-----------------------^ SC2086: Double quote to prevent globbing and word splitting. -- In target/toolchain/files/wrapper.sh line 80: exec $TARGET_TOOLCHAIN_TRIPLET-$BINARY.bin $TARGET_FUNDAMENTAL_ASFLAGS "$@" ^-----------------------^ SC2086: Double quote to prevent globbing and word splitting. -- In target/toolchain/files/wrapper.sh line 83: exec $TARGET_TOOLCHAIN_TRIPLET-$BINARY.bin "$@" ^-----------------------^ SC2086: Double quote to prevent globbing and word splitting. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* toolchain/wrapper.sh: Replace read with read -rRosen Penev2020-07-111-1/+1
| | | | | | | | Without -r, backslashes would get mangled. Found with shellcheck. Signed-off-by: Rosen Penev <rosenp@gmail.com>
* ramips: kernel: fix awake-rt305x-dwc2 patchAlexey Dobrovolsky2020-07-111-7/+7
| | | | | | | | | | | | | At this point in v5.4 kernel we cannot use dwc2_readl() and dwc2_writel() since they rely on the value hsotg->needs_byte_swap which cannot be obtained before the controller wakes up. We should use readl() and writel() to wake up the controller before calling dwc2_check_core_endianness(). Fixes: 6be0da90a165 ("ramips: refresh patches") Signed-off-by: Alexey Dobrovolsky <dobrovolskiy.alexey@gmail.com> [fixed Fixes: tag] Signed-off-by: Petr Štetiar <ynezz@true.cz>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-02 10:14:46 +0000