summaryrefslogtreecommitdiffstats
path: root/target/linux/mvebu
Commit message (Collapse)AuthorAgeFilesLines
* mvebu: fix LEDs on IIJ SA-W2INAGAKI Hiroshi2024-04-142-0/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-146-0/+56
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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: bump 6.1 to 6.1.83Hauke Mehrtens2024-04-141-2/+2
| | | | | | | | | | | | | | | | | | | | 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>
* mvebu: puzzle-m90x: wipe rootfs_data on sysupgradeDaniel Golle2024-04-091-0/+2
| | | | | | | | | | | | | | | | | | | The sysupgrade formware of the Puzzle series is a slightly strange dual-boot approach while remaining compatible with Marvell's SDK firmware upgrade binary format -- which happens to be a full-disk image with GPT partition table. Hence that /lib/upgrade/emmc-puzzle.sh script is like an exotic disease which results from those decisions, and as we also want to somehow stay compatible with the IEI-World stock firmware we got to use it in that same way (we are not compatible with the QNAP-branded identical hardware device anyway). Currently, on sysupgrade the result is that one ends up with the old content of rootfs_data (a GPT partition on those devices) as nothing ever wipes or in any way re-creates the filesystem there. As a simple work-around, let's kill the filesystem on rootfs_data so fstools re-formats it on the next boot. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* mvebu: 6.6: refresh patchesRobert Marko2024-04-031-2/+2
| | | | | | | Well, it seems that we have a patch that was not refreshed and CI is complaining, so refresh it. Signed-off-by: Robert Marko <robimarko@gmail.com>
* mvebu: add 6.6 testing kernelStijn Segers2024-04-031-0/+1
| | | | | | Add 6.6 testing kernel for mvebu target. Signed-off-by: Stijn Segers <foss@volatilesystems.org>
* mvebu: cortexa9: set DTS dir for 6.6Stijn Segers2024-04-031-0/+4
| | | | | | | | | | With 6.6, all DTSes were moved to their vendor subdirectories. ARM64 DTSes already used this scheme, but 32 bit Cortex A9 did not, prior to 6.6. Introduce a kernel version check to keep backward compatibility with 6.1. Suggested-by: Robert Marko <robimarko@gmail.com> Signed-off-by: Stijn Segers <foss@volatilesystems.org>
* mvebu: 6.6: refresh patchesStijn Segers2024-04-0314-53/+53
| | | | | | | | | | | | | Manually refreshed: * 309-linksys-status-led.patch * 310-linksys-use-eth0-as-cpu-port.patch * 320-arm-dts-armada-370-synology-ds213j-mtd-parts.patch * 701-mvpp2-read-mac-address-from-nvmem.patch * 902-drivers-mfd-Add-a-driver-for-IEI-WT61P803-PUZZLE-MCU.patch All other patches automatically refreshed. Signed-off-by: Stijn Segers <foss@volatilesystems.org>
* mvebu: 6.6: remove upstreamed patchesStijn Segers2024-04-031-59/+0
| | | | | | 000-cpufreq-armada-8k-add-ap807-support.patch was upstreamed. Signed-off-by: Stijn Segers <foss@volatilesystems.org>
* mvebu: 6.6: adjust 32 bit ARM DTS pathStijn Segers2024-04-0323-53/+53
| | | | | | | | As of 6.6, all upstream DTSes are moved to their respective vendor subdir. OpenWrt already followed this practice for ARM64, but not yet for 32 bit ARM (Armada 37x/38x). Signed-off-by: Stijn Segers <foss@volatilesystems.org>
* mvebu: 6.6: copy files, patches & configs from 6.1Stijn Segers2024-04-0357-0/+10704
| | | | | | Copy all mvebu 6.1 specific files, patches and configs to 6.1. Signed-off-by: Stijn Segers <foss@volatilesystems.org>
* mvebu: move files to files-6.1Stijn Segers2024-04-0319-0/+0
| | | | | | | DTS paths for 32 bit ARM devices changed with 6.6, move files/ to files-6.1 to prep for kernel 6.6 introduction. Signed-off-by: Stijn Segers <foss@volatilesystems.org>
* treewide: disable spectre mitigation on unaffected Arm64 targetsQingfang Deng2024-03-231-0/+1
| | | | | | | Cortex-A53 is not vulnerable to any Spectre variants. Ref: https://developer.arm.com/Arm%20Security%20Center/Speculative%20Processor%20Vulnerability Signed-off-by: Qingfang Deng <dqfext@gmail.com>
* mvebu: puzzle-m90x: optimize thermal zoneDaniel Golle2024-03-213-12/+36
| | | | | | | | | | | | | | | * have more defined PWM steps similar to the vendor's shell script doing the same thing * replace PWM values with experiencal values provided by forum users * increase hyteresis to prevent changing fan speed every second (just because it's annoying to listen to) * add 'hot' trip point at 75 deg. to warn users that shutdown is imminent Tested on Puzzle M902 only for now, PWM values for Puzzle M901 might be slightly different but should quite certainly also be rised. Suggested-by: Martin Gierschner <martin_gierschner@gmx.de> Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* mvebu: enable thermal zone polling for IEI Puzzle devicesDaniel Golle2024-03-171-3/+6
| | | | | | | | | | Marvell's thermal sensors do not support interrupts, so we need to poll them. Reading temperature every second should be enough to control the fan. While at it, also make sure fan speed is reduced again if temperature goes down. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* mvebu: add support for SolidRun ClearFog ProTobias Schramm2024-03-028-10/+583
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The SolidRun ClearFog Pro is a router based on the SolidRun CN9130 SOM. Specs: - SoC: Quad-Core Cortex-A72 CN9130 SoC - RAM: 4GiB DDR4 - Serial: Micro-USB port on front (FT232R, 115200 8n1) - Storage: 8GiB eMMC, microSD card slot, 8MiB SPI NOR flash - Ethernet: 7x GbE (1 port dedicated on SoC, 6 port switch with single GbE CPU port) - SFP: 1x SFP+ - USB: 1x USB-A 3.1 Gen 1 - PCIe: 2x mini PCIe (one slot with USB and SIM card socket) - SATA: 1x M.2 Key-B In addition to the usual connectivity options this device also features an internal mikroBUS expansion connector. SATA is currently untested due to lack of a suitable M.2 SSD. Installation ============ 1. Write sdcard sysupgrade image to microSD card using dd or similar 2. Insert microSD card into router and apply power 3. Device boots into OpenWRT 4. (optional) dd sysupgrade image to /dev/mmcblk0 to install to eMMC Signed-off-by: Tobias Schramm <tobias@t-sys.eu>
* kernel: 6.1: backport Marvell Armada 8k AP807 cpufreq supportTobias Schramm2024-03-021-0/+64
| | | | | | | | Upstream a patch adding support for cpufreq on AP807-based SoC like the CN913x was submitted. Include it in patches to ensure best performance under load and lowest power consumption in idle. Signed-off-by: Tobias Schramm <tobias@t-sys.eu>
* mvebu: add kernel module for Turris Omnia Wi-Fi 6Jan Jasper de Kroon2024-02-261-1/+1
| | | | | | | | | | | | The following kernel module package was added to the build recipe for the Turris Omnia: kmod-mt7915-firmware This module enables support for the official Wi-Fi 6 upgrade kit sold by CZ.NIC, which includes the AW7915-NP1 miniPCIE board based on Mediatek MT7915AN, providing 5 GHz Wi-Fi 6 connectivity. With this commit we now support the latest Turris Omnia Wi-Fi 6 Edition Signed-off-by: Jan Jasper de Kroon <jajadekroon@gmail.com>
* mvebu: fill additional info for mvneta tx queue workaround patchTomasz Maciej Nowak2024-02-261-0/+5
| | | | | | | | Because some still unresolved bugs in this driver, which sprout occasional questions what this patch works around, point to the issue which started this. Being here, fill headers required by git am. Signed-off-by: Tomasz Maciej Nowak <tmn505@gmail.com>
* kernel: bump 6.1 to 6.1.78John Audia2024-02-181-2/+2
| | | | | | | | | | | | | | | | Changelog: https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.78 Manually rebased: bcm27xx/patches-6.1/950-0865-usb-dwc3-Set-DMA-and-coherent-masks-early.patch bcm27xx/patches-6.1/950-0124-Add-support-for-all-the-downstream-rpi-sound-card-dr.patch All other patches automatically rebased. Build system: x86/64 Build-tested: x86/64/AMD Cezanne, ramips/tplink_archer-a6-v3, logic/xiaomi_redmi-router-ax6000-ubootmod Run-tested: x86/64/AMD Cezanne, ramips/tplink_archer-a6-v3, logic/xiaomi_redmi-router-ax6000-ubootmod Signed-off-by: John Audia <therealgraysky@proton.me>
* mvebu: drop kernel 5.15 config and patchesStefan Kalscheuer2024-02-1843-5548/+0
| | | | | | With default now being at 6.1 we can remove all 5.15 components. Signed-off-by: Stefan Kalscheuer <stefan@stklcode.de>
* mvebu: switch to kernel 6.1Stefan Kalscheuer2024-02-181-2/+1
| | | | | | After a few months of testing it's time to move to 6.1 by default. Signed-off-by: Stefan Kalscheuer <stefan@stklcode.de>
* kernel: backport phylink changes from mainline LinuxDaniel Golle2024-02-151-2/+2
| | | | | | | Let's pick a bunch of useful phylink changes which allow us to keep drivers in sync with mainline Linux. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* kernel: bump 6.1 to 6.1.77John Audia2024-02-081-1/+1
| | | | | | | | | | | | | | | | | | | Changelog: https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.77 Removed upstreamed: generic/backport-6.1/707-v6.8-01-net-phy-at803x-fix-passing-the-wrong-reference-for-c.patch[1] generic/backport-6.1/796-v6.8-ipmr-fix-kernel-panic-when-forwarding-mcast-packets.patch[2] All other patches automatically rebased. 1. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.77&id=7dc0fefd37dd5fb03fdac6e3e01b1c2291148ccb 2. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.77&id=d2f1b7fe74afd66298dbb3c7b39e7b62e4df1724 Build system: x86/64 Build-tested: x86/64/AMD Cezanne Run-tested: x86/64/AMD Cezanne Signed-off-by: John Audia <therealgraysky@proton.me>
* mvebu: convert to new LED color/function format where possibleChristian Marangi2024-02-074-5/+14
| | | | | | | | Initial conversion to new LED color/function format and drop label format where possible. The same label is composed at runtime. Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* mvebu: drop redundant label with new LED color/function formatChristian Marangi2024-02-076-38/+0
| | | | | | | | | Drop redundant label with new LED color/function format declared. This was needed previously when the new format wasn't supported by leds.sh functions script. Now that is supported this property can be removed in favor of the new format. Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* kernel: bump 5.15 to 5.15.148John Audia2024-02-011-1/+1
| | | | | | | | | | | | | | | | | | | | | Changelog: https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.15.148 Removed upstreamed: generic/hack-5.15/321-powerpc_crtsavres_prereq.patch[1] Manually rebased: target/linux/octeontx/patches-5.15/0004-PCI-add-quirk-for-Gateworks-PLX-PEX860x-switch-with-.patch[2] All other patches automatically rebased. 1. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.15.148&id=0b11a145eb00d51f7ef18cfcae587b93f9adb1e9 2. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit?h=v5.15.148&id=b67064bd372300a75293efbbc70624996dccffd4 Build system: x86_64 Build-tested: ramips/tplink_archer-a6-v3 Run-tested: ramips/tplink_archer-a6-v3 Signed-off-by: John Audia <therealgraysky@proton.me>
* kernel: bump 6.1 to 6.1.75John Audia2024-02-011-1/+1
| | | | | | | | | | | | | | | | | | | | | | | Changelog: https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.75 Removed upstreamed: generic/hack-6.1/321-powerpc_crtsavres_prereq.patch[1] generic/pending-6.1/540-ksmbd-only-v2-leases-handle-the-directory.patch[2] Rebased: bcm27xx/patches-6.1/950-0670-fbdev-Don-t-cancel-deferred-work-if-pagelist-empty.patch[3] All other patches automatically rebased. 1. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.75&id=16b88e68b85d5520c28498bb847358ff6300cb90 2. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/fs/smb?h=v6.1.75&id=c866866c795296d3637ab0d48a3d8a3ef5d6f4a3 3. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.75&id=81f444f22816a82ada2cc787a2845cffc8c584a6 Build system: x86/64 Build-tested: x86/64/AMD Cezanne Run-tested: x86/64/AMD Cezanne Signed-off-by: John Audia <therealgraysky@proton.me>
* mvebu: fix RTC of IEI-World Puzzle M90x devicesDaniel Golle2023-12-183-2/+24
| | | | | | | | | The Puzzle devices come with an I2C-connected Epson RX8130 RTC. Disable the (dysfunctional) RTC units of the SoC and add driver kmod-rtc-ds1307 to support the Epson RX8130 instead. Tested-by: Thomas Huehn <thomas.huehn@hs-nordhausen.de> Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* kernel: bump 5.15 to 5.15.141John Audia2023-12-041-1/+1
| | | | | | | | | | | | Changelog: https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.15.141 All patches automatically rebased. Build system: x86_64 Build-tested: ramips/tplink_archer-a6-v3 Run-tested: ramips/tplink_archer-a6-v3 Signed-off-by: John Audia <therealgraysky@proton.me>
* kernel: bump 5.15 to 5.15.140John Audia2023-11-291-139/+0
| | | | | | | | | | | | | | | | | Changelog: https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.15.140 Removed upstreamed: mvebu/patches-5.15/106-Revert-i2c-pxa-move-to-generic-GPIO-recovery.patch[1] All other patches automatically rebased. 1. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.15.140&id=06d320ca170b4e59bb261e2ce3ffe84e9154d42b Build system: x86_64 Build-tested: ramips/tplink_archer-a6-v3 Run-tested: ramips/tplink_archer-a6-v3 Signed-off-by: John Audia <therealgraysky@proton.me>
* kernel: bump 6.1 to 6.1.64John Audia2023-11-293-142/+3
| | | | | | | | | | | | | | | | | | | | | | | | Changelog: https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.64 Removed upstreamed: ixp4xx/patches-6.1/0001-mtd-cfi_cmdset_0001-Byte-swap-OTP-info.patch[1] mvebu/patches-6.1/106-Revert-i2c-pxa-move-to-generic-GPIO-recovery.patch[2] qualcommax/patches-6.1/0026-v6.7-clk-qcom-ipq8074-drop-the-CLK_SET_RATE_PARENT-flag-f.patch[3] Manually rebased: bcm27xx/patches-6.1/950-0111-MMC-added-alternative-MMC-driver.patch All other patches automatically rebased. 1. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.64&id=3b93096d29c5b9ca2af94be4ee9949c1767acf17 2. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.64&id=b3fd9db79e30d5eb5f76ef1f5b7e4f444af574ea 3. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.64&id=877080a3490102da26b8d969588159b2385f739e Build system: x86/64 Build-tested: x86/64/AMD Cezanne Run-tested: x86/64/AMD Cezanne Signed-off-by: John Audia <therealgraysky@proton.me>
* mvebu: remove mac-address-incrementRosen Penev2023-11-226-51/+44
| | | | | | It's deprecated. Signed-off-by: Rosen Penev <rosenp@gmail.com>
* mvebu: add support for Synology DS213jDaniel Golle2023-11-206-1/+295
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The Synology DS213j is a rather dated dual-bay SATA NAS based on on the Marvell Armada-370 SoC. It has long been supported in vanilla Linux, however, flash partitioning there didn't match with reality (ie. the bootloaders expectations) and nobody cared to wrap up OpenWrt support for the device. CPU: Marvell Armada-370 ARMv7 SoC @ 1200 MHz RAM: 512 MB DDR3 Flash: 8 MB (Micron Technology N25Q064) Network: 1x 1000M/100M/10M Ethernet (Marvell 88E1510) SATA: 2x 3.0Gbps USB: 2x USB 2.0 As OS options are becoming limited on that still quite useful hardware, patch the flash partitions to be able to get the most out of it when using OpenWrt. The vendor firmware loads kernel and initrd from fixed addresses in the flash, not making use of a modifyable environment stored in flash which is stored at a location right in the middle of the vendor's zImage partition (at 0x100000). Stock firmware flash layout: 0x000000 ~ 0x0c0000 : "RedBoot" (actually U-Boot) 0x0c0000 ~ 0x390000 : "zImage" 0x390000 ~ 0x7d0000 : "rd.gz" 0x7d0000 ~ 0x7e0000 : "vendor" (contains MAC address, serial no) 0x7e0000 ~ 0x7f0000 : "RedBoot Config" (unused? legacy left-over) 0x7f0000 ~ 0x800000 : "FIS directory" (unused? legacy left-over) OpenWrt flash layout: 0x000000 ~ 0x0c0000 : "u-boot" 0x0c0000 ~ 0x100000 : "gap" 0x100000 ~ 0x110000 : "u-boot-env" 0x110000 ~ 0x7d0000 : "kernel" 0x7d0000 ~ 0x7e0000 : "vendor" (contains MAC address, serial no) 0x7e0000 ~ 0x800000 : "gap2" "kernel", "gap" and "gap2" are concatenated using the mtd-concat virtual MTD driver, resulting in a partition "firmware" used by OpenWrt for kernel, rootfs and rootfs-overlay, 0x720000 (7296kiB) in total. Installation: 1. Connect to internal serial console port and Ethernet port, providing a TFTP server at a static IPv4 address, e.g. 192.168.1.254/24. 2. Interrupt bootloader using CTRL+C 3. Configure bootloader to load OpenWrt on future boot: setenv bootcmd "bootm f4110000" saveenv 4. Load and boot initramfs image via TFTP: setenv ipaddr 192.168.1.1 setenv serverip 192.168.1.254 tftpboot openwrt-mvebu-cortexa9-synology_ds213j-initramfs-kernel.bin bootm 5. Use sysupgrade to load final image. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* mvebu: fix PXA I2C bus with recoveryRobert Marko2023-11-122-0/+278
| | | | | | | | | | | | | | | | | | Since kernel 5.11, the PXA I2C driver has been converted to generic I2C recovery, which makes the I2C bus completely lock up if recovery pinctrl is present in the DT and I2C recovery is enabled. This effectively completely broke I2C on Methode uDPU and eDPU boards as both of them rely on I2C recovery. After a discussion upstream, it was concluded that there is no simple fix and that the blamed upstream commit: 0b01392c18b9993a584f36ace1d61118772ad0ca ("i2c: pxa: move to generic GPIO recovery") should be reverted. I have sent the revert upstream, it should be merged soon so lets "fix" OpenWrt as well. Signed-off-by: Robert Marko <robert.marko@sartura.hr>
* mvebu: add support for IIJ SA-W2INAGAKI Hiroshi2023-10-314-0/+438
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Internet Initiative Japan Inc. (IIJ) SA-W2 is a network appliance with 11ac (Wi-Fi 5) wlan, based on 88F6810. Specification: - SoC : Marvell Armada 380 88F6810 - RAM : DDR3 256 MiB (Micron MT41K64M16TW-107:J x2) - Flash : SPI-NOR 32 MiB (Winbond W25Q256JVFIQ) - WLAN : 2.4/5 GHz, Mini PCI-E - 2.4 GHz : Silex SX-PCEGN (Atheros AR9287 (2T2R)) - 5 GHz : Silex SX-PCEAC (Qualcomm Atheros QCA9880 (3T3R)) - Ethernet : 10/100/1000 Mbps x5 - Switch : Marvell 88E6172 - LEDs/Keys : 12x/1x - UART : "CONSOLE" port (RJ-45, RS-232C) - settings : 115200n8 - assignment: 1:NC, 2:NC, 3:TXD, 4:GND, 5:GND, 6:RXD, 7:NC, 8:NC - note : compatible with Cisco console cable - Power : DC Input or PoE - DC Input : 12 VDC, 3 A - PoE : 802.3af - module : Silvertel Ag9712-2BR - note : USB ports shouldn't be used when powered by PoE - Bootloader : PMON2000 based - Stock : NetBSD based Flash instruction using sysupgrade image: 1. Prepare TFTP server with IP address 192.168.0.10 and put sysupgrade image to TFTP directory 2. Connect PC to "GE0/PoE" port on SA-W2 3. Power on SA-W2, interrupt count-down by Esc and enter to bootloader CLI 4. Set IP address of the device address 192.168.0.1 5. Download sysupgrade image and flash to storage tftpload 192.168.0.10 <image name> firmwrite example: #tftpload 192.168.0.10 openwrt-mvebu-cortexa9-iij_sa-w2-squashfs-sysupgrade.bin Loading openwrt-mvebu-cortexa9-iij_sa-w2-squashfs-sysupgrade.bin loaded 8127268 byte(s) #firmwrite Erasing FLASH block 32 Done 0x00200000. Erasing FLASH block 33 Done 0x00210000. ... Erasing FLASH block 155 Done 0x009b0000. Erasing FLASH block 156 Done 0x009c0000. Programming FLASH. Done. Verifying FLASH. No Errors found. 6. Check the flashed firmware firmcheck example: #firmcheck [Normal firmware] ident: 'SEIL2015' copyright: 'ARM OpenWrt Linux-5.15.93' version format: 1 version major: 9 version minor: 99 version release: 'r22060+36-5163bb5e54' body size: 3578524 checksum: 0x8a083cb8 [Rescue firmware] ident: 'SEIL2015' copyright: 'Copyright (c) 2017 Internet Initiative Japan Inc. All rights reserved.' version format: 1 version major: 3 version minor: 70 version release: 'Release' body size: 10152458 checksum: 0x8f9518c2 7. Boot with the flashed firmware boot Note: - The bootloader on this device is not U-Boot and it's environment space ("bootloader-env") has no compatibility with U-Boot tools. - eth1 is connected to port6 of 88E6172 switch, but multi-cpu port can't be handled on Linux Kernel and not defined. - Powering by PoE hasn't been tested yet. - This device has 2x OS images on flash and they can be switched by setting "BOOTDEV" variable on bootloader CLI. That variable supports the following values: - "flash" : primary image on flash ("firmware") - "rescue": secondary image on flash ("rescue") - "usb" : usb storage (broken?) - "lan0/1": network command to set: set BOOTDEV=<dev> example: set BOOTDEV=rescue This commit also supports booting from secondary partition. - To execute initramfs image on bootloader CLI, use "go" command. ("go" command is not listed on the output of "help", but available) example (download and execute): address 192.168.0.1 tftpload 192.168.0.10 openwrt-mvebu-cortexa9-iij_sa-w2-initramfs-kernel.bin go MAC addresses: LAN : 00:E0:4D:xx:xx:19 (none) WAN : 00:E0:4D:xx:xx:18 (board_info, 0x6 (hex)) 2.4 GHz: 84:25:3F:xx:xx:xx (Mini PCI-E card) 5 GHz : 84:25:3F:xx:xx:xx (Mini PCI-E card) Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* mvebu: cortexa9: enable seil-fw mtdsplit driverINAGAKI Hiroshi2023-10-312-0/+2
| | | | | | Enable seil-fw driver on mvebu/cortexa9 to use it on IIJ SA-W2. Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* mvebu: add support for Fortinet FortiGate 30EINAGAKI Hiroshi2023-10-296-358/+488
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fortinet FortiGate 30E (FG-30E) is a UTM, based on Armada 385 (88F6820). Specification: - SoC : Marvell Armada 385 88F6820 - RAM : DDR3 1 GiB (4x Micron MT41K256M8DA-125, "D9PSH") - Flash : SPI-NOR 128 MiB (Macronix MX66L1G45GMI-10G) - Ethernet : 5x 10/100/1000 Mbps - Switch : Marvell 88E6176 - LEDs/Keys : 16x/1x - UART : "CONSOLE" port (RJ-45, RS-232C level) - port : ttyS0 - settings : 9600bps 8n1 - assignment : 1:NC , 2:NC , 3:TXD, 4:GND, 5:GND, 6:RXD, 7:NC , 8:NC - note : compatible with Cisco console cable - HW Monitoring: nuvoTon NCT7802Y - Power : 12 VDC, 2 A - plug : Modex 5557-02R Flash instruction using initramfs image: 1. Power on FG-30E and interrupt to show bootmenu 2. Call "[I]: System information." -> "[S]: Set serial port baudrate." and set baudrate to 9600 bps 3. Call "[R]: Review TFTP parameters.", check TFTP parameters and connect computer to "Image download port" in the parameters 4. Prepare TFTP server with the parameters obtained above 5. Rename OpenWrt initramfs image to "image.out" and put to TFTP directory 6. Call "[T]: Initiate TFTP firmware transfer." to download initramfs image from TFTP server 7. Type "r" key when the following message is showed, to boot initramfs image without flashing to spi-nor flash "Save as Default firmware/Backup firmware/Run image without saving:[D/B/R]?" 8. On initramfs image, backup mtd if needed minimum: - "firmware-info" - "kernel" - "rootfs" 9. On initramfs image, upload sysupgrade image to the device and perform sysupgrade 10. Wait ~200 seconds to complete flashing and rebooting. If the device is booted with stock firmware, login to bootmenu and call "[B]: Boot with backup firmware and set as default." to set the first OS image as default and boot it. Notes: - Both colors of Bi-color LEDs on the front panel cannot be turned on at the same time. - "PWR" and "Logo" LEDs are connected to power source directly. - The following partitions are added for OpenWrt. These partitions are contained in "uboot" partition (0x0-0x1fffff) on stock firmware. - "firmware-info" - "dtb" - "u-boot-env" - "board-info" Image header for bootmenu tftp: 0x0 - 0xf : ? 0x10 - 0x2f : Image Name 0x30 - 0x17f: ? 0x180 - 0x183: Kernel Offset* 0x184 - 0x187: Kernel Length* 0x188 - 0x18b: RootFS Offset (ext2)* 0x18c - 0x18f: RootFS Length (ext2)* 0x190 - 0x193: DTB Offset 0x194 - 0x197: DTB Length 0x198 - 0x19b: Data Offset (jffs2) 0x19c - 0x19f: Data Length (jffs2) 0x1a0 - 0x1ff: ? *: required for initramfs image MAC addresses: (eth0): 70:4C:A5:xx:xx:CE (board-info, 0xd880 (hex)) WAN : 70:4C:A5:xx:xx:CF LAN 1 : 70:4C:A5:xx:xx:D0 LAN 2 : 70:4C:A5:xx:xx:D1 LAN 3 : 70:4C:A5:xx:xx:D2 LAN 4 : 70:4C:A5:xx:xx:D3 Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* kernel: 5.15: Backport Turris Omnia LED patchesMarek Behún2023-10-233-182/+0
| | | | | | | | | | | | | | | | | | | | | This backports patches leds: turris-omnia: convert to use dev_groups leds: turris-omnia: Use sysfs_emit() instead of sprintf() leds: turris-omnia: Drop unnecessary mutex locking leds: turris-omnia: Do not use SMBUS calls leds: turris-omnia: Make set_brightness() more efficient leds: turris-omnia: Support HW controlled mode via private trigger leds: turris-omnia: Add support for enabling/disabling HW gamma correction leds: turris-omnia: Fix brightness setting and trigger activating into backport-5.15. The above patches replace: leds: turris-omnia: support HW controlled mode via private trigger leds: turris-omnia: initialize multi-intensity to full leds: turris-omnia: change max brightness from 255 to 1 from mvebu/patches-5.15. Signed-off-by: Marek Behún <kabel@kernel.org>
* kernel: 6.1: Backport Turris Omnia LED patchesMarek Mojík2023-10-203-182/+0
| | | | | | | | | | | | | | | | | | | | This backports patches leds: turris-omnia: Use sysfs_emit() instead of sprintf() leds: turris-omnia: Drop unnecessary mutex locking leds: turris-omnia: Do not use SMBUS calls leds: turris-omnia: Make set_brightness() more efficient leds: turris-omnia: Support HW controlled mode via private trigger leds: turris-omnia: Add support for enabling/disabling HW gamma correction leds: turris-omnia: Fix brightness setting and trigger activating into backport-6.1. The above patches replace: leds: turris-omnia: support HW controlled mode via private trigger leds: turris-omnia: initialize multi-intensity to full leds: turris-omnia: change max brightness from 255 to 1 from mvebu/patches-6.1. Signed-off-by: Marek Mojík <marek.mojik@nic.cz>
* mvebu: eDPU: add support for version with external switchRobert Marko2023-09-192-1/+55
| | | | | | | | | | | New revision of eDPU uses an Marvell MV88E6361 switch to connect the SFP cage and G.hn IC instead of connecting them directly to the ethernet controllers. The same image can be used on both versions as U-Boot will enable the switch node and disable the unused ethernet controller. Signed-off-by: Robert Marko <robert.marko@sartura.hr>
* mvebu: cortexa72: enable USB PHYTomasz Maciej Nowak2023-09-082-0/+2
| | | | | | | | | Since kernel 5.13 this is needed to enable USB ports on all devices in subtarget. Previously TF-A and COMPHY driver might have set up this PHY, but not anymore. Signed-off-by: Tomasz Maciej Nowak <tmn505@gmail.com> Tested-by: Robert Marko <robimarko@gmail.com>
* mvebu: refresh 6.1 configsTomasz Maciej Nowak2023-09-084-10/+42
| | | | | | | This should be a part of kernel major bump. Fortunately it didn't stall compilation, so no fixes tag. Signed-off-by: Tomasz Maciej Nowak <tmn505@gmail.com>
* mvebu: add reset delays of PHYs for Fortinet FortiGate 50EINAGAKI Hiroshi2023-09-031-0/+4
| | | | | | | | | | Add reset-(de)assert-us to ethernet PHYs on Fortinet FortiGate 50E to solve instability after HW resetting of PHYs. (ex.: restarting "network" service, etc...) Fixes: #13391 Fixes: 102dc5a62506 ("mvebu: add support for Fortinet FortiGate 50E") Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* mvebu: mcbin-singleshot: enable hearbeat LED by defaultTomasz Maciej Nowak2023-08-102-0/+44
| | | | | | | | | This has been a part of modified upstream patch but got lost on major kernel bump to 5.15, so bring it back. Signed-off-by: Tomasz Maciej Nowak <tmn505@gmail.com> [Add patch for kernel 6.1 too] Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump 6.1 to 6.1.44John Audia2023-08-091-3/+3
| | | | | | | | | | | | Changelog: https://lore.kernel.org/stable/2023080822-repost-unfiled-2f01@gregkh/ All patches automatically rebased. Build system: x86/64 Build-tested: x86/64/AMD Cezanne, filogic/xiaomi_redmi-router-ax6000-ubootmod Run-tested: x86/64/AMD Cezanne, filogic/xiaomi_redmi-router-ax6000-ubootmod Signed-off-by: John Audia <therealgraysky@proton.me>
* kernel: bump 5.15 to 5.15.125John Audia2023-08-091-3/+3
| | | | | | | | | | 1. Add new symbols to generic config 2. Bump kernel Changelog: https://lore.kernel.org/stable/2023080818-groin-gradient-a031@gregkh/ All patches automatically rebased. Signed-off-by: John Audia <therealgraysky@proton.me>
* kernel: bump 5.15 to 5.15.124John Audia2023-08-091-1/+1
| | | | | | | | | | | | | Changelog: https://lore.kernel.org/stable/2023080341-curliness-salary-4158@gregkh/ 1. Needed to make a change to to package/kernel/linux/modules/netsupport.mk due to upstream moving vxlan to its own directory[1]. @john-tho suggested using the the 6.1 xvlan FILES to circumvent. 2. All patches automatically rebased. 1. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.15.124&id=77396fa9096abdbfbb87d63e73ad44d5621cf103 Signed-off-by: John Audia <therealgraysky@proton.me>
* mvebu: add kernel 6.1 as testing kernelStefan Kalscheuer2023-08-021-0/+1
| | | | | | | | | | With an initial set of patches and configs in place let's start testing with kernel 6.1. Run-tested on the cortexa9 subtarget (WRT1900ACS, Turris Omnia) Tested-by: Etienne Champetier <champetier.etienne@gmail.com> Signed-off-by: Stefan Kalscheuer <stefan@stklcode.de>
* mvebu: copy 5.15 kconfigs to 6.1Stefan Kalscheuer2023-08-024-0/+618
| | | | | | Start 6.1 migration with a full copy of the current stable config. Signed-off-by: Stefan Kalscheuer <stefan@stklcode.de>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-18 01:50:16 +0000