aboutsummaryrefslogtreecommitdiffstats
path: root/target
Commit message (Collapse)AuthorAgeFilesLines
* kernel: bump 5.10 to 5.10.200Hauke Mehrtens2023-11-2114-23/+23
| | | | | | All patches automatically rebased. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* ath79: image: allow changing kernel option in mkubntimageTomasz Maciej Nowak2023-11-191-1/+1
| | | | | | | | | | | Backport didn't include changes to mkubntimage invocation, which allowed to pass arguments. This in result produces broken routerstation factory images, which have kernel embedded as kernel partition instead of LZMA loader. Fixes: #13260 Fixes: 8e09f9ffc3cc ("ath79: switch some RedBoot based devices to OKLI loader") Signed-off-by: Tomasz Maciej Nowak <tmn505@gmail.com>
* treewide: fix shell errors during dump stagePetr Štetiar2023-11-132-0/+5
| | | | | | | | | | | | | | | | Fixes following issues: bash: -c: line 1: `echo 1686820180<LINUX_VERMAGIC> | /staging_dir/host/bin/mkhash md5 | cut -b1-8' bash: -c: line 1: `echo 1686820180<LINUX_VERMAGIC> | /staging_dir/host/bin/mkhash md5 | sed -E 's/(.{8})(.{4})(.{4})(.{4})(.{10})../\1-\2-\3-\4-\500/'' bash: -c: line 1: syntax error near unexpected token `|' bash: line 1: *1024*1024: syntax error: operand expected (error token is "*1024*1024") bash: line 1: (64 + ): syntax error: operand expected (error token is ")") expr: syntax error: missing argument after '+' Signed-off-by: Petr Štetiar <ynezz@true.cz> (cherry picked from commit 8fc496be860192f8bd1f16913657626014c8863f) [ fix merge conflicts, adapt to 22.03 ] Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* bcm53xx: refresh kernel configRafał Miłecki2023-11-061-0/+1
| | | | Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* kernel: bump 5.10 to 5.10.199Hauke Mehrtens2023-11-0225-46/+46
| | | | | | All patches automatically rebased. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump 5.10 to 5.10.198Hauke Mehrtens2023-11-0210-20/+20
| | | | | | All patches automatically rebased. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* ath79: increase the rfkill debounce interval for TP-Link Archer C7 v2Shiji Yang2023-10-311-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Due to circuit issue or silicon defect, sometimes the WiFi switch button of the Archer C7 v2 can be accidentally triggered multiple times in one second. This will cause WiFi to be unexpectedly shut down and trigger 'irq 23: nobody cared'[1] warning. Increasing the key debounce interval to 1000 ms can fix this issue. This patch also add the missing rfkill key label. [1] Warning Log: ``` [87765.218511] irq 23: nobody cared (try booting with the "irqpoll" option) [87765.225331] CPU: 0 PID: 317 Comm: irq/23-keys Not tainted 5.15.118 #0 ... [87765.486246] handlers: [87765.488543] [<85257547>] 0x800c29a0 threaded [<5c6328a2>] 0x80ffe0b8 [gpio_button_hotplug@4cf73d00+0x1a00] [87765.498364] Disabling IRQ #23 ``` Fixes: https://github.com/openwrt/openwrt/issues/13010 Fixes: https://github.com/openwrt/openwrt/issues/12167 Fixes: https://github.com/openwrt/openwrt/issues/11191 Fixes: https://github.com/openwrt/openwrt/issues/7835 Tested-by: Hans Hasert Signed-off-by: Shiji Yang <yangshiji66@qq.com> (cherry picked from commit e32f70e7066c3110694851eced3301f50019693b)
* bcm53xx: backport 1 more late DT patch accepted for v6.7Rafał Miłecki2023-10-262-44/+63
| | | | | Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit 732ae343ffb3ad19978b75a8105d55f5e6d1d435)
* bcm53xx: disable unused switch ports in downstream patchRafał Miłecki2023-10-261-15/+135
| | | | | | | | | This makes Linux use correct switch ports again. Fixes: e3d0c7097ee6 ("bcm53xx: backport DT changes from v6.5") Fixes: https://github.com/openwrt/openwrt/issues/13548 Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit a912ee74d6ca08020933dcdb9ce791e74244c25b)
* bcm53xx: backport DT changes queued for v6.7Rafał Miłecki2023-10-267-1/+686
| | | | | | | | | Among other changes this commit makes Linux use correct switch ports again. Fixes: e3d0c7097ee6 ("bcm53xx: backport DT changes from v6.5") Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit a67af19bc84e98588c307af9b08686bde9dd38d5)
* bcm53xx: simplify patch adding switch portsRafał Miłecki2023-10-261-128/+15
| | | | | | | | We now have all raw ports defined in bcm-ns.dtsi. Leave only lables in custom device files. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit 08ce0c76d7d7daad5e9382d51960d69f4b8b8f3a)
* bcm53xx: build a single device per profileRani Hod2023-10-261-0/+1
| | | | | | | | | | | | | | | So far every build of a single bcm53xx Target Profile (it means: when NOT using CONFIG_TARGET_MULTI_PROFILE) resulted in all target devices images being built. Now it only builds the one matching selected profile. Fixes: #13572 Suggested-by: Jonas Gorski <jonas.gorski@gmail.com> Signed-off-by: Rani Hod <rani.hod@gmail.com> [rmilecki: update commit subject + body & move PROFILES line] Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit 802a5f5cb4a7b42d25e82b787d7ab1323a20183f)
* bcm53xx: add support for ASUS RT-AC3100Arınç ÜNAL2023-10-261-0/+8
| | | | | | | | | | | | | | ASUS RT-AC3100 is ASUS RT-AC88U without the external switch. OpenWrt forum users effortless and ktmakwana have confirmed that there are revisions with either 4366b1 or 4366c0 wireless chips. Therefore, include firmware for 4366b1 along with 4366c0. This way, all hardware revisions of the router will be supported by having brcmfmac use the firmware file for the wireless chip it detects. Signed-off-by: Arınç ÜNAL <arinc.unal@arinc9.com> (cherry picked from commit 2214bab3503981fe6168746acd13044a9d5e89e7)
* bcm53xx: backport DT changes for ASUS RT-AC3100 queued for v6.6Arınç ÜNAL2023-10-262-1/+432
| | | | | | | Backport the patch that adds the DT for ASUS RT-AC3100. Signed-off-by: Arınç ÜNAL <arinc.unal@arinc9.com> (cherry picked from commit b7ee8c9f83ea0e3b861e6b71b08ed7a62066d149)
* ipq40xx: switch to performance governor by defaultKoen Vandeputte2023-10-201-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Doing a simple ping to my device shows this: 64 bytes from 10.0.253.101: icmp_seq=1 ttl=64 time=2.00 ms 64 bytes from 10.0.253.101: icmp_seq=2 ttl=64 time=2.02 ms 64 bytes from 10.0.253.101: icmp_seq=3 ttl=64 time=1.68 ms 64 bytes from 10.0.253.101: icmp_seq=4 ttl=64 time=1.91 ms 64 bytes from 10.0.253.101: icmp_seq=5 ttl=64 time=1.92 ms 64 bytes from 10.0.253.101: icmp_seq=6 ttl=64 time=2.04 ms Some users even report higher values on older kernels: 64 bytes from 192.168.1.10: seq=0 ttl=64 time=0.612 ms 64 bytes from 192.168.1.10: seq=1 ttl=64 time=2.852 ms 64 bytes from 192.168.1.10: seq=2 ttl=64 time=2.719 ms 64 bytes from 192.168.1.10: seq=3 ttl=64 time=2.741 ms 64 bytes from 192.168.1.10: seq=4 ttl=64 time=2.808 ms The problem is that the governor is set to Ondemand, which causes the CPU to clock all the way down to 48MHz in some cases. Switching to performance governor: 64 bytes from 10.0.253.101: icmp_seq=1 ttl=64 time=0.528 ms 64 bytes from 10.0.253.101: icmp_seq=2 ttl=64 time=0.561 ms 64 bytes from 10.0.253.101: icmp_seq=3 ttl=64 time=0.633 ms 64 bytes from 10.0.253.101: icmp_seq=4 ttl=64 time=0.526 ms In theory, using the Performance governor should increase power draw, but it looks like it really does not matter for this soc. Using a calibrated precision DC power supply (cpu idle): Ondemand 24.00V * 0.134A = 3.216 Watts 48.00V * 0.096A = 4.608 Watts Performance 24.00V * 0.135A = 3.240 Watts 48.00V * 0.096A = 4.608 Watts Let's simply switch to the Performance governor by default to fix the general jittery behaviour on devices using this soc. Tested on: MikroTik wAP ac Fixes: #13649 Reviewed-by: Robert Marko <robimarko@gmail.com> Reviewed-by: Thibaut VARÈNE <hacks@slashdirt.org> Signed-off-by: Koen Vandeputte <koen.vandeputte@citymesh.com> (cherry picked from commit b8e52852bd62236a2a84663b4592d221ebc64cb4)
* ath79: wpj563: enable 2nd USB controllerKoen Vandeputte2023-10-131-0/+8
| | | | | | | | | | | | | The compex WPJ563 actually has both usb controllers wired: usb0 --> pci-e slot usb1 --> pin header As the board exposes it for generic use, enable this controller too. fixes: #13650 Signed-off-by: Koen Vandeputte <koen.vandeputte@citymesh.com> (cherry picked from commit 9188c77cbee55a933d0fa75c74e175fbc52c556d)
* kernel: bump 5.10 to 5.10.197Hauke Mehrtens2023-09-245-7/+7
| | | | | | All patches automatically rebased. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump 5.10 to 5.10.196Hauke Mehrtens2023-09-2462-435/+184
| | | | | | | | | | | | | | Removed because already in upstream: target/linux/bcm53xx/patches-5.10/030-v5.11-0002-ARM-dts-BCM5301X-Harmonize-EHCI-OHCI-DT-nodes-name.patch target/linux/bcm53xx/patches-5.10/033-v5.16-0019-ARM-dts-BCM53573-Describe-on-SoC-BCM53125-rev-4-swit.patch target/linux/bcm53xx/patches-5.10/040-v6.6-0005-ARM-dts-BCM53573-Drop-nonexistent-usb-cells.patch target/linux/bcm53xx/patches-5.10/040-v6.6-0006-ARM-dts-BCM53573-Add-cells-sizes-to-PCIe-node.patch target/linux/bcm53xx/patches-5.10/040-v6.6-0007-ARM-dts-BCM53573-Use-updated-spi-gpio-binding-proper.patch target/linux/bcm53xx/patches-5.10/040-v6.6-0008-ARM-dts-BCM5301X-Extend-RAM-to-full-256MB-for-Linksy.patch All other patches automatically rebased. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* ath79: fix packetloss on some WLR-7100Matthijs Kooijman2023-09-171-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | On some WLR-7100 routers, significant packet loss was observed. This is fixed by configuring a delay on the GMAC0 RXD and RXDV lines. The values used in this commit are copied from the values used by the stock firmare (based on register dumping). Out of four test routers, the problem was consistently observed on two. It is unclear what the relevant difference is exactly (the two working routers were v1 001 with AR1022 and v1 002 with AR9342, the two broken routers were both v1 002 with AR1022). All PCB routing also seems identical, so maybe there is some stray capacitance on some of these that adds just enough delay or so... With this change, the packet loss disappears on the broken routers, without introducing new packet loss on the previously working routers. Note that the PHY *also* has delays enabled (through `qca,ar8327-initvals`) on both RX and TX lines, but apparently that is not enough, or it is not effective (registers have been verified to be written). For detailed discussion of this issue and debug history, see https://forum.openwrt.org/t/sitecom-wlr-7100-development-progress/79641 Signed-off-by: Matthijs Kooijman <matthijs@stdin.nl> (cherry picked from commit d2ce3a61aa1cbc53988eb640cbab48e20fbfb1aa)
* x86: geode: fix hwrng register accessesJonas Gorski2023-09-141-0/+47
| | | | | | | | | | | | | | | | | | | | When the membase and pci_dev pointer were moved to a new struct in priv, the actual membase users were left untouched, and they started reading out arbitrary memory behind the struct instead of registers. This unfortunately turned the RNG into a constant number generator, depending on the content of what was at that offset. To fix this, update geode_rng_data_{read,present}() to also get the membase via amd_geode_priv, and properly read from the right addresses again. Closes #13417. Reported-by: Timur I. Davletshin <timur.davletshin@gmail.com> Tested-by: Timur I. Davletshin <timur.davletshin@gmail.com> Suggested-by: Jo-Philipp Wich <jo@mein.io> Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com> (cherry picked from commit 09d13cd8d87cc50fde67bbe81c6cca4b799b2724)
* kernel: bump 5.10 to 5.10.194Hauke Mehrtens2023-09-035-8/+8
| | | | | | All patches automatically rebased. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump 5.10 to 5.10.192Hauke Mehrtens2023-08-297-42/+10
| | | | | | | | | Removed because already in upstream: rockchip/patches-5.10/104-rockchip-use-USB-host-by-default-on-rk3399-rock-pi-4.patch All other patches automatically rebased. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump 5.10 to 5.10.191Hauke Mehrtens2023-08-1910-29/+29
| | | | | | All patches automatically rebased. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump 5.10 to 5.10.190Hauke Mehrtens2023-08-119-11/+11
| | | | | | All patches automatically rebased. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump 5.10 to 5.10.189Hauke Mehrtens2023-08-1122-33/+35
| | | | | | All patches automatically rebased. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump 5.10 to 5.10.188Hauke Mehrtens2023-08-1135-184/+63
| | | | | | | | | | | | | | | Manually rebased: bcm27xx/patches-5.10/950-0355-xhci-quirks-add-link-TRB-quirk-for-VL805.patch bcm53xx/patches-5.10/180-usb-xhci-add-support-for-performing-fake-doorbell.patch Removed because already in upstream: bcm53xx/patches-5.10/039-v6.5-0003-ARM-dts-BCM5301X-Drop-clock-names-from-the-SPI-node.patch bcm53xx/patches-5.10/039-v6.5-0015-ARM-dts-BCM5301X-fix-duplex-full-full-duplex.patch generic/backport-5.10/765-v6.5-net-bgmac-postpone-turning-IRQs-off-to-avoid-SoC-han.patch All other patches automatically rebased. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* bcm53xx: backport more DT changes queued for v6.6Rafał Miłecki2023-07-298-28/+290
| | | | | | | Those sort out BCM53573 Ethernet info finally. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit ca8868a51127f6081a524d47eab937b90af0bf05)
* bcm53xx: add BCM53573 Ethernet fix sent upstream for v6.6Rafał Miłecki2023-07-291-0/+28
| | | | | | | | | | | | | | It seems that DSA-based b53 driver never worked with BCM53573 SoCs and BCM53125. In case of swconfig-based b53 this fixes a regression. Switching bgmac from using mdiobus_register() to of_mdiobus_register() resulted in MDIO device (BCM53125) having of_node set (see of_mdiobus_register_phy()). That made downstream b53 driver read invalid data from DT and broke Ethernet support. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit 79fd3e62b4910731c13692b2daa2083e0f95c023)
* octeon: ubnt-edgerouter-4/6p: devicetree cleanupCarsten Spieß2023-07-193-30/+10
| | | | | | | | | | | removed redundant eeprom partition nodes from cn7130_ubnt_edgerouter-4.dts and cn7130_ubnt_edgerouter-6p.dts as they are identically defined in cn7130_ubnt_edgerouter-e300.dtsi. Signed-off-by: Carsten Spieß <mail@carsten-spiess.de> (integrated eeprom referenced node in the .dtsi) Signed-off-by: Christian Lamparter <chunkeey@gmail.com> (cherry picked from commit 700f11aaadb7baa38285ed8f928e976a29a72eed)
* octeon: ubnt-edgerouter-e300: fix missing MTD partitionCarsten Spieß2023-07-191-16/+22
| | | | | | | | | | | | | | | The MAC addresses should be read from 3rd MTD partition, but only two MTD partitions are populated. To fix it, a partitions node has to surround the partition nodes in device tree. Tested with Edgerouter 6P Signed-off-by: Carsten Spieß <mail@carsten-spiess.de> (fixed checkpatch complains) Signed-off-by: Christian Lamparter <chunkeey@gmail.com> (cherry picked from commit 2b1d7965c7e74e1b31ff29a966eaf6334b0d7057)
* octeon: ubnt-edgerouter-e300: fix LED settingsCarsten Spieß2023-07-191-2/+2
| | | | | | | | | | | | | | LEDs on Edgerouter 6P didn't work correctly: blue /white LED swapped, on/off state inverted Fixed in device tree: swap the GPIO ports for power:blue and power:white LEDs change LED activity from LOW to HIGH Tested on Edgerouter 6P Signed-off-by: Carsten Spieß <mail@carsten-spiess.de> (cherry picked from commit 9009672930f7bda99ec8f6f09a92eb49b6c9aac8)
* ib: split out processing user provided packagesTomasz Maciej Nowak2023-07-191-1/+3
| | | | | | | | | | Some device recipes remove default target packages. If user tries to add them back they will be ignored, since packages list is processed in one go. Process the device recipe packages first and do user ones later, so additions won't get filtered out. Signed-off-by: Tomasz Maciej Nowak <tmn505@gmail.com> (cherry picked from commit e40b9a7fa002154e85459791101a0444d99dfb86)
* sdk: rename README + update MakefileTomasz Maciej Nowak2023-07-192-1/+1
| | | | | | | | | | | | | 'help' target fails not finding a file, so follow up on a change[2] made as a fix for main README[1]. 1. d0113711a31f ("README: port to 21st century") 2. 751486b31fd9 ("build: fix README.md reference after rename") Signed-off-by: Tomasz Maciej Nowak <tmn505@gmail.com> (cherry picked from commit 2d5f7035cf45801158bed6f5d0ac0de0002c1810) (cherry picked from commit e9911f10e482f3174f745a36c0c9fd7964758caf) Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* bcm53xx: backport DT changes queued for v6.6Rafał Miłecki2023-07-1410-1/+474
| | | | | Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit 37ff916af789911fdefb802ce9903e866eb82435)
* bcm53xx: backport DT changes from v6.5Rafał Miłecki2023-07-1125-11/+4636
| | | | | Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit 8674b41c0d84f09e14bf8ebe08e1d6dc6ac5fa64)
* kernel: bgmac: fix regressed support for BCM53573 SoCsRafał Miłecki2023-07-101-0/+45
| | | | | Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit d54f3b2cfdbd34aa61ca67fd590eebfdf3db51cf)
* bcm47xx: fix bgmac MTU patch filenameRafał Miłecki2023-07-101-0/+0
| | | | | | Fixes: e17f9fd0e8a9 ("bcm47xx: revert bgmac back to the old limited max frame size") Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit 83aeb0bbd47638b42ee6cdda351d0c51e014d790)
* bcm47xx: revert bgmac back to the old limited max frame sizeRafał Miłecki2023-07-101-0/+33
| | | | | | | | | | | | | | | Bumping max frame size has significantly affected network performance and memory usage. It was done by upstream commit that first appeared in the 5.7 release. Allocating 512 (BGMAC_RX_RING_SLOTS) buffers, 10 k each, is clearly a bad idea on 32 MiB devices. This commit fixes support for Linksys E1000 V2.1 which gives up after allocating ~346 such buffers running 5.15 kernel. Ref: 230c9da963aa ("bcm53xx: revert bgmac back to the old limited max frame size") Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit 4970dd027bced78f8a72aa2baed22c962d3b587b)
* ipq-wifi: fix upstream board-2.bin ZTE M289F snafuChristian Lamparter2023-07-041-1/+1
| | | | | | | | | | | | | | | | | | | | | | | The upstream board-2.bin file in the linux-firmware.git repository for the QCA4019 contains a packed board-2.bin for this device for both 2.4G and 5G wifis. This isn't something that the ath10k driver supports. Until this feature either gets implemented - which is very unlikely -, or the upstream boardfile is mended (both, the original submitter and ath10k-firmware custodian have been notified). OpenWrt will go back and use its own bespoke boardfile. This unfortunately means that 2.4G and on some revisions the 5G WiFi is not available in the initramfs image for this device. qca9984 isn't affected. Fixes: #12886 Reported-by: Christian Heuff <christian@heuff.at> Debugged-by: Georgios Kourachanis <geo.kourachanis@gmail.com> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> (cherry picked from commit 75505c5ec724b9b961dcb411bac1d4b9aede3e1d)
* kernel: bump 5.10 to 5.10.186Hauke Mehrtens2023-07-017-15/+15
| | | | | | All patches automatically rebased. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump 5.10 to 5.10.185Hauke Mehrtens2023-07-0119-57/+25
| | | | | | | | | Removed because upstreamed: uml/patches-5.10/001-um-Fix-build-w-o-CONFIG_PM_SLEEP.patch All other patches automatically rebased. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump 5.10 to 5.10.184Hauke Mehrtens2023-06-1531-67/+66
| | | | | | | | | Manually rebased: generic/pending-5.10/851-0004-Revert-ata-ahci-mvebu-Make-SATA-PHY-optional-for-Arm.patch All other patches automatically rebased. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump 5.10 to 5.10.183Hauke Mehrtens2023-06-1512-24/+25
| | | | | | | | All patches automatically rebased. Deactivate new option CONFIG_DRM_RCAR_USE_LVDS by default. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* bcm63xx: fix NETGEAR DGND3700v2 boot loopÁlvaro Fernández Rojas2023-06-151-0/+1
| | | | | | | | | | | | | The DGND3700v2 renames the cferam bootloader from cferam to cfeXXX, where XXX is the number of firmware upgrades performed by the bootloader. Other bcm63xx devices rename cferam.000 to cferam.XXX, but this device is special because the cferam name isn't changed on the first firmware flashing but it's changed on the subsequent ones. Therefore, we need to look for "cfe" instead of "cferam" to properly detect the cferam partition and fix the bootlop. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com> (cherry picked from commit cdfcac6e246de9f237d1425e498db3f34ddebbaf)
* bmips: fix NETGEAR DGND3700v2 boot loopÁlvaro Fernández Rojas2023-06-151-0/+1
| | | | | | | | | | | | | The DGND3700v2 renames the cferam bootloader from cferam to cfeXXX, where XXX is the number of firmware upgrades performed by the bootloader. Other bcm63xx devices rename cferam.000 to cferam.XXX, but this device is special because the cferam name isn't changed on the first firmware flashing but it's changed on the subsequent ones. Therefore, we need to look for "cfe" instead of "cferam" to properly detect the cferam partition and fix the bootlop. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com> (cherry picked from commit 915e914cfaa243ea36f8c7a4f0f045ec890304fa)
* kernel: mtd: bcm-wfi: add cferam name supportÁlvaro Fernández Rojas2023-06-151-2/+14
| | | | | | | | | Some devices rename cferam bootloader using specific patterns and don't follow broadcom standards for renaming cferam files. This requires supporting different cferam file names. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com> (cherry picked from commit 8813edd8d9695d4e3939fdaa3c530c682f91de11)
* kernel: bump 5.10 to 5.10.181Hauke Mehrtens2023-06-0311-30/+30
| | | | | | All patches automatically rebased. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump 5.10 to 5.10.180Hauke Mehrtens2023-06-0321-103/+57
| | | | | | | Deleted because it was applied upstream ipq806x/patches-5.10/103-ARM-dts-qcom-reduce-pci-IO-size-to-64K.patch Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* ramips: add support for Keenetic Lite III rev. AAlexey Bartenev2023-06-034-0/+163
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | General specification: SoC Type: MediaTek MT7620N (580MHz) ROM: 8 MB SPI-NOR (W25Q64FV) RAM: 64 MB DDR (EM6AB160TSD-5G) Switch: MediaTek MT7530 Ethernet: 5 ports - 5×100MbE (WAN, LAN1-4) Wireless: 2.4 GHz (MediaTek RT5390): b/g/n Buttons: 3 button (POWER, RESET, WPS) Slide switch: 4 position (BASE, ADAPTER, BOOSTER, ACCESS POINT) Bootloader: U-Boot 1.1.3 Power: 9 VDC, 0.6 A MAC in stock: |- + | | LAN | RF-EEPROM + 0x04 | | WLAN | RF-EEPROM + 0x04 | | WAN | RF-EEPROM + 0x28 | OEM easy installation 1. Use a PC to browse to http://my.keenetic.net. 2. Go to the System section and open the Files tab. 3. Under the Files tab, there will be a list of system files. Click on the Firmware file. 4. When a modal window appears, click on the Choose File button and upload the firmware image. 5. Wait for the router to flash and reboot. OEM installation using the TFTP method 1. Download the latest firmware image and rename it to klite3_recovery.bin. 2. Set up a Tftp server on a PC (e.g. Tftpd32) and place the firmware image to the root directory of the server. 3. Power off the router and use a twisted pair cable to connect the PC to any of the router's LAN ports. 4. Configure the network adapter of the PC to use IP address 192.168.1.2 and subnet mask 255.255.255.0. 5. Power up the router while holding the reset button pressed. 6. Wait approximately for 5 seconds and then release the reset button. 7. The router should download the firmware via TFTP and complete flashing in a few minutes. After flashing is complete, use the PC to browse to http://192.168.1.1 or ssh to proceed with the configuration. Signed-off-by: Alexey Bartenev <41exey@proton.me> (cherry picked from commit dc79b51533cfe9a7806353f6c6fd6b22cd80d536)
* ipq-wifi: drop custom board-2.binsChristian Lamparter2023-05-272-33/+20
| | | | | | | | | | | | | The BDFs for all boards were upstreamed to the ath10k-firmware repository and linux-firmware.git. We switched to the upstream board-2.bin, hence the files can be removed here. Keep the ipq-wifi package in case new boards are added. It might take some time till board-2.bins send upstream are merged. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-05 10:13:05 +0000