aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* 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-256-1/+209
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* ipq40xx: net: ethernet: edma: update of_get_phy_mode() for 5.10Robert Marko2021-09-251-1/+9
| | | | | | | | | | In kernel v5.5 of_get_phy_mode had its API changed, so its now returning 0 or errors instead of phymode. Phymode is now returning by passing a pointer to phy_interface_t where it will be stored. Signed-off-by: Robert Marko <robert.marko@sartura.hr>
* ipq40xx: 5.10: add kernel configRobert Marko2021-09-251-0/+493
| | | | | | | | | | Copy config from 5.4 and run "make kernel_oldconfig". Select default ("N") for all new symbols. Signed-off-by: Robert Marko <robert.marko@sartura.hr> [make commit message more explicit] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ipq40xx: 5.10: refresh patches to applyRobert Marko2021-09-259-31/+30
| | | | | | | | Refresh the kernel patches on top of 5.10 so they apply. Manually fixup the 705-net-add-qualcomm-ar40xx-phy.patch to apply. Signed-off-by: Robert Marko <robert.marko@sartura.hr>
* ipq40xx: 5.10: replace patches with upstreamed versionsRobert Marko2021-09-253-11/+18
| | | | | | | | | USB and SDHCI LDO DTS patches have been upstreamed into 5.12, so replace the local versions with upstreamed ones. Reorder, and clearly mark the kernel version. Signed-off-by: Robert Marko <robert.marko@sartura.hr>
* ipq40xx: 5.10: remove duplicate GPIO export patchRobert Marko2021-09-251-165/+0
| | | | | | | Its in the generic target already, so remove the duplicate as it breaks compilation. Signed-off-by: Robert Marko <robert.marko@sartura.hr>
* ipq40xx: 5.10: drop upstreamed patchesRobert Marko2021-09-2522-3005/+0
| | | | | | Drop patches that have been upstreamed in before 5.10. Signed-off-by: Robert Marko <robert.marko@sartura.hr>
* ipq40xx: 5.10: copy patchesRobert Marko2021-09-2544-0/+4683
| | | | | | Copy over the 5.4 kernel patches to 5.10 folder. Signed-off-by: Robert Marko <robert.marko@sartura.hr>
* ramips: add support for I-O DATA WN-DX2033GRINAGAKI Hiroshi2021-09-253-1/+51
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I-O DATA WN-DX2033GR is a 2.4/5 GHz band 11ac (Wi-Fi 5) router, based on MT7621A. Specification: - SoC : MediaTek MT7621A - RAM : DDR3 128 MiB - Flash : Raw NAND 128 MiB (Macronix MX30LF1G18AC-TI) - WLAN : 2.4/5 GHz - 2.4 GHz : 2T2R, MediaTek MT7603E - 5 GHz : 4T4R, MediaTek MT7615 - Ethernet : 5x 10/100/1000 Mbps - Switch : MediaTek MT7530 (SoC) - LEDs/Keys : 2x/3x (2x buttons, 1x slide-switch) - UART : through-hole on PCB - J5: 3.3V, TX, RX, NC, GND from triangle mark - 57600n8 - Power : 12 VDC, 1 A Flash instruction using initramfs image: 1. Boot WN-DX2033GR normally 2. Access to "http://192.168.0.1/" and open firmware update page ("ファームウェア") 3. Select the OpenWrt initramfs image and click update ("更新") button to perform firmware update 4. On the initramfs image, download the sysupgrade.bin image to the device and perform sysupgrade with it 5. Wait ~120 seconds to complete flashing Notes: - The hardware of WN-DX2033GR and WN-AX2033GR are almost the same, and it is certified under the same radio-wave related regulations in Japan - The last 0x80000 (512 KiB) in NAND flash is not used on stock firmware - stock firmware requires "customized uImage header" (called as "combo image") by MSTC (MitraStar Technology Corp.), but U-Boot doesn't - uImage magic ( 0x0 - 0x3 ) : 0x434F4D42 ("COMB") - header crc32 ( 0x4 - 0x7 ) : with "data length" and "data crc32" - image name (0x20 - 0x37) : model ID and firmware versions - data length (0x38 - 0x3b) : kernel + rootfs - data crc32 (0x3c - 0x3f) : kernel + rootfs - There are 2x important flags in the flash: - bootnum : select os partition for booting (persist, 0x4) - 0x01: firmware - 0x02: firmware_2 - debugflag : allow interrupt kernel loader, it's named as "Z-LOADER" (Factory, 0xFE75) - 0x00: disable debug - 0x01: enable debug MAC addresses: LAN : 50:41:B9:xx:xx:90 (Factory, 0xE000 (hex) / Ubootenv, ethaddr (text)) WAN : 50:41:B9:xx:xx:92 (Factory, 0xE006 (hex)) 2.4 GHz : 50:41:B9:xx:xx:90 (Factory, 0x4 (hex)) 5 GHz : 50:41:B9:xx:xx:91 (Factory, 0x8004 (hex)) Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* realtek: fix RTL8231 gpio expander for high GPIOsPaul Fertser2021-09-251-5/+8
| | | | | | | | GPIOs > 31 require special handling. This patch fixes both the initialisation and direction get/set operations. Signed-off-by: Paul Fertser <fercerpav@gmail.com> Reviewed-by: Sander Vanheule <sander@svanheule.net>
* kernel: add patch to fix an issue with kernel headers that broke perfFelix Fietkau2021-09-251-0/+11
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* tools/fakeroot: fix build error on macOSFelix Fietkau2021-09-251-0/+11
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* mac80211: backport support for BSS color changesFelix Fietkau2021-09-253-16/+1025
| | | | | | This is needed for an upcoming mt76 update Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ramips: add missing information to dlink headersAlan Luck2021-09-245-8/+179
| | | | | | | | | | | | Add additional header information required for newer bootloaders found on DIR-2660-A1 & A2. Also remove the MTD splitter compatible from the second firmware partition, as OpenWrt only supports handling of the first one. Signed-off-by: Alan Luck <luckyhome2008@gmail.com> [rephrase commit message, remove removal of read-only flags] Signed-off-by: David Bauer <mail@david-bauer.net>
* hostapd: fix segfault when deinit mesh ifacesJesus Fernandez Manzano2021-09-241-0/+5
| | | | | | | | | | | In hostapd_ubus_add_bss(), ubus objects are not registered for mesh interfaces. This provokes a segfault when accessing the ubus object in mesh deinit. This commit adds the same condition to hostapd_ubus_free_bss() for discarding those mesh interfaces. Signed-off-by: Jesus Fernandez Manzano <jesus.manzano@galgus.net>
* rockchip: fix broken squashfs sysupgradeDavid Bauer2021-09-241-1/+1
| | | | | | | | | | | | | | The rockchip platform supports squashfs SD card images. However, the resulting image is not padded to completely fill the rootfs partition. Because of that, the f2fs overlay might not be erased, resulting in uci-defaults not bing executed or the configuration not being erased, even though drop config was selected. Modify the image generation process so the image is padded to cover the entire root filesystem partition. Signed-off-by: David Bauer <mail@david-bauer.net>
* scripts: package-metadata add pkgmanifestjson callPaul Spooren2021-09-231-0/+36
| | | | | | | | | | The new `pkgmanifestjson` call prints all package manifest of a feed in JSON format. This function can be used to print an overview of packages information used for downstream tooling. The script is entirely based on Petrs work on dependency visualisation. Signed-off-by: Paul Spooren <mail@aparcar.org>
* bcm47xx: use device vendor/model variableMoritz Warning2021-09-232-4/+8
| | | | | | | | Remove use of DEVICE_TITLE in favor of the DEVICE_VENDOR and DEVICE_MODEL as used by all other targets. Signed-off-by: Moritz Warning <moritzwarning@web.de>
* x86: use device vendor/model variableMoritz Warning2021-09-234-5/+10
| | | | | | | | Remove use of DEVICE_TITLE in favor of the DEVICE_VENDOR and DEVICE_MODEL as used by all other targets. Signed-off-by: Moritz Warning <moritzwarning@web.de>
* base-files: reduce number of `mkdir` callsPaul Spooren2021-09-231-17/+19
| | | | | | | | | | | | | The `mkdir` commands supports passing multiple arguments to batch create multiple folders, instead of calling the tool every single time. If the creation of one of the folders fails, all other folder are still created and therefore doesn't change the error handling. Also stop creating `/etc/` explicitly after subfolders of `/etc/` were already created. Signed-off-by: Paul Spooren <mail@aparcar.org>
* base-files: reduce `sed` callsPaul Spooren2021-09-231-4/+2
| | | | | | | | | The `sed`-script shouldn't be called multiple times, especially not with the same files. This commit merges all files together in a single `sed`-script call. Signed-off-by: Paul Spooren <mail@aparcar.org>
* scripts: store maintainer in package metadataPaul Spooren2021-09-231-0/+1
| | | | | | | The maintainer could be usable for downstream tooling, so start storing it in the metadata. Signed-off-by: Paul Spooren <mail@aparcar.org>
* imagebuilder: show architecture in `make info` outputPaul Spooren2021-09-231-0/+1
| | | | | | | Using `make info` show the current target, revision, default packages and available profiles. This commits adds the used architecture. Signed-off-by: Paul Spooren <mail@aparcar.org>
* restool: add back PKG_VERSIONRosen Penev2021-09-231-1/+2
| | | | | | | | | | | | | For some reason, the build system chops off the last number from the version, which is not correct. Add it back. Update hash. Fixes: 96c7164acd80 ("restool: update to LSDK-20.12") Signed-off-by: Rosen Penev <rosenp@gmail.com> [add Fixes] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ipq-wifi: Work around Plasma Cloud PA1200 5GHz crashSven Eckelmann2021-09-231-0/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It was noticed [1] that the ath10k firmware crashes on 5GHz since OpenWrt 21.02.0. The problem seems to be triggered by the the nonLinearTxFir field in the 5GHz BDF. If baseEepHeader.nonLinearTxFir (offset 0xc2) is 1 then the firmware just crashes when setting up the 5Ghz radio using `ifconfig wlan1 up`: ath10k_ahb a800000.wifi: firmware crashed! (guid 9e36ee82-4d2c-4c63-b20b-609a1eaca30c) ath10k_ahb a800000.wifi: qca4019 hw1.0 target 0x01000000 chip_id 0x003b00ff sub 0000:0000 ath10k_ahb a800000.wifi: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 0 ath10k_ahb a800000.wifi: firmware ver 10.4-3.6-00140 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps crc32 ba79b746 ath10k_ahb a800000.wifi: board_file api 2 bmi_id 0:17 crc32 5f400efc ath10k_ahb a800000.wifi: htt-ver 2.2 wmi-op 6 htt-op 4 cal pre-cal-file max-sta 512 raw 0 hwcrypto 1 ath10k_ahb a800000.wifi: firmware register dump: ath10k_ahb a800000.wifi: [00]: 0x0000000B 0x000015B3 0x009C3C27 0x00975B31 ath10k_ahb a800000.wifi: [04]: 0x009C3C27 0x00060530 0x00000018 0x004176B8 ath10k_ahb a800000.wifi: [08]: 0x00405A50 0x00412A30 0x00000000 0x00000000 ath10k_ahb a800000.wifi: [12]: 0x00000009 0x00000000 0x009B9742 0x009B974F ath10k_ahb a800000.wifi: [16]: 0x00971238 0x009B9742 0x00000000 0x00000000 ath10k_ahb a800000.wifi: [20]: 0x409C3C27 0x004053DC 0x00000D2C 0x00405A60 ath10k_ahb a800000.wifi: [24]: 0x809C3E13 0x0040543C 0x00000000 0xC09C3C27 ath10k_ahb a800000.wifi: [28]: 0x809B9AC5 0x0040547C 0x00412A30 0x0040549C ath10k_ahb a800000.wifi: [32]: 0x809B8ECD 0x0040549C 0x00000001 0x00412A30 ath10k_ahb a800000.wifi: [36]: 0x809B8FF3 0x004054CC 0x00412838 0x00000014 ath10k_ahb a800000.wifi: [40]: 0x809BEF98 0x0040551C 0x0041627C 0x00000002 ath10k_ahb a800000.wifi: [44]: 0x80986D47 0x0040553C 0x0041627C 0x00416A88 ath10k_ahb a800000.wifi: [48]: 0x809CBB0A 0x0040559C 0x0041ACC0 0x00000000 ath10k_ahb a800000.wifi: [52]: 0x809864EE 0x0040560C 0x0041ACC0 0x00000001 ath10k_ahb a800000.wifi: [56]: 0x809CA8A4 0x0040564C 0x0041ACC0 0x00000001 ath10k_ahb a800000.wifi: Copy Engine register dump: ath10k_ahb a800000.wifi: [00]: 0x0004a000 14 14 3 3 ath10k_ahb a800000.wifi: [01]: 0x0004a400 16 16 22 23 ath10k_ahb a800000.wifi: [02]: 0x0004a800 3 3 2 3 ath10k_ahb a800000.wifi: [03]: 0x0004ac00 15 15 15 15 ath10k_ahb a800000.wifi: [04]: 0x0004b000 4 4 44 4 ath10k_ahb a800000.wifi: [05]: 0x0004b400 3 3 2 3 ath10k_ahb a800000.wifi: [06]: 0x0004b800 1 1 1 1 ath10k_ahb a800000.wifi: [07]: 0x0004bc00 1 1 1 1 ath10k_ahb a800000.wifi: [08]: 0x0004c000 0 0 127 0 ath10k_ahb a800000.wifi: [09]: 0x0004c400 0 0 0 0 ath10k_ahb a800000.wifi: [10]: 0x0004c800 0 0 0 0 ath10k_ahb a800000.wifi: [11]: 0x0004cc00 0 0 0 0 ath10k_ahb a800000.wifi: failed to update channel list: -108 ath10k_ahb a800000.wifi: failed to set pdev regdomain: -108 ath10k_ahb a800000.wifi: failed to create WMI vdev 0: -108 ieee80211 phy1: Hardware restart was requested Since no actual solution is known (besides downgrading the ath10k firmware) it seems to be better to disable the nonLinearTxFir for now. [1] https://lore.kernel.org/ath10k/3423718.UToCqzeSYe@ripper/ Signed-off-by: Sven Eckelmann <sven@narfation.org>
* ipq-wifi: Update Plasma Cloud PA1200 BDFs to firmware 3.5.12Sven Eckelmann2021-09-231-0/+0
| | | | | | | | The official Plasma Cloud firmware adjusted the BDFs to contain new conformance test limits and target power values. These should be imported to avoid emissions outside the allowed limits. Signed-off-by: Sven Eckelmann <sven@narfation.org>
* bcm53xx: MR32: read mac-address from eepromChristian Lamparter2021-09-232-4/+46
| | | | | | | | Meraki wrote the ethernet MAC-address of the device onto the eeprom (AT24C64) at the fixed location 0x66 to 0x6C. Let's fetch it from there. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* scripts: mkits.sh: Allow legacy @ mode for dts creationDamien Mascord2021-09-233-13/+19
| | | | | | | | | | | | | | | | | | commit 5ec60cbe9d94 ("scripts: mkits.sh: replace @ with - in nodes") broke support for Meraki MR32 and this patch makes the replacement configurable allowing for specifying the @ or - or whatever character that is desired to retain backwards compatibility with existing devices. For example, this patch includes the fix for the Meraki MR32 in target/linux/bcm53xx/image for meraki_mr32: DEVICE_DTS_DELIMITER := @ DEVICE_DTS_CONFIG := config@1 Fixes: 5ec60cbe9d94 ("scripts: mkits.sh: replace @ with - in nodes") Signed-off-by: Damien Mascord <tusker@tusker.org> [Added tags, checkpatch.pl fixes, noted that this is for old stuff] Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* libtool: Revert "libtool: bump to 2.4.6"Hauke Mehrtens2021-09-2310-444/+334
| | | | | | | | | | This breaks the package builds using the SDK. The targets all build fine, but the package builder fails on many packages. The package builder uses the OpenWrt SDK. This reverts commit c377d874bededfad971530aeb7d7e1b43cd3e61a. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* scripts: handle gcc and linux in dl_cleanup scriptAnsuel Smith2021-09-221-2/+2
| | | | | | | | | | | Handle gcc and linux with a special regex that set their progname with their major version. This way every minor version can be cleared. The build cleanup logic can be tweaked later to clean the entire toolchain and target dir with a different gcc version. Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com> [reformat commit message] Signed-off-by: Paul Spooren <mail@aparcar.org>
* bcm53xx: backport early DT patches queued for 5.16Rafał Miłecki2021-09-2312-4/+642
| | | | Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* scripts: format dl_cleanup to black format python styleAnsuel Smith2021-09-221-199/+230
| | | | | | Forma dl_cleanup python script to black style. Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
* scripts: add missing regex for dl_cleanup scriptAnsuel Smith2021-09-221-0/+8
| | | | | | | | | | | | | | | Regex xxx-YYYY-MM-DD-GIT_SHASUM was missing. Add the new regex to improve and better find outdated package. This also fix a bug where some bug were incorrectly detected as packagename-yyyy-mm-dd instead of packagename due to them be parsed by the wrong parser Example: openwrt-keyring-2021-02-20-49283916.tar.xz Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com> [added example in commit message] Signed-off-by: Paul Spooren <mail@aparcar.org>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-01 04:35:44 +0000