summaryrefslogtreecommitdiffstats
path: root/target
Commit message (Collapse)AuthorAgeFilesLines
* malta: Remove kernel 6.1 configurationHauke Mehrtens2024-05-281-265/+0
| | | | | | | Malta is using kernel 6.6 by default now, remove configuration for kernel 6.1. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* malta: Use kernel 6.6 by defaultHauke Mehrtens2024-05-281-2/+1
| | | | | | All 4 subtargets are compiling fine and booting up in qemu. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* lantiq: disable building of ZyXEL P-2812HNU F1Nick Hainke2024-05-281-0/+1
| | | | | | | Disable image building for the board, since the kernel of the main branch is to big to fit into the kernel partition. Signed-off-by: Nick Hainke <vincent@systemli.org>
* lantiq: switch to kernel 6.1Martin Schiller2024-05-271-2/+1
| | | | | | Let's switch the lantiq target to use kernel 6.1 by default. Signed-off-by: Martin Schiller <ms@dev.tdt.de>
* ath79: add support for Dell SonicPoint ACe APL26-0AETomasz Maciej Nowak2024-05-274-0/+252
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Dell/SonicWall APL26-0AE (marketed as SonicPoint ACe) is a dual band wireless access point. End of life as of 2022-07-31. Specification SoC: QualcommAtheros QCA9550 RAM: 256 MB DDR2 Flash: 32 MB SPI NOR WIFI: 2.4 GHz 3T3R integrated 5 GHz 3T3R QCA9890 oversized Mini PCIe card Ethernet: 2x 10/100/1000 Mbps QCA8334 port labeled lan1 is PoE capable (802.3at) USB: 1x 2.0 LEDs: LEDs: 6x which 5 are GPIO controlled and two of them are dual color Buttons: 2x GPIO controlled Serial: RJ-45 port, SonicWall pinout baud: 115200, parity: none, flow control: none Before flashing, be sure to have a copy of factory firmware, in case You wish to revert to original firmware. All described procedures were done in following environment: ROM Version: SonicROM (U-Boot) 8.0.0.0-11o SafeMode Firmware Version: SonicOS 8.0.0.0-14o Firmware Version: SonicOS 9.0.1.0 In case of other versions, following installation instructions might be ineffective. Installation 1. Prepare TFTP server with OpenWrt sysupgrade image and rename that image to "sp_fw.bin". 2. Connect to one of LAN ports. 3. Connect to serial port. 4. Hold the reset button (small through hole on side of the unit), power on the device and when prompted to stop autoboot, hit any key. The held button can now be released. 5. Alter U-Boot environment with following commands: setenv bootcmd bootm 0x9F110000 saveenv 6. Adjust "ipaddr" (access point, default is 192.168.1.1) and "serverip" (TFTP server, default is 192.168.1.10) addresses in U-Boot environment, then run following commands: tftp 0x80060000 sp_fw.bin erase 0x9F110000 +0x1EF0000 cp.b 0x80060000 0x9F110000 $filesize 7. After successful flashing, execute: boot 8. The access point will boot to OpenWrt. Wait few minutes, until the wrench LED will stop blinking, then it's ready for configuration. Known issues Initramfs image can't be bigger than specified kernel size, otherwise bootloader will throw LZMA decompressing error. Switching to lzma-loader should workaround that. This device has Winbond 25Q256FVFG and doesn't have reliable reset, which causes hang on reboot, thus broken-flash-reset needs to be added. This property addition causes dispaly of "scary" warning on each boot, take this warnig into consideration. Signed-off-by: Tomasz Maciej Nowak <tmn505@gmail.com>
* ramips: samknows whitebox v8: set wifi frequencyMieczyslaw Nalewaj2024-05-251-0/+1
| | | | | | | Set the 2.4GHz frequency for WiFi. Fixes: #15391 Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com>
* layerscape: add 6.6 testing kernelPawel Dembicki2024-05-251-0/+1
| | | | | | Support is ready. Let's enable 6.6 as testing version. Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* layerscape: adjust dts path in image scriptsPawel Dembicki2024-05-253-20/+22
| | | | | | | After the spliting dts folder of ARM architecture in upstream, layerscape routines need to be adjusted for new solution. Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* layerscape: refresh 6.6 configPawel Dembicki2024-05-252-50/+65
| | | | | | | | | | | | | | | | | | | | | Mostly done by 'make kernel_oldconfig'. armv8_64b has added one entry manually: CONFIG_CRYPTO_CURVE25519=y as workaround for error: aarch64-openwrt-linux-musl-ld: crypto/crypto_engine.o: in function `crypto_engine_register_kpp': crypto_engine.c:687: undefined reference to `crypto_register_kpp' crypto_engine.c:687:(.text+0x57c): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `crypto_register_kpp' aarch64-openwrt-linux-musl-ld: crypto/crypto_engine.o: in function `crypto_engine_unregister_kpp': crypto/crypto_engine.c:693: undefined reference to `crypto_unregister_kpp' crypto_engine.c:693:(.text+0x5a0): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `crypto_unregister_kpp' Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* generic: kernel add 6.6 missing symbolsPawel Dembicki2024-05-251-0/+8
| | | | | | Found durring works on layerscape. Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* layerscape: kernel: refresh 6.6 patchesPawel Dembicki2024-05-257-244/+141
| | | | | | | | | | | | | | | | Taken refreshed version from Layerscape 6.6 tree: 302-arm64-dts-ls1012a-update-with-ppfe-support.patch 304-arm64-dts-ls1012a-rdb-workaround-by-updating-qspi-fl.patch 400-LF-20-3-mtd-spi-nor-Use-1-bit-mode-of-spansion-s25fs.patch 701-staging-add-fsl_ppfe-driver.patch 702-phy-Add-2.5G-SGMII-interface-mode.patch 704-net-phylink-treat-PHY_INTERFACE_MODE_2500SGMII-in-ph.patch Removed: 704-net-phylink-treat-PHY_INTERFACE_MODE_2500SGMII-in-ph.patch (meld into 702) Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* kernel/layerscape: Restore kernel files for v6.1Pawel Dembicki2024-05-2511-0/+14166
| | | | | | | | | | 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: Pawel Dembicki <paweldembicki@gmail.com>
* kernel/layerscape: Create kernel files for v6.6 (from v6.1)Pawel Dembicki2024-05-2511-0/+0
| | | | | | | | This is an automatically generated commit. During a `git bisect` session, `git bisect --skip` is recommended. Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* mvebu: add support for Fortinet FortiWiFi 51EINAGAKI Hiroshi2024-05-254-2/+34
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fortinet FortiWiFi 51E (FWF-51E) is a UTM with 1x WLAN and 1x SSD, based on Armada 385 (88F6820). Specification: - SoC : Marvell Armada 385 88F6820 - RAM : DDR3 2 GiB (4x Micron MT41K512M8DA-107, "D9SGQ") - Flash : SPI-NOR 128 MiB (Macronix MX66L1G45GMI-10G) - SSD : mSATA SSD 32 GB (A-DATA XM21E (AXM21ES3-32GM-B)) - mode : SATA III 6Gbps - power : 3.3 VDC, 3.1 W (Max.) - Ethernet : 7x 10/100/1000 Mbps - LAN 1-5 : Marvell 88E6176 - WAN 1, 2 : Marvell 88E1512 (2x) - WLAN : Fortinet EMP7618-FT (Atheros AR9382 (2T2R)) - interface : MiniPCIe - LEDs/Keys : 18x/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 : Molex 5557-02R Flash instruction using initramfs image: 1. Power on FWF-51E 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): 90:6C:AC:xx:xx:98 (board-info (OpenWrt), 0xd880 (hex)) WAN 1 : 90:6C:AC:xx:xx:99 WAN 2 : 90:6C:AC:xx:xx:9A LAN 1 : 90:6C:AC:xx:xx:9B LAN 2 : 90:6C:AC:xx:xx:9C LAN 3 : 90:6C:AC:xx:xx:9D LAN 4 : 90:6C:AC:xx:xx:9E LAN 5 : 90:6C:AC:xx:xx:9F WLAN : 88:DC:96:xx:xx:xx (MiniPCIe Card) Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com> Tested-by: Raylynn Knight <rayknight@me.com>
* mvebu: add support for Fortinet FortiWiFi 50E-2RINAGAKI Hiroshi2024-05-254-2/+35
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fortinet FortiWiFi 50E-2R (FWF-50E-2R) is a UTM with 2x WLAN, based on Armada 385 (88F6820). Specification: - SoC : Marvell Armada 385 88F6820 - RAM : DDR3 2 GiB (4x Nanya NT5CC512M8EN-EK) - Flash : SPI-NOR 128 MiB (Macronix MX66L1G45GMI-10G) - Ethernet : 7x 10/100/1000 Mbps - LAN 1-5 : Marvell 88E6176 - WAN 1, 2 : Marvell 88E1512 (2x) - WLAN : Gemtek WMDQ-177ACN (Qualcomm Atheros QCA9892 (2T2R)) (2x) - interface : MiniPCIe - LEDs/Keys : 18x/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.5 A - plug : Molex 5557-02R Flash instruction using initramfs image: 1. Power on FWF-50E-2R 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): 90:6C:AC:xx:xx:98 (board-info (OpenWrt), 0xd880 (hex)) WAN 1 : 90:6C:AC:xx:xx:99 WAN 2 : 90:6C:AC:xx:xx:9A LAN 1 : 90:6C:AC:xx:xx:9B LAN 2 : 90:6C:AC:xx:xx:9C LAN 3 : 90:6C:AC:xx:xx:9D LAN 4 : 90:6C:AC:xx:xx:9E LAN 5 : 90:6C:AC:xx:xx:9F WLAN 1: 1C:49:7B:xx:xx:xx (MiniPCIe Card) WLAN 2: 1C:49:7B:xx:xx:xx (MiniPCIe Card) Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com> Tested-by: Raylynn Knight <rayknight@me.com>
* mvebu: add support for Fortinet FortiGate 52EINAGAKI Hiroshi2024-05-254-2/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fortinet FortiGate 52E (FG-52E) is a UTM, based on Armada 385 (88F6820). Specification: - SoC : Marvell Armada 385 88F6820 - RAM : DDR3 2 GiB (4x Micron MT41K512M8DA-107, "D9SGQ") - Flash : SPI-NOR 128 MiB (Macronix MX66L1G45GMI-10G) - SSD : mSATA SSD 64 GB (2x A-DATA XM21E (AXM21ES3-32GM-B)) - mode : SATA III 6Gbps - power : 3.3 VDC, 3.1 W (Max.) - Ethernet : 7x 10/100/1000 Mbps - LAN 1-5 : Marvell 88E6176 - WAN 1, 2 : Marvell 88E1512 (2x) - LEDs/Keys : 18x/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.5 A - plug : Molex 5557-02R Flash instruction using initramfs image: 1. Power on FG-52E 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): 90:6C:AC:xx:xx:98 (board-info (OpenWrt), 0xd880 (hex)) WAN 1 : 90:6C:AC:xx:xx:99 WAN 2 : 90:6C:AC:xx:xx:9A LAN 1 : 90:6C:AC:xx:xx:9B LAN 2 : 90:6C:AC:xx:xx:9C LAN 3 : 90:6C:AC:xx:xx:9D LAN 4 : 90:6C:AC:xx:xx:9E LAN 5 : 90:6C:AC:xx:xx:9F Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* mvebu: add support for Fortinet FortiGate 51EINAGAKI Hiroshi2024-05-254-2/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fortinet FortiGate 51E (FG-51E) is a UTM, based on Armada 385 (88F6820). Specification: - SoC : Marvell Armada 385 88F6820 - RAM : DDR3 2 GiB (4x Micron MT41K512M8DA-107, "D9SGQ") - Flash : SPI-NOR 128 MiB (Macronix MX66L1G45GMI-10G) - SSD : mSATA SSD 32 GB (A-DATA XM21E (AXM21ES3-32GM-B)) - mode : SATA III 6Gbps - power : 3.3 VDC, 3.1 W (Max.) - Ethernet : 7x 10/100/1000 Mbps - LAN 1-5 : Marvell 88E6176 - WAN 1, 2 : Marvell 88E1512 (2x) - LEDs/Keys : 18x/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.5 A - plug : Molex 5557-02R Flash instruction using initramfs image: 1. Power on FG-51E 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:98 (board-info (OpenWrt), 0xd880 (hex)) WAN 1 : 70:4C:A5:xx:xx:99 WAN 2 : 70:4C:A5:xx:xx:9A LAN 1 : 70:4C:A5:xx:xx:9B LAN 2 : 70:4C:A5:xx:xx:9C LAN 3 : 70:4C:A5:xx:xx:9D LAN 4 : 70:4C:A5:xx:xx:9E LAN 5 : 70:4C:A5:xx:xx:9F Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com> Tested-by: Raylynn Knight <rayknight@me.com>
* mvebu: separate common parts to new dtsi for FortiGate/FortiWiFi 5xEINAGAKI Hiroshi2024-05-252-168/+173
| | | | | | | Add a new dtsi which contains the common parts of Fortinet FortiGate/FortiWiFi 5xE series devices. Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* mvebu: separate common parts to new dtsi for FortiGate/FortiWiFi 3xEINAGAKI Hiroshi2024-05-252-92/+97
| | | | | | | Add a new dtsi which contains the common parts of Fortinet FortiGate/FortiWiFi 3xE series devices. Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* mvebu: rename common dtsi of FortiGate 30E/50EINAGAKI Hiroshi2024-05-253-2/+2
| | | | | | | Rename the common dtsi of Fortinet FortiGate 30E/50E for the preparation of adding support for the other FortiGate/FortiWiFi 3xE/5xE devices. Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* mvebu: add common image definition for FortiGate devicesINAGAKI Hiroshi2024-05-251-13/+11
| | | | | | | | Add a common definition of Fortinet FortiGate devices to image/cortexa9.mk for a preparation of adding support for other FortiGate 3xE/5xE devices. Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* ath79: qca9563: add support for Amplifi Router HDKristian Skramstad2024-05-253-0/+210
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Hardware: SoC: Qualcomm Atheros QCA956X ver 1 rev 0 CPU clock: 775.000 MHz Memory: 128 MB DDR2 Flash: 32 MB SPI NOR mx25l25635e Switch: Atheros AR8327 rev. 4 Ethernet: 5x 10/100/1000 Mbps (1 WAN + 4 LAN) Buttons: 1x Reset Serial: TX, RX, GND, VCC Baudrate: 115200 Wifi: Qualcomm Atheros qca988x 802.11ac/n - 3x3 Qualcomm Atheros AR9561 802.11b/g/n - 3x3 Not working: Leds: 1x via a SPI controller Display: ST7789V or ILI9341V controlled by stm32f205. Note: DSA changes are ready, but we have an issue with ports not working after 20-30 minutes. So for now we use swconfig. Installation: serial connection only There is a J11 four pin connector. You need to connect TX, RX and GND. You can find very good information about the device here https://github.com/alexanderhenne/AFi-R?tab=readme-ov-file#finding-j11 Upgrading via serial port: 1. Download the kernel initramfs image. Copy the image to a TFTP server 2. Connect to console on the AP, and connect the LAN1 port to your PC LAN 3. Stop autoboot to get to U-boot shell Interrupt the autoboot process by pressing any key when prompted 4. Transfer the kernel image with TFTP Set your ip address on your TFTP server to 192.168.1.254 # tftpboot 0x81000000 amplifi-router-hd-initramfs-kernel.bin 5. Load the image # bootm 0x81000000 6. SCP sysupgrade image from your PC to the Amplifi HD (If you use a newer mac use scp -O) # scp openwrt-ath79-generic-ubnt_amplifi-router-hd-squashfs-sysupgrade.bin root@192.168.1.1:/tmp/ 7. Write sysupgrade to the firmware partition # mtd write /tmp/openwrt-ath79-generic-ubnt_amplifi-router-hd-squashfs-sysupgrade.bin firmware 8. Reboot your device # reboot Credit to alexanderhenne for all the information. Signed-off-by: Kristian Skramstad <kristian+github@83.no>
* ramips: add support for ELECOM WRC-X1800GSINAGAKI Hiroshi2024-05-254-0/+307
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ELECOM WRC-X1800GS is a 2.4/5 GHz band 11ax (Wi-Fi 6) router, based on MT7621A. Specification: - SoC : MediaTek MT7621A - RAM : DDR3 256 MiB - Flash : RAW-NAND 128 MiB (Macronix MX30LF1G28AD-TI) - WLAN : 2.4/5 GHz 2T2R (MediaTek MT7915D) - Ethernet : 5x 10/100/1000 Mbps - switch : MediaTek MT7530 (SoC) - LEDs/Keys (GPIO) : 7x/4x - UART : pin-header on PCB ("J5") - arrangement : 3.3V, TX, RX, NC, GND from tri-angle marking - settings : 115200n8 - Power : 12 VDC, 1 A Flash instruction using initramfs-factory image: 1. Boot WRC-X1800GS normally with "Router" mode 2. Access to "http://192.168.2.1/" and open firmware update page ("ファームウェア更新") 3. Select the OpenWrt initramfs-factory image and click apply ("適用") button 4. After flashing initramfs-factory image and reboot, upload the sysupgrade image and perform sysupgrade with it 5. Wait ~120 seconds to complete flashing Notes: - WRC-X1800GS has 2x os images. Those are switched on every firmware updating on stock firmware, but dual-boot feature on this device cannot be handled on OpenWrt. So the 1st image is always used on OpenWrt. This is controlled by "bootnum" variable embedded in "persist" partition (addr: 0x4). - WRC-X1800GS has 2x HW revisions. There are some small changes, but the same DeviceTree in stock firmware is used for both revisions. On this support of WRC-X1800GS, 2x green:wlan-2g-N LEDs are defined for each revision and the same default triggers are set. MAC addresses: LAN : 38:97:A4:xx:xx:38 (Factory, 0x1fdfa (hex) / Ubootenv, ethaddr (text)) WAN : 38:97:A4:xx:xx:3B (Factory, 0x1fdf4 (hex)) 2.4 GHz: 38:97:A4:xx:xx:39 5 GHz : 38:97:A4:xx:xx:3A Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* ramips: parameterize some values in Build/znet-headerINAGAKI Hiroshi2024-05-251-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Parameterize magic number and header length to use the device-specific values. example: On WRC-X1800GS, an additional ELECOM-specific header and a magic number "COMC" are required. Stock FW v1.18: $ hexdump -n $((0x40080)) -C wrc-x1800gs_v1.18.bin 00000000 45 4c 45 43 4f 4d 00 00 57 52 43 2d 58 31 38 30 |ELECOM..WRC-X180| 00000010 30 47 53 00 00 00 00 00 00 00 00 00 00 00 00 00 |0GS.............| 00000020 00 00 00 00 00 00 00 00 31 2e 31 38 00 00 00 00 |........1.18....| 00000030 00 00 00 00 00 00 00 00 43 4f 4d 43 04 00 ac 00 |........COMC....| 00000040 40 f0 49 74 b1 e8 6a ca e4 20 65 1f 34 2e 30 34 |@.It..j.. e.4.04| 00000050 28 58 56 46 2e 31 29 62 31 37 00 00 00 00 00 00 |(XVF.1)b17......| 00000060 00 00 00 00 00 00 00 00 ff ff ff ff ff ff ff ff |................| 00000070 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................| * 00040000 d0 0d fe ed 00 36 9c c0 00 00 00 38 00 36 9a e0 |.....6.....8.6..| 00040010 00 00 00 28 00 00 00 11 00 00 00 10 00 00 00 00 |...(............| 00040020 00 00 00 6c 00 36 9a a8 00 00 00 00 00 00 00 00 |...l.6..........| 00040030 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00 00 |................| 00040040 00 00 00 03 00 00 00 04 00 00 00 62 65 54 97 8f |...........beT..| 00040050 00 00 00 03 00 00 00 28 00 00 00 00 4d 49 50 53 |.......(....MIPS| 00040060 20 4f 70 65 6e 57 72 74 20 46 49 54 20 28 46 6c | OpenWrt FIT (Fl| 00040070 61 74 74 65 6e 65 64 20 49 6d 61 67 65 20 54 72 |attened Image Tr| 00040080 Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* ipq40xx: eap1300: add eap1300ext as alt modelRyan Castellucci2024-05-251-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The EnGenius EAP1300 and EAP1300EXT use identical boards and firmware (as flashed) from the vendor. As with the EAP1300, the EAP1300EXT requires a specific firmware version to flash OpenWRT. Unfortunately, the required firmware is truncated on the vendor's website. A working file can be created as follows: ``` curl \ https://www.engeniustech.com/wp_firmware/eap1300-all-v3.5.3.5_c1.9.04.bin \ | perl -pe 's/\x09EAP1300_A/\x0cEAP1300EXT_A/' \ > eap1300ext-all-v3.5.3.5_c1.9.04.bin ``` The file should have sha256: `58a1197a426139a12b03fd432334e677124cbe3384349bd7337f2ee71f1dcfd4`. Please see commit 2b4ac79 for further details. The vendor firmware must be decrypted before it can be flashed from OpenWRT. A tool able to do that is available from: https://github.com/ryancdotorg/enfringement/blob/main/decrypt.py Signed-off-by: Ryan Castellucci <code@ryanc.org>
* mediatek: filogic: prevent faulty mac address assignmentLeon M. Busch-George2024-05-253-6/+2
| | | | | | | | | | | | The vendor U-Boot on the Cudy M3000 and the Yuncore AX835 assign random mac addresses on boot and set the 'local-mac-address' property which prevents Openwrt from assigning the correct address from evmem. This patch removes the alias for ethernet0 so that U-Boot doesn't add the property, removes the workaround from 02_network, and adds back the nvmem definition for the M3000. Signed-off-by: Leon M. Busch-George <leon@georgemail.eu>
* ixp4xx: Add back support for D-Link DSM G600 ALinus Walleij2024-05-252-0/+13
| | | | | | | | | OpenWrt supported the D-Link DSM G600 A in the past. It has 64 MB of RAM and 16 MB of flash so it will run just fine, and should be quite usable with a rootfs on an external harddrive. Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
* ixp4xx: Add back support for Freecom FSG-3Linus Walleij2024-05-252-0/+25
| | | | | | | | | | | | | | | | | | | | | | | | OpenWrt supported the Freecom FSG-3 in the past. It has 64 MB of RAM so will run fine, but the bare 4 MB of flash makes it a non-default target. The generated compressed image is currently below 4MB (just 3.3 MB) though, so it should be possible to flash just fine with a rootfs on a harddrive or USB stick, which is what the FSG-3 used in the past as well. The device has a WAN port on eth0 and three LAN ports on eth1. The LAN ports are probably a DSA switch but the old OpenWrt base never activated that, instead it relies on boot defaults. Due to questionable usablity without tweaking and further work this image is not built by default, but made available for developers who know what they are doing. The TAR+CRC image generation is a rewritten version of the earlier support code. Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
* ixp4xx: Add back support for Iomega NAS100DLinus Walleij2024-05-252-0/+14
| | | | | | | | | | | | OpenWrt supported the Iomega NAS100D in the past and it has 64 MB of RAM so if booted from a harddrive it will probably work just fine. The APEX boot loader already has a build variant for this machine that we can just pick up and use. This device has a single ethernet port so bring this online with DHCP as expected for a NAS device. Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
* ixp4xx: Add ext4 and rootfs-part to featuresLinus Walleij2024-05-251-1/+1
| | | | | | | | Several of the IXP4xx machines mount root on external harddrives so add EXT4 and rootfs-part to the featureset so the right features are always selected. Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
* mediatek: filogic: add Adtran SmartRG Mount Stuart seriesDaniel Golle2024-05-249-7/+811
| | | | | | | | | | | | | | | | | | | | | | | | | | Common specifications: * Mediatek MT7988A (4x Cortex-A73, up to 1.8 GHz clock speed) * 8 GiB eMMC * 2 GiB DDR4 RAM * 1x 10000M/1000M/100M + 3x 1000M/100M/10M LAN ports * MT7996 Tri-band (2.4G, 5G, 6G) 4T4R 802.11be Wi-Fi * Airoha AG3352 GPS * Renesas DA14531MOD Bluetooth * 2 buttons (Reset, Mesh/WPS) * uC-controlled RGB LED via I2C * 2x LED for each 1G port, 3x LED for each 10G port * USB 3.0 type A port * 3.3V-level 115200 baud UART console via 4-pin Dupont connector exposed at the bottom of the device * USB-C PD power input SDG-8733: 1x 10000M/1000M/100M WAN port SDG-8734: 1x USXGMII/10GBase-R/5GBase-R/2500Base-X/1000Base-X/SGMII SFP+ Both models are also available in versions including 2x FXS POTS interfaces for analog phones. Those interfaces are not supported by OpenWrt. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* mediatek: fix sysupgrade config backup on Adtran SmartRG devicesDaniel Golle2024-05-241-0/+4
| | | | | | | Add missing call to emmc_copy_config which either writes the sysupgrade tar.gz backup file or clears the existing rootfs_data overlay. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* generic: 6.6: backports and add LED support for Aquantia PHYsDaniel Golle2024-05-244-12/+480
| | | | | | | Backport patch adding support for the AQR114C PHY and add support for PHY LEDs and polarity setting of Aquantia 3rd and 4th generation PHYs. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* ath79: add support for 8Devices Carambola3 boardAndrey Bondar2024-05-244-0/+148
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Carambola3 is a WiFi module based on Qualcomm/Atheros QCA4531 http://wiki.8devices.com/carambola3 Specification: - 650/600/216 MHz (CPU/DDR/AHB) - 128 MB of RAM (DDR2) - 32 MB of FLASH - 2T2R 2.4 GHz - 2x 10/100 Mbps Ethernet - 1x USB 2.0 Host socket - UART for serial console - 12x GPIO Flash instructions: Upgrading from ar71xx target: - Upload image into the board: scp openwrt-ath79-generic-8dev_carambola3-squashfs-sysupgrade.bin \ root@192.168.1.1/tmp/ - Run sysupgrade sysupgrade -F /tmp/openwrt-ath79-generic-8dev_carambola3-squashfs-sysupgrade.bin Upgrading from u-boot: - Set up tftp server with openwrt-ath79-generic-8dev_carambola3-initramfs-kernel.bin - Go to u-boot (reboot and press ESC when prompted) - Set TFTP server IP setenv serverip 192.168.1.254 - Set device ip from the same subnet setenv ipaddr 192.168.1.1 - Copy new firmware to board tftpboot 0x82000000 initramfs.bin - Boot OpenWRT bootm 0x82000000 - Upload image openwrt-ath79-generic-8dev_carambola3-squashfs-sysupgrade.bin into the board - Run sysupgrade. Signed-off-by: Andrey Bondar <a.bondar@8devices.com> Link: https://github.com/openwrt/openwrt/pull/15514 Signed-off-by: Robert Marko <robimarko@gmail.com>
* ramips: add support for TP-Link Archer MR200v5Lea Teuberth2024-05-234-0/+216
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Specifications: CPU: MT7628AN 580MHz RAM: 64MB DDR2 FLASH: 8MB EN25QH64 NOR SPI WIFI: 2.4GHz 2x2 MT7628 b/g/n internal WIFI: 5GHz 1x1 MT7610E ac/n PCI LTE: Qualcomm MDM9207 ETH: 4xLAN 100base-T integrated SWITCH: RT3050-ESW Port 0,1,2,3: LAN, Port 6: CPU LEDS: LAN, WAN, Power, 3x signal strength, WiFi BTNS: Reset, WiFi toggle UART: Near ETH ports, Vcc-GND-RX-TX, 115200, 8N1 Installation: 1. Update using recovery mode - set your IP to 192.168.0.225, subnet mask: 255.255.255.0 - start tftp server, rename tftp-recovery.bin to tp_recovery.bin and place it into the server's directory - while holdig the "reset" button, power on the device - keep holding "reset" until the file is being transferred Notes: This board has only one MAC address programmed in the "romfile" partition: - MAC for phy0 (2.4GHz) at romfile 0xf100 (0) - MAC for phy1 (5GHz) at romfile 0xf100 (-1) - stock firmware re-uses phy0 MAC for ethernet - stock firmware uses romfile 0xf100 (1) for WWAN; not used since QMI interface is raw IP Signed-off-by: Lea Teuberth <lea.teuberth@outlook.com>
* mediatek: include "kmod-mt7915e" package per deviceRafał Miłecki2024-05-232-54/+54
| | | | | | | | | | | mt7915e driver supports MT7915 & MT7916 devices and MT7981 & MT7986 on-SoC wireless controllers. Devices based on MT7988 and possibly other next chipsets are quite unlikely to need it (MT7988 was designed to be used with MT7996). Move kmod-mt7915e to DEVICE_PACKAGES of relevant devices. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* ipq40xx: dont panic on PSGMII calibration failRobert Marko2024-05-221-1/+1
| | | | | | | | | | | Currently, in case that PSGMII calibration fails it will panic the kernel which is not ideal and is preventing any debugging to be done. So, since PGMII calibration failing only means that wired networking wont work lets convet the panic() call to dev_error. Link: https://github.com/openwrt/openwrt/pull/15542 Signed-off-by: Robert Marko <robimarko@gmail.com>
* qualcommax: ipq807x support Netgear Orbi Pro SXK80Andrew Smith2024-05-229-0/+607
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit adds support for Netgear Orbi Pro SXR80 and SXS80 (collectively known as SXK80) Specifications: --------------- * CPU: Qualcomm IPQ8074A Quad core Cortex-A53 * RAM: 1024MB * Storage: SPI-NAND 512 MiB (Winbond W29N04GZ) * Ethernet: 4x 1G RJ45 ports (QCA8075) 1x 2.5G RJ45 LAN/WAN (QCA8081) * WLAN: - 2.4 GHz: Qualcomm QCN5024 4x4 - 2x 5 GHz: Qualcomm QCN5054 4x4 (second radio high channels only) * LEDs: - Power: (Green and red) - Front: (Blue, green, red and white) * Buttons: - 1x Soft reset - 1x Sync/WPS * Power: 12V DC Jack Installation instructions (Telnet): ----------------------------------- *Note, this guide assumes SXR80, for SXS80 change the firmware file name as appropriate 1. Put firmware file openwrt-qualcommax-ipq807x-netgear_sxr80-initramfs-uImage.itb in root of TFTP server available at 192.168.1.10. 2. Enable telnet by going to http://[ip of device]/debug.htm and clicking on the tickbox 'Enable telnet' 3. Telnet into the device and login using the same username and password as the web interface: 4. Run the following command: `fw_setenv bootcmd 'env default -a; saveenv; reset'` 5. Reboot the router, once the web interface is available again re-enable telnet via http://[ip of device]/debug.htm and telnet into the device. 6. Run the following command: `fw_printenv` It should look similar to the below: ``` baudrate=115200 bootargs=console=ttyMSM0,115200n8 bootcmd=mii write 0x0 0x0 0x800; sleep 1; nmrp; bootdni; boot_DNI_secureboot bootdelay=2 ipaddr=192.168.1.1 netmask=255.255.255.0 serverip=192.168.1.10 soc_version_major=2 soc_version_minor=0 ``` **If you see the message:** `Warning: Bad CRC, using default environment` **DO NOT CONTINUE, YOU WILL BRICK YOUR DEVICE** 7. Run the following command: `fw_setenv originalboot 'mii write 0x0 0x0 0x800; sleep 1; nmrp; bootdni; boot_DNI_secureboot'` (This should match what's in the bootcmd variable displayed in step 6) 8. Run the following commands: ``` fw_setenv wrttftp 'mii write 0x0 0x0 0x800; sleep 1; nmrp; if tftpboot openwrt-qualcommax-ipq807x-netgear_sxr80-initramfs-uImage.itb; then bootm; fi; bootdni; boot_DNI_secureboot' fw_setenv wrtboot 'mii write 0x0 0x0 0x800; sleep 1; nmrp; nand read 0x40000000 0x1980000 0x06d00000; bootm 0x40000000' fw_setenv bootcmd 'run wrttftp' ``` 9. Ensure SXR/S device is attached via ethernet (LAN port) to the same ethernet segment as the TFTP server. 10. Reboot the device, it should reboot into OpenWrt and be available on 192.168.1.1 11. Once OpenWrt has booted, update the bootcmd using the following command: `fw_setenv bootcmd 'run wrtboot'` 12. Flash the sysupgrade image 13. It should boot into OpenWrt References to SXK80 GPL source: https://www.downloads.netgear.com/files/GPL/SXK80-V3.2.0.108_gpl_src.tar.bz2.zip Signed-off-by: Flole Systems <flole@flole.de> Signed-off-by: Andrew Smith <gul.code@outlook.com> Link: https://github.com/openwrt/openwrt/pull/14939 Signed-off-by: Robert Marko <robimarko@gmail.com>
* qualcommax: ipq807x: sax1v1k: fix QCA8081 resetRobert Marko2024-05-211-0/+1
| | | | | | | | | | | | It seems that on Spectrum SAX1V1K QCA8081 is being brought out of reset too quickly and thus causing it to get stuck in an invalid autoneg register configuration mode. Setting an deasset delay seems to fix this, so lets set it. Fixes: #15493 Link: https://github.com/openwrt/openwrt/pull/15541 Signed-off-by: Robert Marko <robimarko@gmail.com>
* mediatek/filogic: add OpenWrt One supportJohn Crispin2024-05-216-1/+517
| | | | | | | | | | | | | | | | | | | | | | | | | Specification: - MT7981 CPU using 2.4GHz and 5GHz WiFi (both AX) - 1GB RAM - 16MB NOR - 128MB NAND - 3 LEDs (red, green, blue, white) - 2 buttons (reset, user defined) - 1 2.5Gbit WAN port (Airoha EN8811h) - 1 1Gbit LAN ports - 1 single lane M.2 SSD slot - 1 mikroBus socket - externel HW WDT (25s refresh time) - i2c RTC (with battery backup) Serial Interface - UBS-C CDC-ACM - 3 Pins GND, RX, TX - Settings: 115200, 8N1 MAC addresses are not populated on the early samples. Signed-off-by: John Crispin <john@phrozen.org>
* Revert "mediatek/filogic: add OpenWrt One support"John Crispin2024-05-216-517/+1
| | | | | | | | This reverts commit 797904b3cb4a5c575641c19e7f3989926e4c7902. There is a stray line in the commit description Signed-off-by: John Crispin <john@phrozen.org>
* mediatek/filogic: add OpenWrt One supportJohn Crispin2024-05-216-1/+517
| | | | | | | | | | | | | | | | | | | | | | | | | | | filogic: Add support for D-Link AQUILA PRO AI M30 Specification: - MT7981 CPU using 2.4GHz and 5GHz WiFi (both AX) - 1GB RAM - 16MB NOR - 128MB NAND - 3 LEDs (red, green, blue, white) - 2 buttons (reset, user defined) - 1 2.5Gbit WAN port (Airoha EN8811h) - 1 1Gbit LAN ports - 1 single lane M.2 SSD slot - 1 mikroBus socket - externel HW WDT (25s refresh time) - i2c RTC (with battery backup) Serial Interface - UBS-C CDC-ACM - 3 Pins GND, RX, TX - Settings: 115200, 8N1 MAC addresses are not populated on the early samples. Signed-off-by: John Crispin <john@phrozen.org>
* mediatek/filogic: enable led PWM driver by defaultJohn Crispin2024-05-211-0/+1
| | | | Signed-off-by: John Crispin <john@phrozen.org>
* mediatek/filogic: fix mt7981.dtsi PCIe supportJohn Crispin2024-05-211-1/+1
| | | | | | | * the compatible string was wrong * the pinmux was missing Signed-off-by: John Crispin <john@phrozen.org>
* ixp4xx: Bump to kernel v6.6Linus Walleij2024-05-2010-39/+139
| | | | | | | | | | | | The IXP4xx is well supported upstream and can readily be supported with kernel v6.6. To simplify things after the DTS directory was renamed, switch to v6.6 only. Bring in some outstanding patches. Tested on the Gateworks GW2348-4. Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
* gemini: In-flight ethernet patchesLinus Walleij2024-05-196-0/+420
| | | | | | | | | | These patches have partial acceptance upstream and are still a WIP, now there is merge window for kernel v6.10 so these will not be reposted until that is over. In the meantime, let's add the current state to OpenWrt so the ethernet on Gemini is up and working (tested on several devices). Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
* imagebuilder: fix multiple issue with manifest and sign keys handlingChristian Marangi2024-05-191-2/+10
| | | | | | | | | Fix multiple issue with manifest handling where APK was hardcoded and fix a logic error where (TODO) APK _check_keys was called for the OPKG codepath instead of correctly calling for the APK codepath. Fixes: d788ab376f85 ("build: add APK package build capabilities") Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* mediatek: add firmware name for AQR PHYs on mt7988a-rfbFelix Fietkau2024-05-192-0/+2
| | | | | | Fixes PHY probe in case there is no firmware in a connected EEPROM Signed-off-by: Felix Fietkau <nbd@nbd.name>
* mediatek: convert mt7988a-rfb to keep bl31/uboot in UBIFelix Fietkau2024-05-194-20/+115
| | | | | | | | Add ubi volumes for mt7988a-rfb and support for using factory data for Ethernet MAC addresses and MT7996 WLAN calibration data. Also add rootdisk handle. Removes the need to keep using nmbm Signed-off-by: Felix Fietkau <nbd@nbd.name>
* build: add APK package build capabilitiesPaul Spooren2024-05-172-11/+62
| | | | | | | | | A new option called `USE_APK` is added which generated APK packages (.apk) instead of OPKG packages (.ipk). Some features like fstools `snapshot` command are not yet ported Signed-off-by: Paul Spooren <mail@aparcar.org>
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-20 06:36:46 +0000