aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux
Commit message (Collapse)AuthorAgeFilesLines
* kernel: bump 5.10 to 5.10.178John Audia2023-04-2218-110/+41
| | | | | | | | | | | 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>
* kernel: bump 5.15 to 5.15.108John Audia2023-04-2225-195/+41
| | | | | | | | | | | | | | | | | Removed upstreamed: backport-5.15/430-v6.3-ubi-Fix-failure-attaching-when-vid_hdr-offset-equals.patch[1] backport-5.15/612-v6.3-skbuff-Fix-a-race-between-coalescing-and-releasing-S.patch[2] All other patches automatically rebased. 1. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.15.108&id=85d7a7044b759d865d10395a357632af00de5867 2. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.15.108&id=906a6689bb0191ad2a44131a3377006aa098af59 Build system: x86_64 Build-tested: bcm2711/RPi4B, ramips/tplink_archer-a6-v3, filogic/xiaomi_redmi-router-ax6000-ubootmod Run-tested: bcm2711/RPi4B, ramips/tplink_archer-a6-v3, filogic/xiaomi_redmi-router-ax6000-ubootmod Signed-off-by: John Audia <therealgraysky@proton.me>
* generic: update nvmem cell mac-address-ascii supportChukun Pan2023-04-212-42/+52
| | | | | | | | Instead of use mac-address-ascii in nvmem_get_mac_address function, move it into of_get_mac_addr_nvmem function to support more devices. Signed-off-by: Chukun Pan <amadeus@jmu.edu.cn>
* ramips: MSG1500 X.00: switch to mac-address-ascii dtsChukun Pan2023-04-213-17/+30
| | | | | | | | The Config partition of some machines is special, and the openwrt script cannot read the protest_lan_mac correctly. This problem can be solved by reading the mac address (ascii) in dts. Signed-off-by: Chukun Pan <amadeus@jmu.edu.cn>
* mediatek: filogic: remove redundant code for tuf-ax4200Chukun Pan2023-04-211-2/+1
| | | | | | Remove redundant code in 02_network. Signed-off-by: Chukun Pan <amadeus@jmu.edu.cn>
* mediatek: filogic: move mac address setting togetherChukun Pan2023-04-211-4/+6
| | | | | | Simultaneously sort in the order of letters. Signed-off-by: Chukun Pan <amadeus@jmu.edu.cn>
* mediatek: filogic: fix network config for mt7986a-rfbChukun Pan2023-04-211-1/+3
| | | | | | | Fix the network configuration according to the device tree. Fixes: 5faff99 ("mediatek: filogic: fix mt7986a ethernet devicetree entries") Signed-off-by: Chukun Pan <amadeus@jmu.edu.cn>
* mediatek: filogic: update kernel config-5.15Daniel Golle2023-04-201-1/+4
| | | | | | | Expose thermal-zone as hwmon sensor, remove thermal emulation driver and add some missing symbols. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* mediatek: bpi-r3: allow up to 3W per SFP moduleDaniel Golle2023-04-201-0/+2
| | | | | | | | | According to SinoVoip up to 3A @ 3.3V are available for both SFP modules together. Raise energy limit from 1W (default) to 3W, however, be aware that using modules consuming more than 1W will require active cooling! Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* kernel: bump 5.15 to 5.15.107John Audia2023-04-199-18/+18
| | | | | | | | | | All patches automatically rebased. Build system: x86_64 Build-tested: bcm2711/RPi4B, ramips/tplink_archer-a6-v3, filogic/xiaomi_redmi-router-ax6000-ubootmod Run-tested: bcm2711/RPi4B, ramips/tplink_archer-a6-v3, filogic/xiaomi_redmi-router-ax6000-ubootmod Signed-off-by: John Audia <therealgraysky@proton.me>
* bmips: pci-bcm6348: load IO resource from DT rangesÁlvaro Fernández Rojas2023-04-183-28/+14
| | | | | | Correctly load IO resource from DT ranges and remove the specific IO resource. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bmips: drop unneeded ath9k fixupÁlvaro Fernández Rojas2023-04-182-243/+1
| | | | | | | We no longer need the custom ath9k fixup now that we're using the standard kmod-owl-loader. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bmips: hg556a: switch to kmod-owl-loaderÁlvaro Fernández Rojas2023-04-183-14/+66
| | | | | | Stop using custom ath9k fixup and switch to standard kmod-owl-loader Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* ath79: mikrotik: update kernel on NAND using YafutMichał Kępień2023-04-183-8/+5
| | | | | | | | | | | | | | | | | | | | | Instead of erasing the entire NAND partition holding the kernel during every system upgrade and then flashing a Yaffs file system image prepared using kernel2minor (not accounting for bad blocks in the process), use the Yafut utility to replace the kernel executable on MikroTik NAND devices, preserving the existing Yaffs file system (including bad block information) on the partition holding the kernel. Add Yafut to DEFAULT_PACKAGES for the ath79/mikrotik target, so that the tool is included in the initramfs images created when building for multiple profiles. However, exclude Yafut from the images built for MikroTik devices with NOR flash as the tool is currently only meant to be used on devices with NAND flash. As this addresses the concerns for MikroTik NAND devices discussed in commit 9d96b6fb72 ("ath79/mikrotik: disable building NAND images"), re-enable building images for these devices. Signed-off-by: Michał Kępień <openwrt@kempniu.pl>
* kernel: backport MEMREAD ioctlMichał Kępień2023-04-1815-17/+908
| | | | | | | | | MEMREAD is a new ioctl for MTD character devices that was first included in Linux 6.1. It allows userspace applications to use the Linux kernel's OOB autoplacement mechanism while reading data from NAND devices. The Yafut tool needs this ioctl to do its job. Signed-off-by: Michał Kępień <openwrt@kempniu.pl>
* ath79: mikrotik: drop unused files from ramdiskMichał Kępień2023-04-181-2/+1
| | | | | | | | | | | | | | | | | | | The ramdisk used by sysupgrade on MikroTik devices currently includes U-Boot fw_* files that are not necessary for performing a system upgrade on that platform. The relevant lines were added to target/linux/ath79/mikrotik/base-files/lib/upgrade/platform.sh by commit a66eee6336 ("ath79: add mikrotik subtarget"), likely because they also existed in target/linux/ath79/nand/base-files/lib/upgrade/platform.sh, where the platform_do_upgrade_mikrotik_nand() function moved by commit a66eee6336 originally lived. However, these lines were added to target/linux/ath79/nand/base-files/lib/upgrade/platform.sh by commit 55e6c903ae ("ath79: GL-AR300M: provide NAND support; increase to 4 MB kernel"), which is not related to MikroTik devices in any way. Remove the code adding unused U-Boot fw_* files to the ramdisk used by sysupgrade on MikroTik devices. Signed-off-by: Michał Kępień <openwrt@kempniu.pl>
* 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>
* ath79: fix LED pinout for Comfast CF-E314N v2Mark Onstid2023-04-171-6/+6
| | | | | | | | | | | | In addition to standardizing LED names to match the rest of the systems, this commit fixes a possibly erroneous pinout for LEDs in Comfast CF-E314N v2. In particular, rssimediumhigh and rssihigh are moved from pins 13 and 14 to 14 and 16 respectively. In addition to working on a test device, this pinout better matches the one set out in the prototype support patch for the device in Github PR #1873. Signed-off-by: Mark Onstid <turretkeeper@mail.com>
* ramips: add Xiaomi RA75 red signal ledOleksandr Zharov2023-04-171-0/+11
| | | | | | | | | | | | | | | | | RA75 has 5 physical LEDs under 2 indicators, mixed with light pipes: Indicator "System": GPIO0: blue GPIO2: amber Indicator "Signal": GPIO44: blue GPIO37: amber GPIO46: red All except GPIO46 were already added by Jo Deisenhofer. GPIO46 is used for UART1 by default, so it needs additional pin control change in devicetree to be operational. Verified on my RA75. Signed-off-by: Oleksandr Zharov <alex.zeed@gmail.com>
* ipq40xx: convert AP-365 to DSADavid Bauer2023-04-152-2/+2
| | | | | | | | | Re-enable the Aruba AP-365 with DSA support. Changes are trvivial, as the board design is pretty much the already updated AP-303. Run-tested on the device. Signed-off-by: David Bauer <mail@david-bauer.net>
* kernel: backport fix for recently introduced UBI bugDaniel Golle2023-04-154-4/+142
| | | | | | | | | 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>
* kernel: backport fix for a page pool related race conditionFelix Fietkau2023-04-142-0/+170
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* generic: move accepted patch to backport-5.15Daniel Golle2023-04-132-13/+37
| | | | | | | | | | The patch adding SFP quirk for MXPD 483II was accepted upstream and will be part of Linux v6.3: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=ad651d68cee75e9ac20002254c4e5d09ee67a84b Move the patch from pending-5.15 to backport-5.15. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* mediatek: sync pinctrl-mt7981 and pinctrl-mt7986 driversDaniel Golle2023-04-132-25/+150
| | | | | | | Now that new pinconf features have been backported sync pinctrl-mt7981 and pinctrl-m7986 with bleeding-edge upstream versions. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* mediatek: backport new pinctrl featuresDaniel Golle2023-04-137-0/+1077
| | | | | | | | Backport new features for MediaTek pinctrl/pinconf drivers from upstream. This will serve as the base to improve pinconf bias/pull-up/pull-down on MT7981 and MT7986, and also prepare for upcoming support for MT7988. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* mvebu: puzzle-mcu: add mcu write retry functionIan Chang2023-04-132-0/+126
| | | | | | | Avoid MCU getting "command reply receive timed out" message when LED configuration setting trigger function is enabled in heartbeat mode. Signed-off-by: Ian Chang <ianchang@ieiworld.com>
* base-files: fix Linksys upgrade, restore config stepMichael Trinidad2023-04-112-2/+2
| | | | | | | | | | | | | It appears that the refactor of the upgrade process for NAND devices resulted in the nand_do_upgrade_success step not being called for devices using the linksys.sh script. As a result, configuration was not preserved over sysupgrade steps. This corrects a typo in the call of nand_do_upgrade_failed for ipq40xx and ipq806x devices using the linksys.sh script. Fixes: 8634c1080d50 ("ipq40xx: Fix Linksys upgrade, restore config step") Fixes: 2715aff5df83 ("ipq806x: Fix Linksys upgrade, restore config step") Signed-off-by: Michael Trinidad <trinidude4@hotmail.com>
* mvebu: cortexa9: fix Linksys upgrade, restore config stepMichael Trinidad2023-04-111-1/+6
| | | | | | | | | | | | It appears that the refactor of the upgrade process for NAND devices resulted in the nand_do_upgrade_success step not being called for devices using the linksys.sh script. As a result, configuration was not preserved over sysupgrade steps. This restores the preservation of configs for mvebu/cortexa9 devices using the linksys.sh script. Fixes: e25e6d8e5407 ("base-files: fix and clean up nand sysupgrade code") Signed-off-by: Michael Trinidad <trinidude4@hotmail.com>
* kirkwood: fix Linksys upgrade, restore config stepMichael Trinidad2023-04-111-1/+6
| | | | | | | | | | | | | | It appears that the refactor of the upgrade process for NAND devices resulted in the nand_do_upgrade_success step not being called for devices using the linksys.sh script. As a result, configuration was not preserved over sysupgrade steps. This restores the preservation of configs for kirkwood devices using the linksys.sh script. Fixes: e25e6d8e5407 ("base-files: fix and clean up nand sysupgrade code") Fixes: #12298 Signed-off-by: Michael Trinidad <trinidude4@hotmail.com>
* bcm53xx: switch to Kernel 5.15 by defaultPaul Spooren2023-04-101-2/+1
| | | | | | | Getting ready for the next release. Signed-off-by: Paul Spooren <mail@aparcar.org> Tested-by: Rafał Miłecki <rafal@milecki.pl>
* bcm4908: switch to Kernel 5.15 by defaultPaul Spooren2023-04-101-2/+1
| | | | | | | | Getting ready for the next release. Signed-off-by: Paul Spooren <mail@aparcar.org> [rmilecki: tested on GT-AC5300: boot, sysupgrade & 940 Mbps NAT] Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bmips: dts: add missing phy modesÁlvaro Fernández Rojas2023-04-105-0/+17
| | | | | | PHY modes should be defined in the device tree for the bcm63xx internal switch. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bmips: remove source-only flagÁlvaro Fernández Rojas2023-04-101-1/+1
| | | | | | | | bmips target is now more stable and it's time to start generating buildbot images in order to receive a wider testing, which will be essential to replace bcm63xx target in the future. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bmips: add subtargets for each SoCÁlvaro Fernández Rojas2023-04-1049-382/+2037
| | | | | | | | BMIPS is a generic arch that can be used for multiple Broadcom SoCs, each one with its own specific drivers, so instead of having a huge kernel supporting all of them, let's switch to a subtarget per SoC like other OpenWrt targets. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bmips: b43-sprom: fix build when SSB/BCMA disabledÁlvaro Fernández Rojas2023-04-101-16/+16
| | | | | | Fix build of B43 SPROM fallback when SSB or BCMA are disabled. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bmips: allow disabling mdio-mux-bcm6368Álvaro Fernández Rojas2023-04-101-0/+10
| | | | | | This controller is only present on SoCs with B53 MMAP switch. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* kernel: disable CONFIG_HW_RANDOM_BCM2835Álvaro Fernández Rojas2023-04-101-0/+1
| | | | | | This HW RNG is present on some Broadcom 63XX SoCs, but not all of them. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* kernel: bump 5.15 to 5.15.106John Audia2023-04-097-218/+5
| | | | | | | | | | | | | | | | | | Removed upstreamed: generic/735-net-ethernet-mtk_eth_soc-fix-flow_offload-related-re.patch[1] pending-5.15/350-mips-bmips-BCM6358-disable-RAC-flush-for-TP1.patch[2] All other patches automatically rebased. 1. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.15.106&id=76f09582a191dcf11118fd4bdbf50f538c90fa8d 2. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/arch/mips/bmips?h=v5.15.106&id=65b723644294f1d79770704162c0e8d1f700b6f1 Build system: x86_64 Build-tested: bcm2711/RPi4B, ramips/tplink_archer-a6-v3, filogic/xiaomi_redmi-router-ax6000-ubootmod, ipq806x/R7800 Run-tested: bcm2711/RPi4B, ramips/tplink_archer-a6-v3, filogic/xiaomi_redmi-router-ax6000-ubootmod, ipq806x/R7800 Signed-off-by: John Audia <therealgraysky@proton.me>
* bmips: switch to LED kernel modulesÁlvaro Fernández Rojas2023-04-093-13/+19
| | | | | | | Disable LED controllers from kernel config and switch to per device kernel modules. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bmips: add LED kernel modulesÁlvaro Fernández Rojas2023-04-091-0/+30
| | | | | | | Add BCM6328 and BCM6358 LED kernel modules. This allows selecting the LED controllers only for those devices using them. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bmips: add support for Sercomm SHG2500Álvaro Fernández Rojas2023-04-096-1/+776
| | | | | | | | Sercomm SHG2500 is a BCM63168 with 128M of RAM, 256M of NAND, an external BCM53124S switch for the LAN ports and internal/external Broadcom wifi. LEDs are connected to an external MSP430G2513 MCU controlled via SPI. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bmips: use sercomm-pid scriptÁlvaro Fernández Rojas2023-04-092-21/+14
| | | | | | | Make use of sercomm-pid script for generating the Sercomm PID, which avoids having to add an array of hex bytes for every new Sercomm device. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bmips: image: rename SERCOMM_VERSION to SERCOMM_FSVERÁlvaro Fernández Rojas2023-04-092-7/+7
| | | | | | | SERCOMM_VERSION is ambiguous and it should be more clear that it refers to the version used for the filesystem. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* ramips: sercomm-payload: use pide-file argumentÁlvaro Fernández Rojas2023-04-091-1/+1
| | | | | | | Instead of passing an array of hex bytes for the Sercomm PID we can now use the --pid-file parameter. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* kernel: bump 5.10 to 5.10.177John Audia2023-04-088-13/+13
| | | | | | All patches automatically rebased. Signed-off-by: John Audia <therealgraysky@proton.me>
* 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>
* mpc85xx: refresh patchesDavid Bauer2023-04-082-3/+3
| | | | Signed-off-by: David Bauer <mail@david-bauer.net>
* mpc85xx: add support for Enterasys WS-AP3715iDavid Bauer2023-04-0812-2/+507
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Hardware -------- SoC: NXP P1010 (1x e500 @ 800MHz) RAM: 256M DDR3 (2x Samsung K4B1G1646G-BCH9) FLASH: 32M NOR (Spansion S25FL256S) BTN: 1x Reset WiFi: 1x Atheros AR9590 2.4 bgn 3x3 2x Atheros AR9590 5.0 an 3x3 ETH: 2x Gigabit Ethernet (Atheros AR8033 / AR8035) UART: 115200 8N1 (RJ-45 Cisco) Installation ------------ 1. Grab the OpenWrt initramfs, rename it to ap3715.bin. Place it in the root directory of a TFTP server and serve it at 192.168.1.66/24. 2. Connect to the serial port and boot the AP. Stop autoboot in U-Boot by pressing Enter when prompted. Credentials are identical to the one in the APs interface. By default it is admin / new2day. 3. Alter the bootcmd in U-Boot: $ setenv ramboot_openwrt "setenv ipaddr 192.168.1.1; setenv serverip 192.168.1.66; tftpboot 0x2000000 ap3715.bin; bootm" $ setenv boot_openwrt "sf probe 0; sf read 0x2000000 0x140000 0x1000000; bootm 0x2000000" $ setenv bootcmd "run boot_openwrt" $ saveenv 4. Boot the initramfs image $ run ramboot_openwrt 5. Transfer the OpenWrt sysupgrade image to the AP using SCP. Install using sysupgrade. $ sysupgrade -n <path-to-sysupgrade.bin> Signed-off-by: David Bauer <mail@david-bauer.net>
* mpc85xx: don't compress kernel image for WS-AP3825iDavid Bauer2023-04-081-1/+1
| | | | | | | The kernel is already compressed with XZ by the bootwrapper, thus we gain nothing by compressing it a second time. Signed-off-by: David Bauer <mail@david-bauer.net>
* mpc85xx: reserve upper 1MB of RAM for WS-AP3825iDavid Bauer2023-04-081-1/+2
| | | | | | | | | | | | The bootpage for the second core is placed by U-Boot in the upper 128k of syste-memory. This could either be a reserved-area or deducted from the total system-memory. As only the latter is parsed by the bootwrapper, reduce the available system memory for linux in order to preserve the bootpage from being overwritten. Signed-off-by: David Bauer <mail@david-bauer.net>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-12 22:44:51 +0000