aboutsummaryrefslogtreecommitdiffstats
path: root/target
Commit message (Collapse)AuthorAgeFilesLines
* 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>
* ipq40xx: R619AC: replace space with - separator in variant stringChristian Lamparter2023-05-271-2/+2
| | | | | | | | | | | | | | Kalle: "I see that variant has a space in it, does that work it correctly? My original idea was that spaces would not be allowed, but didn't realise to add a check for that." Is this an easy change? Because the original author (Tim Davis) noted: "You may substitute the & and space with something else saner if they prove to be problematic." Signed-off-by: Christian Lamparter <chunkeey@gmail.com> (cherry picked from commit 3b3eaf31cbf4d680a55e3c14edb59606409dd821)
* ramips: correct page read return value of the mt7621 nand driverShiji Yang2023-05-271-5/+9
| | | | | | | | | | | | | | read_page() need to return maximum number of bitflips instead of the accumulated number. Change takes from upstream mt7621 u-boot [1]. * @read_page: function to read a page according to the ECC generator * requirements; returns maximum number of bitflips * corrected in any single ECC step, -EIO hw error [1] https://lore.kernel.org/all/cover.1653015383.git.weijie.gao@mediatek.com/ Signed-off-by: Shiji Yang <yangshiji66@qq.com> (cherry picked from commit 2fbb91d73ffecc7d033e5bb0b550d664ef9e0f91)
* kernel: bump 5.10 to 5.10.179John Audia2023-05-065-7/+7
| | | | | | | | | All patches automatically rebased. Signed-off-by: John Audia <therealgraysky@proton.me> [Refresh patches on openwrt-22.03 branch] Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> (cherry picked from commit 80c1105b0339516344f12364a599070ab1c9a41a)
* kernel: bump 5.10 to 5.10.178John Audia2023-05-0623-117/+48
| | | | | | | | | | | | | | Removed upstreamed: backport-5.10/430-v6.3-ubi-Fix-failure-attaching-when-vid_hdr-offset-equals.patch[1] 1. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.10.178&id=0279e82e148407feec88466990de14bcba9e12c0 All other patches automatically rebased. Signed-off-by: John Audia <therealgraysky@proton.me> [Refresh patches on openwrt-22.03 branch] Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> (cherry picked from commit 126c64df2bb6dec95906c1f68aa37e581ef2550f)
* kernel: bump 5.10 to 5.10.177John Audia2023-05-0613-26/+27
| | | | | | | | | All patches automatically rebased. Signed-off-by: John Audia <therealgraysky@proton.me> [Refresh patches on openwrt-22.03 branch] Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> (cherry picked from commit 78a468f690a0f3052ff68ef33910705b25bac33d)
* ramips: mt7621: add support for Cudy X6 v2Felix Baumann2023-05-045-51/+145
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Rename existing device to v1 and create common .dtsi Difference to v1: 16MB Flash Specifications: SoC: MediaTek MT7621 RAM: 256 MB Flash: 16 MB (SPI NOR, XM25QH128C on my device) WiFi: MediaTek MT7915E Switch: 1 WAN, 4 LAN (Gigabit) Buttons: Reset, WPS LEDs: Two Power LEDs (blue and red; together they form purple) Power: DC 12V 1A center positive Serial: 115200 8N1 C440 - (3V3 - GND - RX - TX) - C41 | v1 and v2 (P - G - R - T) | v2 labels them on the board Installation: Download and flash the manufacturer's built OpenWrt image available at http://www.cudytech.com/openwrt_software_download Install the new OpenWrt image via luci (System -> Backup/Flash firmware) Be sure to NOT keep settings. Recovery: Loads only signed manufacture firmware due to bootloader RSA verification Serve tftp-recovery image as /recovery.bin on 192.168.1.88/24 Connect to any lan ethernet port Power on the device while holding the reset button Wait at least 8 seconds before releasing reset button for image to download MAC addresses as verified by OEM firmware: use address source LAN f4:a4:54:86:75:a2 label WAN f4:a4:54:86:75:a3 label + 1 2g f4:a4:54:86:75:a2 label 5g f6:a4:54:b6:75:a2 label + LA-Bit set + 4th oktet increased The label MAC address is found in bdinfo 0xde00. Signed-off-by: Felix Baumann <felix.bau@gmx.de> (cherry picked from commit e38de40f8dd350344407fe5a91e81191f6960804)
* ramips: Cudy X6 fixes / improvementsFelix Baumann2023-04-303-16/+19
| | | | | | | | | | | | | | | | | | | | | | | - Correct WiFi MACs, they didn't match oem firmware - Move nvmem-cells to bdinfo partition and remove &bdinfo reference - Add OEM device model name R13 to SUPPORTED_DEVICES This allows sysupgrading from Cudy's OpenWrt fork without force - Label red_led and use it during failsafe mode and upgrades MAC addresses as verified by OEM firmware: use address source LAN b4:4b:d6:2d:c8:4a label WAN b4:4b:d6:2d:c8:4b label + 1 2g b4:4b:d6:2d:c8:4a label 5g b6:4b:d6:3d:c8:4a label + LA-Bit set + 4th oktet increased The label MAC address is found in bdinfo 0xde00. Signed-off-by: Felix Baumann <felix.bau@gmx.de> [read wifi mac from flash offset] Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit 45cf200b2e22c34f2ae043b87e24230de526fefc)
* ramips: reduce Archer AX23 / MR70X SPI-frequencyDavid Bauer2023-04-272-2/+2
| | | | | | | | | | | | | | | It was brought to attention the Archer AX23 v1 fails to read jffs2 data from time to time. While this is not reproducible on my unit, it is on others. Reducing the SPI frequency does the trick. While it worked with at lest 40 MHz, opt for the cautious side and choose a save frequency of 25 MHz. Apply the same treatment to the Mercusys MR70X which uses a similar design just in case. Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit 2c530fcb972c112e7a2b10f9c21ac6d276624b5e)
* ramips: fix lzma-loader for buffalo_WSR_600DHPHaoan Li2023-04-231-0/+1
| | | | | | | | | This fixes a well known "LZMA ERROR 1" error, reported previously on numerous of similar devices. Fixes: #11919 Signed-off-by: Haoan Li <lihaoan1001@163.com> (cherry picked from commit c7b484f3647c58da2f86395228a9927290a6f6ed)
* ath79: create Aruba AP-105 APBoot compatible imageDavid Bauer2023-04-181-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Alter the Aruba AP-105 image generation process so OpenWrt can be loaded with the vendor Aruba APBoot. This works by prepending the OpenWrt LZMA loader to the uImage and jumping directly to the loader. Aruba does not offer bootm on these boards. This approach keeps compatibility to devices which had their U-Boot replaced. Both bootloaders can boot the same image. The same modification is most likely also possible for the Aruba AP-175. With this patch, new installations do not require replacing the bootloader and can be performed from the serial console without opening the case. Installation ------------ 1. Attach to the serial console of the AP-105. Interrupt autoboot and change the U-Boot env. $ setenv apb_rb_openwrt "setenv ipaddr 192.168.1.1; setenv serverip 192.168.1.66; netget 0x84000000 ap105.bin; go 0x84000040" $ setenv apb_fb_openwrt "cp.b 0xbf040000 0x84000000 0x10000; go 0x84000040" $ setenv bootcmd "run apb_fb_openwrt" $ saveenv 2. Load the OpenWrt initramfs image on the device using TFTP. Place the initramfs image as "ap105.bin" in the TFTP server root directory, connect it to the AP and make the server reachable at 192.168.1.66/24. $ run apb_rb_openwrt 3. Once OpenWrt booted, transfer the sysupgrade image to the device using scp and use sysupgrade to install the firmware. Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit e11d00d44c66b1534fbc399fda55951cd0a2168a)
* kernel: backport fix for recently introduced UBI bugDaniel Golle2023-04-152-2/+71
| | | | | | | | | | Import commit "ubi: Fix failure attaching when vid_hdr offset equals to (sub)page size" which did not yet make it to stable upstream Linux trees. Fixes: #12232 Fixes: #12339 Signed-off-by: Daniel Golle <daniel@makrotopia.org> (cherry picked from commit aad34818b50029e07ed9221ae46f9770d6e29785)
* imagebuilder: allow to specific ROOTFS_PARTSIZEPaul Spooren2023-04-091-1/+3
| | | | | | | | | | | | Setting this options modifies the rootfs size of created images. When installing a large number of packages it may become necessary to increase the size to have enough storage. This option is only useful for supported devices, i.e. with an attached SD Card or installed on a hard drive. Signed-off-by: Paul Spooren <mail@aparcar.org> (cherry picked from commit 7b7edd25a571568438c886529d3443054e02f55f)
* ramips: define remapping-range for DAP-X1860David Bauer2023-04-081-0/+7
| | | | | | | | | | Prevent the BBT translation layer from remapping the UBI used for storing rootfs. Explicitly define the number of blocks reserved for remapping. Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit 076da59f17803e9412ef5e50988aff6c7e536292)
* ramips: add support for D-Link DAP-X1860 A1Sebastian Schaper2023-04-086-0/+234
| | | | | | | | | | | | | | | | | | | | | | | | | | | | The DAP-X1860 is a wall-plug AX1800 repeater. Specifications: - MT7621, 256 MiB RAM, 128 MiB SPI NAND - MT7915 + MT7975 2x2 802.11ax (DBDC) - Ethernet: 1 port 10/100/1000 - LED RSSI bargraph (2x green, 1x red/orange), status and RSSI LEDs are incorrectly populated red/orange (should be red/green according to documentation) Installation: - Keep reset button pressed during plug-in - Web Recovery Updater is at 192.168.0.50 - Upload factory.bin, confirm flashing (seems to work best with Chromium-based browsers) Revert to OEM firmware: - tar -xvf DAP-X1860_RevA_Firmware_101b94.bin - openssl enc -d -md md5 -aes-256-cbc -in FWImage.st2 \ -out FWImage.st1 -k MB0dBx62oXJXDvt12lETWQ== - tar -xvf FWImage.st1 - flash kernel_DAP-X1860.bin via Recovery Signed-off-by: Sebastian Schaper <openwrt@sebastianschaper.net> (cherry picked from commit 3c31f6b521bb5fc49e222a8f2bcd454b73452a0e)
* ramips: lower re305-v3 spi-max-frequencyJoe Mullally2023-04-081-1/+1
| | | | | | | | | | | | | | Fix flash I/O instability observed in newer devices with cFeon QH64A-104HIP (detected as en25qh64). Ref: https://forum.openwrt.org/t/support-for-tp-link-re305-v3/75893/91 Reported-by: Dimitri Souza <dimitri.souza@gmail.com> Tested-by: Dimitri Souza <dimitri.souza@gmail.com> Signed-off-by: Joe Mullally <jwmullally@gmail.com> [alter commit-message - target master] Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit 2122c80b321d439cf8b669ae26fcfeec605cf2cc)
* lantiq: fix lzma-loader for Netgear DGN 3500(B)Maik Goette2023-04-022-5/+18
| | | | | | | | Fixes Uncompressing Kernel Image ... ERROR: LzmaDecode.c, 561 Fixes: #11701 for both 3500(B) Signed-off-by: Maik Goette <github@beeit.de> (cherry picked from commit 4d9c38d654fdfb72ef641573bbf5b0f73f638f2e)
* ath79: tiny: Do not build TPLink WPA8630Pv2 by defaultJoe Mullally2023-04-021-0/+1
| | | | | | | | | | | 22.03.1+ and snapshot builds no longer fit the 6M flash space available for these models. This disables failing buildbot image builds for these devices. Images can still be built manually with ImageBuilder. Signed-off-by: Joe Mullally <jwmullally@gmail.com> (cherry picked from commit 4965cbd259bb9001e8724f53520f4be1e4723212)
* ramips: mt7621: mikrotik 760igs (hEX S) fix SFPJohn Thomson2023-04-021-0/+1
| | | | | | | | | | | | | | This device uses an AR8031/AR8033 chip to convert SoC gmac1 RGMII to 1000base-x or sgmii for the SFP fibre cage. The SFP cage requires phy-mode rgmii-rxid, and without it will not recieve any packets: ethtool -S sfp rx_fcs_errors will increase when packets should be being received, but no other _rx counters will change. Fixes: c77858aa792 ("ramips: mt7621-dts: change phy-mode of gmac1 to rgmii") Reviewed-by: Robert Marko <robimarko@gmail.com> Reviewed-by: Arınç ÜNAL <arinc.unal@arinc9.com> Signed-off-by: John Thomson <git@johnthomson.fastmail.com.au> (cherry picked from commit 7ea965b57803ceec20222279377e611652ac217f)
* ath79: use lzma-loader for Senao initramfs imagesMichael Pratt2023-04-021-0/+1
| | | | | | | | | | Some vendors of Senao boards have put a bootloader that cannot handle both large gzip or large lzma files. There is no disadvantage by doing this for all of them. Signed-off-by: Michael Pratt <mcpratt@pm.me> (cherry picked from commit 8342c092a03caedbf160d4ac3982c6a9be91261f)
* ath79: Fix glinet ar300m usb not workingLuo Chongjun2023-04-022-13/+8
| | | | | | | | | | | | | | | | | | | glinet forum users reported the problem at https://forum.gl-inet.com/t/gl-ar300m16-openwrt-22-03-0-rc5-usb-port-power-off-by-default/23199 The current code uses the regulator framework to control the USB power supply. Although usb0 described in DTS refers to the regulator by vbus-supply, but there is no code related to regulator implemented in the USB driver of QCA953X, so the USB of the device cannot work. Under the regulator framework, adding the regulator-always-on attribute fixes this problem, but it means that USB power will not be able to be turned off. Since we need to control the USB power supply in user space, I didn't find any other better way under the regulator framework of Linux, so I directly export gpio. Signed-off-by: Luo Chongjun <luochongjun@gl-inet.com> (cherry picked from commit b352124cd2115fec648a00956a848660df9477d3)
* ramips: rt5350: enable lzma-loader for ALLNET ALL5003Sergio Paracuellos2023-04-021-0/+1
| | | | | | | | Fixes the boot loader LZMA decompression issue: LZMA ERROR 1 - must RESET board to recover Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com> (cherry picked from commit 84c04ff4069a652755267d126418b211379c1cbf)
* sdk: expose PATENTED an NLS build optionsTomasz Maciej Nowak2023-04-021-0/+17
| | | | | | | | | | Some packages offer functionalities guarded by these options and it'll be impossible to reach them without changing Config-build.in. So allow to toggle these in more friendly way, by exposing them in configuration menu. Signed-off-by: Tomasz Maciej Nowak <tmn505@gmail.com> (cherry picked from commit 477ff0821a5e532adc0861d4093029967f5e1178)
generated by cgit v1.2.3 (git 2.25.1) at 2024-10-30 22:53:28 +0000