aboutsummaryrefslogtreecommitdiffstats
path: root/target
Commit message (Collapse)AuthorAgeFilesLines
* mvebu: add Globalscale MOCHAbinRobert Marko2021-10-025-0/+469
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Globalscale MOCHAbin is a Armada 7040 based development board. Specifications: * Armada 7040 Quad core ARMv8 Cortex A-72 @ 1.4GHz * 2 / 4 / 8 GB of DDR4 DRAM * 16 GB eMMC * 4MB SPI-NOR (Bootloader) * 1x M.2-2280 B-key socket (for SSD expansion, SATA3 only) * 1x M.2-2250 B-key socket (for modems, USB2.0 and I2C only) * 1x Mini-PCIe 3.0 (x1, USB2.0 and I2C) * 1x SATA 7+15 socket (SATA3) * 1x 16-pin (2×8) MikroBus Connector * 1x SIM card slot (Connected to the mini-PCIe and both M.2 slots) * 2x USB3.0 Type-A ports via SMSC USB5434B hub * Cortex 2x5 JTAG * microUSB port for UART (PL2303GL/PL2303SA onboard) * 1x 10G SFP+ * 1x 1G SFP (Connected to 88E1512 PHY) * 1x 1G RJ45 with PoE PD (Connected to 88E1512 PHY) * 4x 1G RJ45 ports via Topaz 88E6141 switch * RTC with battery holder (SoC provided, requires CR2032 battery) * 1x 12V DC IN * 1x Power switch * 1x 12V fan header (3-pin, power only) * 1x mini-PCIe LED header (2x0.1" pins) * 1x M.2-2280 LED header (2x0.1" pins) * 6x Bootstrap jumpers * 1x Power LED (Green) * 3x Tri-color RGB LEDs (Controllable) * 1x Microchip ATECC608B secure element Note that 1G SFP and 1G WAN cannot be used at the same time as they are in parallel connected to the same PHY. Installation: Copy dtb from build_dir to bin/ and run tftpserver there: $ cp ./build_dir/target-aarch64_cortex-a72_musl/linux-mvebu_cortexa72/image-armada-7040-mochabin.dtb bin/targets/mvebu/cortexa72/ $ in.tftpd -L -s bin/targets/mvebu/cortexa72/ Connect to the device UART via microUSB port and power on the device. Power on the device and hit any key to stop the autoboot. Set serverip (host IP) and ipaddr (any free IP address on the same subnet), e.g: $ setenv serverip 192.168.1.10 # Host $ setenv ipaddr 192.168.1.15 # Device Set the ethernet device (Example for the 1G WAN): $ setenv ethact mvpp2-2 Ping server to confirm network is working: $ ping $serverip Using mvpp2-2 device host 192.168.1.15 is alive Tftpboot the firmware: $ tftpboot $kernel_addr_r openwrt-mvebu-cortexa72-globalscale_mochabin-initramfs-kernel.bin $ tftpboot $fdt_addr_r image-armada-7040-mochabin.dtb Boot the image: $ booti $kernel_addr_r - $fdt_addr_r Once the initramfs is booted, transfer openwrt-mvebu-cortexa72-globalscale_mochabin-squashfs-sdcard.img.gz to /tmp dir on the device. Gunzip and dd the image: $ gunzip /tmp/openwrt-mvebu-cortexa72-globalscale_mochabin-squashfs-sdcard.img.gz $ dd if=/tmp/openwrt-mvebu-cortexa72-globalscale_mochabin-squashfs-sdcard.img of=/dev/mmcblk0 && sync Reboot the device. Hit any key to stop the autoboot. Reset U-boot env and set the bootcmd: $ env default -a $ setenv bootcmd 'load mmc 0 ${loadaddr} boot.scr && source ${loadaddr}' Optionally I would advise to edit the console env variable to remove earlycon as that causes the kernel to never use the driver for the serial console. Earlycon should be used only for debugging before the kernel can configure the console and will otherwise cause various issues with the console. $ setenv console 'console=ttyS0,115200' Save and reset $ saveenv $ reset OpenWrt should boot from eMMC now. Signed-off-by: Robert Marko <robert.marko@sartura.hr>
* lantiq: kernel: xway-nand: Move ECC engine setting to new DT bindingDaniel Kestrel2021-10-0213-7/+50
| | | | | | | | | | | | | | | | When trying to add support for another device with Micron NAND chips, it was discovered that the default setting in the kernel source does not work with Micron Chips, since the device trees setting is overwritten and hard coded by the kernel xway_nand driver. This was the original reason for this PR. A kernel patch sets the default ECC mode to soft without overwriting the device tree settings and the device tree for devices using it are updated with new parameters because the old ones are deprecated by torvalds/linux@533af69. A patch for kernel 5.4 is provided to support the new settings because kernel 5.4 does not support it. Signed-off-by: Daniel Kestrel <kestrel1974@t-online.de>
* lantiq: kernel: xway-nand: Fix setting on-die ECC engines in dtsHauke Mehrtens2021-10-022-2/+70
| | | | | | | This backports a fix proposed for upstream kernel to fix overwriting the NAND ECC engine in device tree. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* mediatek: mt7623: bpi-r2: add LED aliasesDaniel Golle2021-10-011-0/+29
| | | | | | Add aliases for LEDs in device tree of the BPi-R2. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* mediatek: remove files and patches for Linux 5.4Daniel Golle2021-10-01183-111722/+0
| | | | | | | All subtargets only provide files and patches for Linux 5.10 by now so there is little use for the old Linux 5.4 stuff. Remove it. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* armvirt: switch to Kernel 5.10Paul Spooren2021-10-011-2/+1
| | | | | | | | | | | | Armvirt is a development and testing platform and should therefore use the latest OpenWrt Kernel by default. Tested via qemu. Acked-by: Rosen Penev <rosenp@gmail.com> Acked-by: Yousong Zhou <yszhou4tech@gmail.com> Signed-off-by: Paul Spooren <mail@aparcar.org>
* malta: switch to Kernel 5.10Paul Spooren2021-10-011-2/+1
| | | | | | | | | | Malta is a development and testing platform and should therefore use the latest OpenWrt Kernel by default. Acked-by: Rosen Penev <rosenp@gmail.com> Acked-by: Yousong Zhou <yszhou4tech@gmail.com> Signed-off-by: Paul Spooren <mail@aparcar.org>
* mediatek: add FEATURES and order them alphabeticallyDaniel Golle2021-09-302-2/+2
| | | | | | | | Add common features 'gpio', 'nand', 'pci', 'pcie', 'squashfs' and 'usb' for all mediatek targets, add 'display' and 'usbgadget' for MT7623. Sort features alphabetically while at it. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* mediatek: mt7622: provide power on mPCIe in SATA modeDaniel Golle2021-09-301-17/+2
| | | | | | | | | User reported that R64 doesn't provide power to the mPCIe slot in case the PCIe port is disabled as it is when selecting the SATA configuration. As users may still want to use USB-connected mPCIe modules in CN8 slot. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* kernel: bump 5.10 to 5.10.70Rui Salvaterra2021-09-307-52/+11
| | | | | | | Deleted (upstreamed): bcm53xx/patches-5.10/181-Revert-USB-bcma-Add-a-check-for-devm_gpiod_get.patch Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com>
* kernel: bump 5.10 to 5.10.69Rui Salvaterra2021-09-304-24/+1
| | | | | | Patches automatically refreshed. Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com>
* kernel: bump 5.10 to 5.10.68Rui Salvaterra2021-09-3021-534/+25
| | | | | | | | | | | | | Deleted (upstreamed): generic/backport-5.10/610-v5.13-02-netfilter-Fix-fall-through-warnings-for-Clang.patch generic/backport-5.10/792-v5.15-0001-net-dsa-b53-Fix-calculating-number-of-switch-ports.patch generic/backport-5.10/792-v5.15-0002-net-dsa-b53-Set-correct-number-of-ports-in-the-DSA-s.patch generic/backport-5.10/792-v5.15-0003-net-dsa-b53-Fix-IMP-port-setup-on-BCM5301x.patch generic/backport-5.10/840-0001-PCI-of-Don-t-fail-devm_pci_alloc_host_bridge-on-miss.patch generic/backport-5.10/840-0002-PCI-iproc-Fix-BCMA-probe-resource-handling.patch generic/pending-5.10/498-mtd-mtdconcat-select-readwrite-function.patch Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com>
* kernel: bump 5.10 to 5.10.67Rui Salvaterra2021-09-3017-69/+27
| | | | | | | Deleted (upstreamed): bcm27xx/patches-5.10/950-0312-vc4_hdmi-Set-HD_CTL_WHOLSMP-and-HD_CTL_CHALIGN_SET.patch Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com>
* kernel: bump 5.10 to 5.10.65Rui Salvaterra2021-09-3020-64/+72
| | | | | | | | | Manually refreshed: generic/pending-5.10/800-bcma-get-SoC-device-struct-copy-its-DMA-params-to-th.patch bcm27xx/patches-5.10/950-0053-firmware-bcm2835-Support-ARCH_BCM270x.patch bcm27xx/patches-5.10/950-0087-firmware-raspberrypi-Add-backward-compatible-get_thr.patch Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com>
* ramips: add support for Netgear R7450Dale Hui2021-09-264-1/+30
| | | | | | | | | | | | | | | | | | | | | | | | | Netgear R7450 is a clone of Netgear R6700v2 Specifications ============== SoC: MediaTek MT7621AT RAM: 256M DDR3 FLASH: 128M NAND WiFi: MediaTek MT7615N an+ac MediaTek MT7615N bgn ETH: MediaTek MT7621AT BTN: 1x Connect (WPS), 1x WLAN, 1x Reset LED: Power (white/amber), WAN(white/amber), 2.4G(white), 5G(white), USB(white) , GuestWifi(white) 4x LAN(white/amber), Wifi Button(white), WPS Button(white) Flash Instructions ================== Login to netgear webinterface and flash factory.img Signed-off-by: Dale Hui <strokes-races0b@icloud.com> [fix model/compatible in DTS] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: add support for Netgear R6900v2Dale Hui2021-09-264-0/+30
| | | | | | | | | | | | | | | | | | | | | | | Netgear R6900v2 is a clone of Netgear R6700v2 Specifications ============== SoC: MediaTek MT7621AT RAM: 256M DDR3 FLASH: 128M NAND WiFi: MediaTek MT7615N an+ac MediaTek MT7615N bgn ETH: MediaTek MT7621AT BTN: 1x Connect (WPS), 1x WLAN, 1x Reset LED: Power (white/amber), WAN(white/amber), 2.4G(white), 5G(white), USB(white) , GuestWifi(white) 4x LAN(white/amber), Wifi Button(white), WPS Button(white) Flash Instructions ================== Login to netgear webinterface and flash factory.img Signed-off-by: Dale Hui <strokes-races0b@icloud.com>
* ramips: add Nighthawk AC2100 as name for Netgear R6700v2Dale Hui2021-09-261-0/+3
| | | | | | | | Netgear Nighthawk AC2100 is another name of the Netgear R6700v2. Signed-off-by: Dale Hui <strokes-races0b@icloud.com> [adjust commit message/title] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: make Netgear R7200 a separate device from R6700v2Dale Hui2021-09-264-4/+30
| | | | | | | | | With the various variants of Netgear R**** devices, make it more obvious which image should be used for the R7200. Signed-off-by: Dale Hui <strokes-races0b@icloud.com> [provide proper commit message] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* realtek: add Kernel 5.10 as testing versionINAGAKI Hiroshi2021-09-261-0/+1
| | | | | | | This patch adds "KERNEL_TESTING_PATCHVER:=5.10" to the Makefile in realtek target to allow using Kernel 5.10 for testing. Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* realtek: enable uart1 on the devices with PoE support in 5.10INAGAKI Hiroshi2021-09-267-0/+28
| | | | | | | | | | | | | | | | On the devices with PoE support, the secondary UART (uart1) on the SoC is used to communicate between the SoC and controller. Enable the secondary UART on the following devices: - D-Link DGS-1210-10P - Netgear GS110TPP v1 - Netgear GS310TP v1 - ZyXEL GS1900-8HP v1/v2 - ZyXEL GS1900-10HP - ZyXEL GS1900-24HP v2 Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* realtek: use physical addresses in soc dtsi in 5.10INAGAKI Hiroshi2021-09-262-12/+12
| | | | | | Use physical addresses instead of virtual address in dts files. Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* realtek: use gpio-keys instead of "-polled" if SoC GPIO is used in 5.10INAGAKI Hiroshi2021-09-262-4/+2
| | | | | | | | The new backported GPIO driver supports interrupt, so use gpio-keys instead of gpio-keys-polled for keys connected to the internal GPIO controller. Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* realtek: update GPIO bindings in the dts files in dts-5.10INAGAKI Hiroshi2021-09-266-33/+29
| | | | | | | | | | | | | | | | | | | this patch includes the following changes: - adjust mapping for the new driver - GPIO 24 -> GPIO 0 - GPIO 47 -> GPIO 0 (+ disabling system LED) - disable pins in the invalid range (out of the range 0-31 of the new driver) - are these pins on the external RTL8231 (&gpio1)? - GPIO 67 (-> GPIO 3 on &gpio1?) - GPIO 94 (-> GPIO 30 on &gpio1?) - drop "indirect-access-bus-id" property from gpio0 node in device dts files Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* realtek: fix kernel panic in DSA driver for 5.10INAGAKI Hiroshi2021-09-261-2/+8
| | | | | | | | | | dsa_to_port function in 5.10 returns dsa_port from the port list in dsa_switch_tree, but the tree is built when the switch is registered by dsa_register_switch and it's null in rtl83xx_mdio_probe. So, we need to use dsa_to_port after the registration of the switch. Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* realtek: add pinmux node of LED_GLB_CTRL to rtl838x.dtsi in dts-5.10INAGAKI Hiroshi2021-09-261-0/+16
| | | | | | | This patch adds a pinctrl-single pinmux node to allow disabling system LED and enabling GPIO 0 (old driver: GPIO 24). Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* realtek: fix compile errors in dsa driver for 5.10INAGAKI Hiroshi2021-09-262-4/+9
| | | | | | | | | | | | | | | | | | | | | | | | | this patch fixes the following errors when compiling: - dsa_switch_alloc is removed[1] - a parameter "enum dsa_tag_protocol mprot" is added to dsa_tag_protocol in dsa_switch_ops (include/net/dsa.h) - several paramters are added to "phylink_mac_link_up" in dsa_switch_ops (include/net/dsa.h) added: - int speed - int duplex - bool tx_pause - bool rx_pause - a parameter "struct switchdev_trans *trans" is added to port_vlan_filtering in dsa_switch_ops (include/net/dsa.h) [1]: https://lore.kernel.org/lkml/20191020031941.3805884-17-vivien.didelot@gmail.com/ Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* realtek: fix compile errors in rtl838x_eth.c for 5.10INAGAKI Hiroshi2021-09-261-10/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | this patch fixes the following errors when compiling: - "unsigned int txqueue" is added as an additional parameter of ndo_tx_timeout in net_device_ops (include/linux/netdevice.h) - "mac_link_state" in phylink_mac_ops (include/linux/phylink.h) is renamed to "mac_pcs_get_state" and changed the return value to void from int - several parameters are added to "mac_link_up" in phylink_mac_ops (include/linux/phylink.h) and the order of the parameters is changed added: - int speed - int duplex - bool tx_pause - bool rx_pause - a parameter "phy_interface_t *interface" is added to of_get_phy_mode (drivers/of/of_net.c) and returns the state instead of phy mode Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* realtek: add "soc" node to soc dtsi in dts-5.10INAGAKI Hiroshi2021-09-262-129/+147
| | | | | | Add a "soc" node as a simple-bus to rtl838x.dtsi and rtl930x.dtsi. Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* realtek: update soc dtsi in 5.10 for backported driversINAGAKI Hiroshi2021-09-262-6/+41
| | | | | | | | | | | | | | | this patch updates SoC dtsi (rtl838x.dtsi, rtl930x.dtsi) for the following backported drivers: - gpio-realtek-otto (5.13) - spi-realtek-rtl (5.12) - irq-realtek-rtl (5.12) And, disable SoC GPIO node (gpio0) in rtl930x.dtsi in dts-5.10. Currently, the upstreamed driver doesn't support the GPIO controller on RTL930x SoC. Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* realtek: cleanup and update soc dtsi in 5.10INAGAKI Hiroshi2021-09-262-28/+11
| | | | | | | | | | the following changes are included in this patch: - node is enabled by default, drop 'status = "okay"' - adjust order of "compatible" lines and "reg" lines - add a new blank line before fixed-link node in rtl830x.dtsi Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* realtek: copy dts directory for Kernel 5.10INAGAKI Hiroshi2021-09-2643-1/+1708
| | | | | | | | | | | | | This patch adds "dts-5.10" directory to use backported drivers. There are several specification changes in the new drivers, so there are some compatibility issues in using dts/dtsi files for 5.4. The old DTS files are moved to "dts-5.4", so their corresponding kernel version is obvious as well. Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com> [change "dts" to "dts-5.4", adjust Makefile] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* realtek: refresh and update config-5.10INAGAKI Hiroshi2021-09-261-16/+15
| | | | | | | | | | This patch adjusts config-5.10 by running kernel_menuconfig. Note: - disable psb6970 phy driver (unused in realtek target?) Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* realtek: refresh patches for Kernel 5.10INAGAKI Hiroshi2021-09-2610-51/+44
| | | | | | | This patch refresh all patches in patches-5.10/ to adjust for Kernel 5.10. Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* realtek: remove unnecessary line from rtl838x/Platform in 5.10INAGAKI Hiroshi2021-09-261-1/+0
| | | | | | | | | The following line is already defined in arch/mips/Kbuild.platforms by 300-mips-add-rtl838x-platform.patch. platform-$(CONFIG_RTL838X) += rtl838x/ Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* realtek: drop fixup_bigphys_addr from ioremap.h in 5.10INAGAKI Hiroshi2021-09-261-5/+0
| | | | | | | A macro with the same name is provided in asm/pgtable.h in Kernel 5.10, use it and drop from ioremap.h. Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* realtek: fix "help" line in Kconfig in files/patches for 5.10INAGAKI Hiroshi2021-09-263-3/+3
| | | | | | | | | | | | | | | | | | | | In Kernel 5.10, "help" must be used instead of "---help---". this patch fixes the following errors: drivers/net/dsa/rtl83xx/Kconfig:7: syntax errorgit drivers/net/dsa/rtl83xx/Kconfig:6: unknown statement "---help---" drivers/net/dsa/rtl83xx/Kconfig:7:warning: ignoring unsupported character '.' drivers/net/dsa/rtl83xx/Kconfig:7: unknown statement "This" drivers/net/ethernet/Kconfig:170: syntax error drivers/net/ethernet/Kconfig:169: unknown statement "---help---" drivers/net/ethernet/Kconfig:170:warning: ignoring unsupported character '.' drivers/net/ethernet/Kconfig:170: unknown statement "Say" drivers/net/phy/Kconfig:331: syntax error drivers/net/phy/Kconfig:330: unknown statement "---help---" drivers/net/phy/Kconfig:331: unknown statement "Supports" Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* realtek: backport irq-realtek-rtl driver from 5.12 to 5.10INAGAKI Hiroshi2021-09-263-0/+303
| | | | | | | | This patch backports "irq-realtek-rtl" driver to Kernel 5.10 from 5.12. "MACH_REALTEK_RTL" is used as a platform name in upstream, but "RTL838X" is used in OpenWrt, so update the dependency by the additional patch. Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* realtek: drop platform irq driver from 5.10INAGAKI Hiroshi2021-09-264-320/+7
| | | | | | | To use backported irq driver, drop old irq driver from realtek target and call irqchip_init() in setup.c. Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* realtek: backport gpio-realtek-otto driver from 5.13 to 5.10INAGAKI Hiroshi2021-09-264-0/+519
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch backports "gpio-realtek-otto" driver to Kernel 5.10. "MACH_REALTEK_RTL" is used as a platform name in upstream, but "RTL838X" is used in OpenWrt, so update the dependency by the additional patch. Note: GPIO mapping is changed in the upstreamed driver. old - new 24 - 0 25 - 1 26 - 2 27 - 3 28 - 4 29 - 5 30 - 6 31 - 7 16 - 8 17 - 9 18 - 10 19 - 11 20 - 12 21 - 13 22 - 14 23 - 15 8 - 16 9 - 17 10 - 18 11 - 19 12 - 20 13 - 21 14 - 22 15 - 23 Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* realtek: drop rtl838x gpio driver from 5.10INAGAKI Hiroshi2021-09-263-436/+3
| | | | | | | | | | To backport the upstreamed driver (gpio-realtek-otto) from 5.13, drop the old driver from realtek target. And, modify 301-gpio-add-rtl838x-driver.patch to remove rtl838x GPIO support and rename it only for rtl8231 GPIO support. Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* realtek: backport spi-realtek-rtl driver from 5.12 to 5.10INAGAKI Hiroshi2021-09-263-0/+322
| | | | | | | | This patch backports "spi-realtek-rtl" driver to Kernel 5.10 from 5.12. "MACH_REALTEK_RTL" is used as a platform name in upstream, but "RTL838X" is used in OpenWrt, so update the dependency by the additional patch. Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* realtek: drop rtl838x spi-nor driver from 5.10INAGAKI Hiroshi2021-09-264-738/+0
| | | | | | | To backport the upstreamed driver (spi-realtek-rtl) from 5.12, drop the old driver from realtek target. Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* realtek: copy config/files/patches to 5.10INAGAKI Hiroshi2021-09-2642-0/+15134
| | | | | | | | | | | | this patch copies the following files from 5.4 to 5.10: - config-5.4 -> config-5.10 - files-5.4/ -> files-5.10/ - patches-5.4/ -> patches-5.10/ Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com> [rebase on change in files-5.4] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: enable I2C_CHARDEVDavid Bauer2021-09-251-0/+1
| | | | | | | Expose I2C busses with a chardev device. This is required to control the PSE controller on the Ubiquiti UniFi Flex Switch. Signed-off-by: David Bauer <mail@david-bauer.net>
* ramips: add support for Ubiquiti USW-FlexDavid Bauer2021-09-253-0/+185
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Hardware -------- MediaTek MT7621AT 16M SPI-NOR Macronix MX25L12835FMI Microchip PD69104B1 4-Channel PoE-PSE controller TI TPS2373 PoE-PD controller PoE-Controller -------------- By default, the PoE outputs do not work with OpenWrt. To make them output power, install the "poemgr" package from the packages feed. This package can control the PD69104B1 PSE controller. Installation ------------ 1. Connect to the booted device at 192.168.1.20 using username/password "ubnt" via SSH. 2. Add the uboot-envtools configuration file /etc/fw_env.config with the following content $ echo "/dev/mtd1 0x0 0x1000 0x10000 1" > /etc/fw_env.config 3. Update the bootloader environment. $ fw_setenv boot_openwrt "fdt addr \$(fdtcontroladdr); fdt rm /signature; bootubnt" $ fw_setenv bootcmd "run boot_openwrt" 4. Transfer the OpenWrt sysupgrade image to the device using SCP. 5. Check the mtd partition number for bs / kernel0 / kernel1 $ cat /proc/mtd 6. Set the bootselect flag to boot from kernel0 $ dd if=/dev/zero bs=1 count=1 of=/dev/mtdblock4 7. Write the OpenWrt sysupgrade image to both kernel0 as well as kernel1 $ dd if=openwrt.bin of=/dev/mtdblock6 $ dd if=openwrt.bin of=/dev/mtdblock7 8. Reboot the device. It should boot into OpenWrt. Restore to UniFi ---------------- To restore the vendor firmware, follow the Ubiquiti UniFi TFTP recovery guide for access points. The process is the same for the Flex switch. Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: add support for TP-Link CPE710-v1Andrew Cameron2021-09-255-1/+172
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | TP-Link CPE710-v1 is an outdoor wireless CPE for 5 GHz with one Ethernet port based on the AP152 reference board Specifications: - SoC: QCA9563-AL3A MIPS 74kc @ 775MHz, AHB @ 258MHz - RAM: 128MiB DDR2 @ 650MHz - Flash: 16MiB SPI NOR Based on the GD25Q128 - Wi-Fi 5Ghz: ath10k chip (802.11ac for up to 867Mbps on 5GHz wireless data rate) Based on the QCA9896 - Ethernet: one 1GbE port - 23dBi high-gain directional 2×2 MIMO antenna and a dedicated metal reflector - Power, LAN, WLAN5G Blue LEDs - 3x Blue LEDs Flashing instructions: Flash factory image through stock firmware WEB UI or through TFTP To get to TFTP recovery just hold reset button while powering on for around 30-40 seconds and release. Rename factory image to recovery.bin Stock TFTP server IP:192.168.0.100 Stock device TFTP address:192.168.0.254 Signed-off-by: Andrew Cameron <apcameron@softhome.net> [convert to nvmem, fix MAC assignment in 11-ath10k-caldata] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* kernel: 5.10: backport fix for lp55xx LED driverRobert Marko2021-09-251-0/+28
| | | | | | | | | | | | | | | | | | | This backports the upstream commit: leds: lp55xx: Initialize enable GPIO direction to output Without it under kernel 5.10 on Asus MAP-AC2200 the LED driver will fail probing: [ 1.947521] lp5523x: probe of 0-0032 failed with error -22 After the backported fix: [ 1.873236] lp5523x 0-0032: lp5523 Programmable led chip found Signed-off-by: Robert Marko <robert.marko@sartura.hr> Tested-by: Szabolcs Hubai <szab.hu@gmail.com> [ipq4029/gl-b1300] Tested-by: Nick Hainke <vincent@systemli.org> [ipq4019/fritzbox-7530 ipq4019/fritzbox-4040 ipq4019/sxtsq-5ac] Tested-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> [ipq4019/map-ac2200]
* ipq40xx: add testing support for kernel 5.10Robert Marko2021-09-251-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | Add kernel 5.10 as the testing kernel to ipq40xx to get wider testing. The following devices failed to build with buildbot settings and all feeds installed (apparently due to kernel size): * cell-c rtl30vw * compex wpj428 * devolo magic 2 next * engenius emr3500 * glinet gl-b1300 * glinet gl-s1300 * qcom ap-dk01.1-c1 * qcom ap-dk04.1-c1 Signed-off-by: Robert Marko <robert.marko@sartura.hr> Tested-by: Nick Hainke <vincent@systemli.org> [ipq4019/fritzbox-7530 ipq4019/fritzbox-4040 ipq4019/sxtsq-5ac] Tested-by: Szabolcs Hubai <szab.hu@gmail.com> [ipq4029/gl-b1300] Tested-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> [ipq4019/map-ac2200] [add tested-by and note about failed devices] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ipq40xx: 5.10: move AR40xx to MDIO driversRobert Marko2021-09-256-23/+2256
| | | | | | | | | | | MDIO drivers were moved into their own sub directory of networking drivers. This has caused the AR40xx driver to probe before MDIO drivers and that wont work as it depends on the MDIO bus to be up so it can be fetched. Lets solve it by moving the AR40xx into MDIO folder so they get probed like before. Signed-off-by: Robert Marko <robert.marko@sartura.hr>
* ipq40xx: net: ethernet: edma: reject unsupported coalescing paramsRobert Marko2021-09-251-0/+4
| | | | | | | | | | | Set ethtool_ops->supported_coalesce_params to let the core reject unsupported coalescing parameters. This driver did not previously reject unsupported parameters. This is a required ethtool op since kernel 5.7. Signed-off-by: Robert Marko <robert.marko@sartura.hr>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-09 23:03:00 +0000