aboutsummaryrefslogtreecommitdiff
path: root/target/linux
Commit message (Collapse)AuthorAge
...
* sunxi: move KERNEL_LOADADDR into subtargetsZoltan HERPAI2024-04-19
| | | | | | | As preparation for the arm926ej-s support which has a different load address, move the KERNEL_LOADADDR into the subtargets. Signed-off-by: Zoltan HERPAI <wigyori@uid0.hu>
* sunxi: move fpu feature flag into the subtargetsZoltan HERPAI2024-04-19
| | | | | | | As the upcoming arm926ej-s does not have an FPU, move this flag into the subtargets. Signed-off-by: Zoltan HERPAI <wigyori@uid0.hu>
* sifiveu: 6.6: set testing kernelZoltan HERPAI2024-04-19
| | | | | | | | Allow selecting 6.6 as testing kernel on sunxi. Runtime-tested: SiFive Unleashed Signed-off-by: Zoltan HERPAI <wigyori@uid0.hu>
* sifiveu: 6.6: refresh patchesZoltan HERPAI2024-04-19
| | | | | | Refresh kernel patches. Signed-off-by: Zoltan HERPAI <wigyori@uid0.hu>
* kernel/sifiveu: Restore kernel files for v6.1Zoltan HERPAI2024-04-19
| | | | | | | | | | This is an automatically generated commit which aids following Kernel patch history, as git will see the move and copy as a rename thus defeating the purpose. See: https://lists.openwrt.org/pipermail/openwrt-devel/2023-October/041673.html for the original discussion. Signed-off-by: Zoltan HERPAI <wigyori@uid0.hu>
* kernel/sifiveu: Create kernel files for v6.6 (from v6.1)Zoltan HERPAI2024-04-19
| | | | | | | | This is an automatically generated commit. During a `git bisect` session, `git bisect --skip` is recommended. Signed-off-by: Zoltan HERPAI <wigyori@uid0.hu>
* mxs: add kernel 6.6 as testingZoltan HERPAI2024-04-19
| | | | | | Add new LTS kernel support. Signed-off-by: Zoltan HERPAI <wigyori@uid0.hu>
* mxs: adjust DTS path for 6.6Zoltan HERPAI2024-04-19
| | | | | | | For the ARM arch on 6.6, DTS files are moved into their vendor directories, mimicking arm64. Reflect this in the image Makefile. Signed-off-by: Zoltan HERPAI <wigyori@uid0.hu>
* mediatek: backport PWM driversDaniel Golle2024-04-19
| | | | | | | * MT7981 and MT7988 backported to Linux 6.1 * MT7988 backported to Linux 6.6 Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* qoriq: add kernel 6.1 supportStijn Tintel2024-04-18
| | | | | | | Add support for kernel 6.1 as testing kernel for qoriq. Refresh config using `make kernel_oldconfig`. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* kernel/qoriq: Restore kernel files for v5.15Stijn Tintel2024-04-18
| | | | | | | | | | This is an automatically generated commit which aids following Kernel patch history, as git will see the move and copy as a rename thus defeating the purpose. See: https://lists.openwrt.org/pipermail/openwrt-devel/2023-October/041673.html for the original discussion. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* kernel/qoriq: Create kernel files for v6.1 (from v5.15)Stijn Tintel2024-04-18
| | | | | | | | This is an automatically generated commit. When doing `git bisect`, consider `git bisect --skip`. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* qoriq: refresh kernel 5.15 configStijn Tintel2024-04-18
| | | | | | Done with `make kernel_oldconfig`. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* ipq807x: add support for Zbtlink ZBT-Z800AXChukun Pan2024-04-17
| | | | | | | | | | | | | | | | | | | Hardware specifications: SoC: Qualcomm IPQ8072A RAM: 1GB of DDR4 600MHz Flash1: Winbond W25Q64DW 8MB Flash2: MX30UF2G28AD 256MB WiFi1: QCN5024 2.4GHz AX 4x4 WiFi2: QCN5054 5GHz AX 4x4 Ethernet: 5x 1G RJ45 port USB: 2x USB 3.0 (1x M.2) Button: Reset, WPS Flash instructions: Upload factory.bin in stock firmware's upgrade page, do not preserve settings. Signed-off-by: Chukun Pan <amadeus@jmu.edu.cn>
* sunxi: fix network bringup on Olinuxino Micro boardsZoltan HERPAI2024-04-17
| | | | | | | It's the A13-based Olinuxino Micro which has only wireless interfaces. The A20-based board is a fully-fledged one which has an ethernet interface. Signed-off-by: Zoltan HERPAI <wigyori@uid0.hu>
* kernel: bump 5.15 to 5.15.155Hauke Mehrtens2024-04-16
| | | | | | | | Manual adapted the following patches: generic/hack-5.15/221-module_exports.patch octeontx/patches-5.15/0004-PCI-add-quirk-for-Gateworks-PLX-PEX860x-switch-with-.patch Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* ipq40xx: whw03v2: enable additional 5 GHz channelsRodrigo Balerdi2024-04-16
| | | | | | | | This device supports channel ranges 36-64 and 100-165, just like others based on the same reference design, but its current DTS is unnecessarily restricting these ranges to 36-48 and 149-165. Signed-off-by: Rodrigo Balerdi <lanchon@gmail.com>
* sunxi: update a13-olimex-som DTS pathZoltan HERPAI2024-04-16
| | | | | | | | In preparation for supporting kernel 6.6, where the DTS files are grouped into vendors - similarly to what arm64 has been doing all along -, update the SUNXI_DTS var of this board to prepend it with SUNXI_DTS_DIR. Signed-off-by: Zoltan HERPAI <wigyori@uid0.hu>
* pistachio: remove 5.15 supportZoltan HERPAI2024-04-16
| | | | | | Now that 6.1 is default, remove 5.15 support. Signed-off-by: Zoltan HERPAI <wigyori@uid0.hu>
* pistachio: default to kernel 6.1Zoltan HERPAI2024-04-16
| | | | | | | 6.1 has been present as testing for some time now, so switch the default to it. Signed-off-by: Zoltan HERPAI <wigyori@uid0.hu>
* kernel: Add missing config optionHauke Mehrtens2024-04-15
| | | | | | | | | | Kernel 6.1.83 allows to select CONFIG_GPIO_VF610, deactivate it by default. This fixes compilation of the armsr/armv8 target. Fixes: 2ad898e091cb ("kernel: bump 6.1 to 6.1.83") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* ramips: Add support for D-Link DIR-3040 A1Vince McKinsey2024-04-14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds support for the A1 hardware revision of the DIR-3040. It is an exact copy of the DIR-3060 save for some cosmetic changes to the housing. Even going so far as having the same FCC ID. Hardware specification: SoC: MediaTek MT7621AT Flash: Winbond W29N01HVSINA 128MB RAM: Micron MT41K128M16JT-125 256MB Ethernet: 5x 10/100/1000 Mbps WiFi1: MT7615DN 2.4GHz N 2x2:2 WiFi2: MT7615DN 5GHz AC 2x2:2 WiFi3: MT7615N 5GHz AC 4x4:4 Button: WPS, Reset Flash instructions: OpenWrt can be installed via D-Link Recovery GUI: NOTE: Seems to only work in Firefox on Windows. Tried with Chrome on Windows, Firefox in Linux, and Chromium in Linux. None of these other browsers worked. 1. Push and hold reset button (on the bottom of the device) until power led starts flashing (about 10 secs or so) while plugging in the power cable. 2. Give it ~30 seconds, to boot the recovery mode GUI 3. Connect your client computer to LAN1 of the device 4. Set your client IP address manually to 192.168.0.2 / 255.255.255.0. 5. Call the recovery page for the device at http://192.168.0.1/ 6. Use the provided emergency web GUI to upload and flash a new firmware to the device Thanks to @Lucky1openwrt and @iivailo for creating the DIR-3060 DTS file and related changes, so it was possible for me to adapt them to the DIR-3040, build images, test and fix minor issues. MAC Addresses: | use | address | example | | --- | --- | --- | | LAN | label | f4:*:61 | | WAN | label + 4 | f4:*:65 | | WI1/2g | label + 2 | f4:*:63 | | WI1/5g | label + 1 | f4:*:62 | | WI2/5g | label + 3 | f4:*:64 | The label MAC address was found in Factory, 0xe000 Checklist: ✓ nand ✓ ethernet ✓ button ✓ wifi2g ✓ wifi5g ✓ wifi5g ✓ mac ✓ led Signed-off-by: Vince McKinsey <vincemckinsey@gmail.com>
* mvebu: fix LEDs on IIJ SA-W2INAGAKI Hiroshi2024-04-14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | On IIJ SA-W2, some multiple LEDs have no "function" property and only "color" property is available for the newer binding of LED on Linux Kernel. 9d93b6d091 ("mvebu: drop redundant label with new LED color/function format") removes "label" property from LEDs, then, multiple "<color>:" (ex.: "green:"/"red:") will be appeared and renamed to "<color>:_<num>" (ex.: "green:_1", "green:_2", ...) by kernel. log: [ 1.911118] leds-gpio leds: Led green: renamed to green:_1 due to name collision [ 1.918600] leds-gpio leds: Led red: renamed to red:_1 due to name collision [ 1.925727] leds-gpio leds: Led green: renamed to green:_2 due to name collision [ 1.933202] leds-gpio leds: Led red: renamed to red:_2 due to name collision [ 1.940321] leds-gpio leds: Led green: renamed to green:_3 due to name collision [ 1.947797] leds-gpio leds: Led red: renamed to red:_3 due to name collision [ 1.954939] leds-gpio leds: Led green: renamed to green:_4 due to name collision [ 1.962456] leds-gpio leds: Led green: renamed to green:_5 due to name collision /sys/class/leds: root@OpenWrt:/# ls /sys/class/leds/ green: green:_3 green:status red:_2 green:_1 green:_4 red: red:_3 green:_2 green:_5 red:_1 red:status Fix this issue by adding missing "function" (and "function-enumerator") property to those LEDs on IIJ SA-W2. Fixes: 9d93b6d091 ("mvebu: drop redundant label with new LED color/function format") Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* mvebu: fix LEDs on Fortinet FortiGate devicesINAGAKI Hiroshi2024-04-14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | On Fortinet FortiGate 30E/50E, some multiple LEDs have no "function" property and only "color" property is available for the new binding of LED on Linux Kernel. 9d93b6d091 ("mvebu: drop redundant label with new LED color/function format") removes "label" property from LEDs, then, multiple "<color>:" (ex.: "green:"/"red:"/"amber:") will be appeared as LED names and renamed to "<color>:_<num>" (ex.: "green:_1", "green:_2", ...) by kernel. log: [ 12.425170] leds-gpio gpio-leds: Led green: renamed to green:_1 due to name collision [ 12.520390] leds-gpio gpio-leds: Led amber: renamed to amber:_1 due to name collision [ 12.614931] leds-gpio gpio-leds: Led green: renamed to green:_2 due to name collision [ 12.709895] leds-gpio gpio-leds: Led green: renamed to green:_3 due to name collision [ 12.804439] leds-gpio gpio-leds: Led amber: renamed to amber:_2 due to name collision [ 12.898969] leds-gpio gpio-leds: Led green: renamed to green:_4 due to name collision [ 12.993504] leds-gpio gpio-leds: Led amber: renamed to amber:_3 due to name collision [ 13.088033] leds-gpio gpio-leds: Led green: renamed to green:_5 due to name collision [ 13.182570] leds-gpio gpio-leds: Led green: renamed to green:_6 due to name collision [ 13.277103] leds-gpio gpio-leds: Led amber: renamed to amber:_4 due to name collision [ 13.371636] leds-gpio gpio-leds: Led green: renamed to green:_7 due to name collision /sys/class/leds: root@OpenWrt:/# ls /sys/class/leds/ amber: amber:_4 green:_2 green:_6 red:alarm amber:_1 amber:alarm green:_3 green:_7 red:status amber:_2 green: green:_4 green:status amber:_3 green:_1 green:_5 red: Fix this issue by adding missing "function" (and "function-enumerator") property those to LEDs on Fortinet FortiGate devices. Note: there is no appropriate function for "ha" LEDs in dt-bindings/leds/common.h, so use the hardcoded string for them instead. Fixes: 9d93b6d091 ("mvebu: drop redundant label with new LED color/function format") Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* kernel: add pending patches for new LED_FUNCTION_* definitionsINAGAKI Hiroshi2024-04-14
| | | | | | | Add pending patches to add LED_FUNCTION_MOBILE and LED_FUNCTION_SPEED_* definitions for Fortinet FortiGate devices and IIJ SA-W2. Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* ath79: add support for Comfast CF-EW71 v2Felix Golatofski2024-04-14
| | | | | | | | | | | | | | | | | | Specifications: Qualcomm/Atheros QCA9531 2x 10/100 Mbps Ethernet, with 48v PoE 2T2R 2.4 GHz, 802.11b/g/n 128MB RAM 16MB SPI Flash 4x LED (Always On Power, LAN, WAN, WLAN) Flashing instructions: The original firmware is based on OpenWrt, so flashing the sysupgrade image over the factory firmware is sufficient. The bootloader has a built-in recovery web-ui. This is the method I used to flash OpenWrt. You can get to the recovery web-ui by holding down the reset button for a few seconds (~5s) while pluggin in the router. The LEDs should start blinking fast and the router should be available on 192.168.1.1 for the recovery. Tested: Reset button, WAN LED, LAN LED, Power LED (always on, not much to test), WLAN LED, MAC addresses (same as factory firmware). Signed-off-by: Felix Golatofski <git@xdfr.de>
* kernel: bump 6.1 to 6.1.86Hauke Mehrtens2024-04-14
| | | | | | | | | | | Removed upstreamed: bcm27xx/patches-6.1/950-1235-drm-vc4-don-t-check-if-plane-state-fb-state-fb.patch [1] All other patches automatically rebased. 1. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.86&id=48bfb4b03c5ff6e1fa1dc73fb915e150b0968c40 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump 6.1 to 6.1.84Hauke Mehrtens2024-04-14
| | | | | | | | | | | Removed upstreamed: pistachio/patches-6.1/110-pwm-img-fix-clock-lookup.patch [1] All other patches automatically rebased. 1. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.84&id=44b6fb6cdedb2c391a2da355521d4610b2645fcc Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump 6.1 to 6.1.83Hauke Mehrtens2024-04-14
| | | | | | | | | | | | | | | | | | | | Removed upstreamed: generic/backport-6.1/789-STABLE-01-net-dsa-mt7530-prevent-possible-incorrect-XTAL-frequ.patch [1] generic/backport-6.1/789-STABLE-02-net-dsa-mt7530-fix-link-local-frames-that-ingress-vl.patch [2] generic/backport-6.1/789-STABLE-03-net-dsa-mt7530-fix-handling-of-all-link-local-frames.patch [3] generic/pending-6.1/735-net-mediatek-mtk_eth_soc-release-MAC_MCR_FORCE_LINK-.patch [4] generic/pending-6.1/736-net-ethernet-mtk_eth_soc-fix-PPE-hanging-issue.patch [5] Manual adjusted the following patches: mediatek/patches-6.1/100-dts-update-mt7622-rfb1.patch 1. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.83&id=be4512b9ac6fc53e1ca8daccbda84f643215c547 2. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.83&id=f1fa919ea59655f73cb3972264e157b8831ba546 3. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.83&id=86c0c154a759f2af9612a04bdf29110f02dce956 4. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.83&id=6b62bad2da1b338f452a9380639fc9b093d75a25 5. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.83&id=f78807362828ad01db2a9ed005bf79501b620f27 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: Reorder generic kernel 6.1 configHauke Mehrtens2024-04-14
| | | | | | | | This reordering was done using these commands: ./scripts/kconfig.pl '+' target/linux/generic/config-6.1 /dev/null > target/linux/generic/config-6.1-new mv target/linux/generic/config-6.1-new target/linux/generic/config-6.1 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump 6.6 to 6.6.27John Audia2024-04-14
| | | | | | | | | | | | | | | | | Changelog: https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.27 Removed upstreamed: pending-6.6/981-gcc-plugins-stackleak-Avoid-.head.txt.section.patch[1] All patches automatically rebased. 1. https://github.com/gregkh/linux/commit/9dff96b8b3a404d3b3581af46450f2efeb7d290a Build system: x86/64 Build-tested: flogic/xiaomi_redmi-router-ax6000-ubootmod, ramips/tplink_archer-a6-v3, x86/64/AMD Cezanne Run-tested: flogic/xiaomi_redmi-router-ax6000-ubootmod, ramips/tplink_archer-a6-v3, x86/64/AMD Cezanne Signed-off-by: John Audia <therealgraysky@proton.me>
* x86: generic: config-6.6: refreshJohn Audia2024-04-14
| | | | | | | | | | Ran `make kernel_menuconfig` Reference to CONFIG_SPECTRE_BHI_ON=y[1] 1. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/diff/arch/x86/Kconfig?id=v6.6.26&id2=v6.6.25 Signed-off-by: John Audia <therealgraysky@proton.me>
* kernel: bump 6.6 to 6.6.26John Audia2024-04-14
| | | | | | | | | | | | | | | | | | Changelog: https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.26 Manually rebased: generic/hack-6.6/210-darwin_scripts_include.patch Added pending: generic/pending-6.6/981-gcc-plugins-stackleak-Avoid-.head.txt.section.patch All other patches automatically rebased. Build system: x86/64 Build-tested: x86/64/AMD Cezanne, flogic/xiaomi_redmi-router-ax6000-ubootmod, ramips/tplink_archer-a6-v3, flogic/glinet_gl-mt6000 Run-tested: x86/64/AMD Cezanne, flogic/xiaomi_redmi-router-ax6000-ubootmod, ramips/tplink_archer-a6-v3, flogic/glinet_gl-mt6000 Signed-off-by: John Audia <therealgraysky@proton.me>
* ipq40xx: whw03v2: change LED color for 'running' state to blueRodrigo Balerdi2024-04-13
| | | | | | | | | | | | | | | | | | | | Change the RGB indicator LED color for the running state from green to blue. There are various reasons for this change: - In stock firmware, green means internet connection is up, red means it is down, and blue means indeterminate. To track stock behavior as closely as possible, OpenWrt should indicate blue by default. - In the current 23.x OpenWrt releases for this router, the led glows blue all the time -not green- because the bootloader sets it blue and there is an OpenWrt bug that makes it unable to control the LED. The bug is fixed in master, so without this commit there would be an unexpected change of behavior for this device in the next release. - The ports other closely related Linksys devices (such as EA8300 and MR8300) get this right and use blue for the running state. Signed-off-by: Rodrigo Balerdi <lanchon@gmail.com>
* ipq40xx: whw03v2: fix handling of RGB LEDRodrigo Balerdi2024-04-13
| | | | | | | The RGB LED should glow green in the 'running' state, but it was glowing cyan because the blue component defaulted to 'on'. Signed-off-by: Rodrigo Balerdi <lanchon@gmail.com>
* mediatek: fix DTS defining mt7530 switch phys but not referencing themDaniel Golle2024-04-13
| | | | | | | | | | | | | | | | | | | | | | | | The upstream solution to define the MDIO bus in DT is a bit more strict than our previous downstream solution doing the same thing and now requires switch PHYs to be referenced in DT as well. Arınç Ünal told us in #15141: "With [the now upstream patch written by him which we backported], the switch MDIO bus won't be assigned to ds->user_mii_bus when the switch MDIO bus is defined on the device tree anymore. This was not the case with the downstream patch. When ds->user_mii_bus is populated, DSA will 1:1 map the port with PHY. Meaning port with address 1 will be mapped to PHY with address 1. Because that ds->user_mii_bus is not populated when the switch MDIO bus is defined on the device tree, on every port node, the PHY address must be supplied by the phy-handle property." Add those phy-handles to affected devices' DT. Fixes: 4354b34f6f ("generic: 6.6: sync mt7530 DSA driver with upstream") Fixes: 401a6ccfaf ("generic: 6.1: sync mt7530 DSA driver with upstream") Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* ramips: add support for TP-Link EC220-G5 v2Mieczyslaw Nalewaj2024-04-13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | TP-Link EC220-G5 v2 is a dual band router with 4 GbE ports Advertised as AC1200 for its 867Mbps (2x2) 5GHz band and 300 Mbps (2x2) 2.4GHz band. Specs: - SoC: MediaTek MT7620A - Ethernet: 4x GbE ports (Realtek RTL8367S) - Wireless 2.4GHz: MediaTek MT7620A - Wireless 5GHz: MediaTek MT7612E - RAM: 64MiB - ROM: 8MiB (W25Q64BV) - 2 Buttons (WPS and reset) - 7 LEDs Flash instructions via serial console: 1. Rename the factory.bin to to test.bin 2. start a TFTP server from IP address 192.168.0.225 and serve the image named test.bin 3. connect your device to the LAN port 4. power up the router and press 4 on the console to stop the boot process. 5. enter the following commands on the router console tftp 0x80060000 test.bin erase tplink 0x20000 0x7a0000 cp.b 0x80060000 0x20000 0x7a0000 reset Flash instructions via TFTP: 1. Update orginal firmware of the router to the latest one. 2. Rename openwrt-ramips-mt7620-tplink_ec220-g5-v2-squashfs-tftp-recovery.bin to tp_recovery.bin 3. Change computer IP to 192.168.0.66 4. Run TFTP serwer 5. Start the router with the reset button pressed, the file will be automatically downloaded and after a while the router will restart. 6. After updating, set your computer's IP to DHCP Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com>
* ramips: mt7620a_tplink_archer.dtsi rename to mt7620a_tplink_8m.dtsiMieczyslaw Nalewaj2024-04-13
| | | | | | Change the name mt7620a_tplink_archer.dtsi to mt7620a_tplink_8m.dtsi because it will also be a base for TP-Link non-Archer routers. Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com>
* ramips: TP-Link Archer C2 v1: simplification of the dts definitionMieczyslaw Nalewaj2024-04-13
| | | | | | Import from the mt7620a_tplink_archer.dtsi file and thus simplify the rest of the definition. Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com>
* ramips: mt7620a_tplink_archer.dtsi - remove unnecessary nvmem-cells definitionsMieczyslaw Nalewaj2024-04-13
| | | | | | Remove unnecessary nvmem-cells definitions that are being redefined anyway. Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com>
* realtek: fix filter_port_list_reverse callsStijn Tintel2024-04-13
| | | | | | | | | | | | | | The function introduced in commit 7cbfe5654d6e is named filter_port_list_reverse, not filter_port_list_reversed. Fixes the following error on hpe,1920-8g-poe-65w and hpe,1920-8g-poe-180w. /bin/board_detect: /etc/board.d/02_network: line 84: filter_port_list_reversed: not found Fixes: 7cbfe5654d6e ("realtek: move port filtering out of uci_set_poe()") Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be> Acked-by: Sander Vanheule <sander@svanheule.net>
* mediatek: mt7622: rtl8367c: source code spell fixesPaul Donald2024-04-12
| | | | | | Improves indexing and searches Signed-off-by: Paul Donald <newtwen+github@gmail.com>
* mediatek: mt7622: rtl8367c: source comment fixesPaul Donald2024-04-12
| | | | | | | | Fix also some Chinese -> UTF8 encoding problems Improves indexing and searches Signed-off-by: Paul Donald <newtwen+github@gmail.com>
* mediatek: mt7622: rtl8367c: source comment fixesPaul Donald2024-04-12
| | | | | | | | | | | | | | | | | | | | | | | | Fix also some Chinese GB18030 -> UTF-8 encoding problems (translated the Chinese strings to English): 修改 -> modification port8~port10的设置在另外一个register -> port8~port10 setup is done in a separate register You are in the correct (UTF-8) encoding when you see: * $Date: 2017-03-08 15:13:58 +0800 (週三, 08 三月 2017) $ e.g. week 3, 08 third month, 2017 But not if you see: * $Date: 2017-03-08 15:13:58 +0800 (閫变笁, 08 涓夋湀 2017) $ rtl8367c/rtl8367c_asicdrv_lut.c should be read as UTF-8, despite having some earlier Chinese text lost to GB18030 encoding. Improves indexing and searches Signed-off-by: Paul Donald <newtwen+github@gmail.com>
* mediatek: mt7622: rtl8367c: source comment fixesPaul Donald2024-04-12
| | | | | | | | Fix also some Chinese -> UTF8 encoding problems Improves indexing and searches Signed-off-by: Paul Donald <newtwen+github@gmail.com>
* mediatek: mt7622: rtl8367c: source comment fixesPaul Donald2024-04-12
| | | | | | Improves indexing and searches Signed-off-by: Paul Donald <newtwen+github@gmail.com>
* qualcommax: enhance smp_affinity (log, uci, syntax)Sean Khan2024-04-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1.) Changed logic of `set_affinity` to now use physical cores rather than knowing the bitmask. Rather than having to know a bitmask, users can provide a numerical instance of one or more CPU cores (numbered 0-63). This is done via function `cpus_to_bitmask`. Functions Added: a.) bitmask_to_cpus - Takes a bitmask of CPUs and returns a list of CPU numbers. (i.e. `bitmask_to_cpus "f"` -> 0,1,2,3) b.) cpus_to_bitmask - Takes a comma/space or range list of CPUs and returns a bitmask. Example: `cpus_to_bitmask "2,3"` -> c `cpus_to_bitmask "0,1,2,3"` -> f `cpus_to_bitmask "1,3"` -> a With or without quotes `cpus_to_bitmask "1 3"` -> a `cpus_to_bitmask 1 3` -> a 2.) Added UCI options: enable - to enable/disable the script from running. [default 1 (on)] enable_log - to enable/disable logging output to `logger`.[default 1 (on)] Log output: ``` Mon Apr 8 23:00:01 2024 user.notice smp_affinity: Pinning IRQ(87) reo2host-destination-ring1 to CPU 0 Mon Apr 8 23:00:01 2024 user.notice smp_affinity: Pinning IRQ(88) reo2host-destination-ring2 to CPU 1 Mon Apr 8 23:00:01 2024 user.notice smp_affinity: Pinning IRQ(89) reo2host-destination-ring3 to CPU 2 Mon Apr 8 23:00:01 2024 user.notice smp_affinity: Pinning IRQ(90) reo2host-destination-ring4 to CPU 3 Mon Apr 8 23:00:01 2024 user.notice smp_affinity: Pinning IRQ(79) wbm2host-tx-completions-ring1 to CPU 1 Mon Apr 8 23:00:01 2024 user.notice smp_affinity: Pinning IRQ(83) wbm2host-tx-completions-ring2 to CPU 2 Mon Apr 8 23:00:01 2024 user.notice smp_affinity: Pinning IRQ(85) wbm2host-tx-completions-ring3 to CPU 3 Mon Apr 8 23:00:01 2024 user.notice smp_affinity: Pinning IRQ(73) ppdu-end-interrupts-mac1 to CPU 1 Mon Apr 8 23:00:01 2024 user.notice smp_affinity: Pinning IRQ(77) ppdu-end-interrupts-mac2 to CPU 2 Mon Apr 8 23:00:01 2024 user.notice smp_affinity: Pinning IRQ(75) ppdu-end-interrupts-mac3 to CPU 3 Mon Apr 8 23:00:01 2024 user.notice smp_affinity: Pinning IRQ(32) edma_txcmpl to CPU 3 Mon Apr 8 23:00:01 2024 user.notice smp_affinity: Pinning IRQ(33) edma_rxfill to CPU 3 Mon Apr 8 23:00:01 2024 user.notice smp_affinity: Pinning IRQ(35) edma_rxdesc to CPU 3 Mon Apr 8 23:00:01 2024 user.notice smp_affinity: Pinning IRQ(36) edma_misc to CPU 3 ``` Output of `/proc/interrupts`: ``` 69: 0 0 0 0 GIC-0 209 Edge rxdma2host-destination-ring-mac1 70: 0 0 0 0 GIC-0 211 Edge rxdma2host-destination-ring-mac3 71: 0 0 0 0 GIC-0 210 Edge rxdma2host-destination-ring-mac2 72: 2435 0 0 0 GIC-0 321 Edge reo2host-status 73: 268427 8011 0 0 GIC-0 261 Edge ppdu-end-interrupts-mac1 74: 2 0 0 0 GIC-0 255 Edge rxdma2host-monitor-status-ring-mac1 75: 176169 0 4 10035 GIC-0 263 Edge ppdu-end-interrupts-mac3 76: 2 0 0 0 GIC-0 260 Edge rxdma2host-monitor-status-ring-mac3 77: 0 0 0 0 GIC-0 262 Edge ppdu-end-interrupts-mac2 78: 0 0 0 0 GIC-0 256 Edge rxdma2host-monitor-status-ring-mac2 79: 3428 3123 0 0 GIC-0 189 Edge wbm2host-tx-completions-ring1 80: 0 0 0 0 GIC-0 323 Edge reo2ost-exception 81: 178 0 0 0 GIC-0 322 Edge wbm2host-rx-release 82: 0 0 0 0 GIC-0 212 Edge host2rxdma-host-buf-ring-mac1 83: 6524 0 13712 0 GIC-0 190 Edge wbm2host-tx-completions-ring2 84: 4 0 0 0 GIC-0 235 Edge host2rxdma-host-buf-ring-mac3 85: 560 0 0 1979 GIC-0 191 Edge wbm2host-tx-completions-ring3 86: 0 0 0 0 GIC-0 215 Edge host2rxdma-host-buf-ring-mac2 87: 4520 0 0 0 GIC-0 267 Edge reo2host-destination-ring1 88: 2231 2811 0 0 GIC-0 268 Edge reo2host-destination-ring2 89: 2180 0 2512 0 GIC-0 271 Edge reo2host-destination-ring3 90: 1990 0 0 2321 GIC-0 320 Edge reo2host-destination-ring4 ``` 3.) Added `uci-defaults` script `15_smp_affinity` to configure defaults options on first boot. Signed-off-by: Sean Khan <datapronix@protonmail.com>
* qualcommax: drop 6.1 supportRobert Marko2024-04-11
| | | | | | | We have defaulted to 6.6 for a while so its time to completely drop 6.1 so new devices dont have to include patches for 6.1. Signed-off-by: Robert Marko <robimarko@gmail.com>
* mediatek: filogic: add support for Edgecore EAP111Robert Marko2024-04-11
| | | | | | | | | | | | | | | | | | | HW specifications: * Mediatek MT7981A * 256MB SPI-NAND * 512MB DRAM * Uplink: 1 x 10/100/1000Base-T Ethernet, Auto MDIX, RJ-45 with 802.3at PoE (Built-in GBe PHY) * LAN: 1 x 10/100/1000Base-T Ethernet, Auto MDIX, RJ-45 (Airoha EN8801SC) * 1 Tricolor LED * Reset button * 12V/2.0A DC input Installation: Board comes with OpenWifi/TIP which is OpenWrt based, so sysupgrade can be used directly over SSH. Signed-off-by: Robert Marko <robert.marko@sartura.hr>
* mediatek: add Airoha EN8801SC PHY driverRobert Marko2024-04-11
| | | | | | | | | | | Airoha EN8801SC PHY is a gigabit PHY used on Edgecore EAP111 so, include the MTK driver with some cleanups. Unfortunatelly, there is no specification sheet nor datasheet available in order to demistify the magic PBUS writes and work on upstreaming this driver. Signed-off-by: Robert Marko <robert.marko@sartura.hr>
Powered by cgit, Themed by Ted Yin.