aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* bcm27xx: 6.1: refresh config and add missing symbolsÁlvaro Fernández Rojas2023-06-09
| | | | | | Refresh config for kernel 6.1 and add missing symbols. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm27xx: 6.1: add kernel patchesÁlvaro Fernández Rojas2023-06-09
| | | | | | Add kernel patches for version 6.1. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm27xx: 6.1: copy config from 5.15Álvaro Fernández Rojas2023-06-09
| | | | | | Copy config from 5.15 kernel version. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* kernel: 6.1: add missing Kconfig symbolsÁlvaro Fernández Rojas2023-06-09
| | | | | | Add missing symbol found during refreshing bcm27xx Kconfigs. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* openssl: update to 3.0.9Ivan Pavlov2023-06-09
| | | | | | | | | | | | | | CVE-2023-2650 fix Remove upstreamed patches Major changes between OpenSSL 3.0.8 and OpenSSL 3.0.9 [30 May 2023] * Mitigate for very slow OBJ_obj2txt() performance with gigantic OBJECT IDENTIFIER sub-identities. (CVE-2023-2650) * Fixed buffer overread in AES-XTS decryption on ARM 64 bit platforms (CVE-2023-1255) * Fixed documentation of X509_VERIFY_PARAM_add0_policy() (CVE-2023-0466) * Fixed handling of invalid certificate policies in leaf certificates (CVE-2023-0465) * Limited the number of nodes created in a policy tree (CVE-2023-0464) Signed-off-by: Ivan Pavlov <AuthorReflex@gmail.com>
* ipq807x: remove critical trips from AC/HK DTSIRobert Marko2023-06-08
| | | | | | | Now that critical trips are defined for all thermal zones in the SOC DTSI there is no need to duplicate them in AC and HK DTSI. Signed-off-by: Robert Marko <robimarko@gmail.com>
* ipq807x: add critical thermal trips to all thermal zonesRobert Marko2023-06-08
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Kernel 6.1 has started actually enforcing the bindings requirment that thermal zones must have associated trips described as well, otherwise they will fail during probing with: [ 0.865494] thermal_sys: Failed to find 'trips' node [ 0.867254] thermal_sys: Failed to find trip points for thermal-sensor id=4 [ 0.872271] thermal_sys: Failed to find 'trips' node [ 0.878898] thermal_sys: Failed to find trip points for thermal-sensor id=5 [ 0.884222] thermal_sys: Failed to find 'trips' node [ 0.890775] thermal_sys: Failed to find trip points for thermal-sensor id=6 [ 0.896073] thermal_sys: Failed to find 'trips' node [ 0.902668] thermal_sys: Failed to find trip points for thermal-sensor id=7 [ 0.907964] thermal_sys: Failed to find 'trips' node [ 0.914569] thermal_sys: Failed to find trip points for thermal-sensor id=8 [ 0.921203] thermal_sys: Failed to find 'trips' node [ 0.926469] thermal_sys: Failed to find trip points for thermal-sensor id=14 [ 0.931759] thermal_sys: Failed to find 'trips' node [ 0.938703] thermal_sys: Failed to find trip points for thermal-sensor id=15 So, since CPUFreq support isnt yet upstream we can start by adding critical trips to all of the thermal zones to protect the devices against severely overheating. Qualcomm has set the overheat trip at 120 C but lets be conservative and set it at 110 C. This patch has been sent upstream as well. Signed-off-by: Robert Marko <robimarko@gmail.com>
* generic: 6.1: move Qualcomm SoC ID bindings to genericRobert Marko2023-06-08
| | | | | | | | | | | Move the Qualcomm SoC ID bindings that are used by the CPUFreq NVMEM driver that was recently backported to generic from ipq807x as that series depends on SoC ID bindings but they were forgotten. Due to that IPQ806x builds would fail as the backport was still in ipq807x. Fixes: d44279 ("generic: 6.1: backport Qualcomm CPUFreq NVMEM changes") Signed-off-by: Robert Marko <robimarko@gmail.com>
* generic: 5.15: backport PPC VDSO executable stack fixRobert Marko2023-06-08
| | | | | | | | | | | | Recent binutils will warn if there is no .note.GNU-stack section and will interpret that as that stack is executable. So, lets modify the upstream 6.1 fix as in 5.15 VDSO32 and VDSO64 are still separate but later they were merged to resolve: /external-toolchain/openwrt-toolchain-mpc85xx-p1020_gcc-12.3.0_musl.Linux-x86_64/toolchain-powerpc_8548_gcc-12.3.0_musl/bin/../lib/gcc/powerpc-openwrt-linux-musl/12.3.0/../../../../powerpc-openwrt-linux-musl/bin/ld: warning: arch/powerpc/kernel/vdso32/getcpu.o: missing .note.GNU-stack section implies executable stack /external-toolchain/openwrt-toolchain-mpc85xx-p1020_gcc-12.3.0_musl.Linux-x86_64/toolchain-powerpc_8548_gcc-12.3.0_musl/bin/../lib/gcc/powerpc-openwrt-linux-musl/12.3.0/../../../../powerpc-openwrt-linux-musl/bin/ld: NOTE: This behaviour is deprecated and will be removed in a future version of the linker Signed-off-by: Robert Marko <robimarko@gmail.com>
* generic: drop useless binfmt patch fixing compilation warningChristian Marangi2023-06-08
| | | | | | | | | | | | | | | | | The compilation warning was triggered by wrongly set FRAME_WARN to 1024 even for 64bit. This was recently fix by correctly setting the FRAME_WARN to 2048 for 64bit systems. The compilation warning would still be triggered on 32bit system but the actual code is never reached as ARCH_USE_GNU_PROPERTY is only set on arm64 arch. Drop the patch as kmalloc cause perf regression as suggested by upstream maintainers. Fixes: fa79baf4a6e2 ("generic: copy backport, hack, pending patch and config from 5.15 to 6.1") Fixes: 5913ea1ba2fa ("generic: 5.15: add pending patch fixing binfmt compilation warning") Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* kernel: use struct group to wipe psb6970 volatile priv dataAleksander Jan Bajkowski2023-06-08
| | | | | | | | | | | | | | | | | | Instead of reference vlan and do strange subtraction, use the handy struct_group() to create a virtual struct of the same size of the members. This permits to have a more secure memset and fix compilation warning in 6.1 where additional checks are done. Fix compilation warning: | inlined from 'psb6970_reset_switch' at drivers/net/phy/psb6970.c:275:2: | ./include/linux/fortify-string.h:314:25: error: call to '__write_overflow_field' | declared with attribute warning: detected write beyond size of field | (1st parameter); maybe use struct_group()? [-Werror=attribute-warning] | 314 | __write_overflow_field(p_size_field, size); | | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |cc1: all warnings being treated as errors Signed-off-by: Aleksander Jan Bajkowski <olek2@wp.pl>
* oxnas: Enable CONFIG_CRYPTO_LZ4Jitao Lu2023-06-08
| | | | | | | | | | | | | | | | | | | | | Previously, CONFIG_LZ4_DECOMPRESS=y was selected by CONFIG_RD_LZ4 only. When building kernel for initramfs, CONFIG_RD_LZ4 will be unset by Kernel/SetInitramfs if the chosen compression method is not lz4, then CONFIG_LZ4_DECOMPRESS will become a *module* in the newly generated kernel config. However, the newly added module won't be built after 38c150612cc9be488527e342db92d5c74093213f, so packaging kmod-lib-lz4 fails due to missing lz4_decompress.ko. CONFIG_CRYPTO_LZ4=y makes CONFIG_LZ4_DECOMPRESS=y being selected w/o CONFIG_RD_LZ4, so that the modules of the default kernel and initramfs kernel are consistent. Fixes: #12766 Fixes: 38c150612cc ("build: revert 54070a1 (all kernels are >= 5.10)") Signed-off-by: Jitao Lu <dianlujitao@gmail.com>
* ramips: enable LED button for TP-Link EC330-G5u v1Mikhail Zhilkin2023-06-08
| | | | | | | | | The device already has LED push button (KEY_LIGHTS_TOGGLE) and exported GPIO control "led-light". This commit adds button handler script for switching on/off all device LEDs. Signed-off-by: Mikhail Zhilkin <csharper2005@gmail.com> Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ipq807x: use updated CPUFreq NVMEM supportRobert Marko2023-06-07
| | | | | | | | | | | | | Most of the CPUFreq NVMEM patches have been upstreamed in an improved way. IPQ8074 support itself is being reviewed upstream currently. Upstreamed patches have been moved to generic backports so that ipq806x can use them as well, so lets just use the latest version of IPQ8074 support that is being reviewed upstream. Runtime tested on Qnap 301W (IPQ8072A) and Xiaomi AX3600 (IPQ8071A). Signed-off-by: Robert Marko <robimarko@gmail.com>
* generic: 6.1: backport Qualcomm CPUFreq NVMEM changesRobert Marko2023-06-07
| | | | | | | | | | | | | | | | Currently, IPQ807x is using CPUFreq NVMEM for dealing with different SoC SKU-s having different frequency limits, and we are keeping the patches for it in ipq807x target. However, we managed to upstream a big cleanup of the driver in order to make it possible for other SMEM based targets to be added to CPUFreq NVMEM. IPQ806x will be using CPUFreq NVMEM and depends on these changes as well, so lets put them in generic backport to avoid code duplication. This replaces the older patches in ipq807x. Signed-off-by: Robert Marko <robimarko@gmail.com>
* kernel: ltq-ptm: do not write directly to dev->addrAleksander Jan Bajkowski2023-06-06
| | | | | | | | | | One is never to write to dev->addr directly. In 6.1 it will be a const and with the newly enabled WERROR, we get a failing grade. Lets fix this ahead of time. Ref: https://github.com/torvalds/linux/commit/adeef3e32146a8d2a73c399dc6f5d76a449131b1 Signed-off-by: Aleksander Jan Bajkowski <olek2@wp.pl>
* kernel: bump 6.1 to 6.1.32Robert Marko2023-06-06
| | | | | | | | | | | | | | | Removed upstreamed: generic-backport/610-v6.3-net-page_pool-use-in_softirq-instead.patch[1] All other patches automatically rebased. [1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/net?h=v6.1.32&id=7dccd5fa7edb9562da61af820bb9d0346447baf1 Build system: x86_64/Fedora 38 Build-tested: ipq807x/Dynalink DL-WRX36 Runtime-tested: ipq807x/Dynalink DL-WRX36 Signed-off-by: Robert Marko <robimarko@gmail.com>
* ipq807x: mark MDT loader fix as backportRobert Marko2023-06-06
| | | | | | | MDT loader fix for remoteproc was already merged, so mark it as a backport with the future 6.5 kernel version. Signed-off-by: Robert Marko <robimarko@gmail.com>
* ipq807x: refresh kernel configRobert Marko2023-06-06
| | | | | | | Refresh the kernel config as multiple options were disabled in the generic config since 6.1 was added to ipq807x. Signed-off-by: Robert Marko <robimarko@gmail.com>
* ipq807x: renumber upstreamed patchesRobert Marko2023-06-06
| | | | | | | We are running out of 00xx numbers to put backports into, so lets just renumber all of the upstreamed patches back to 0000 and onwards. Signed-off-by: Robert Marko <robimarko@gmail.com>
* mediatek: use DEVICE_DTC_FLAGS and drop DTC_FLAGS where not neededDaniel Golle2023-06-06
| | | | | | | | | | | | The MT7986 RFB was intended to use device tree overlays and for that reason modified DTC_FLAGS. zyxel_ex5601-t0-stock later on probably copied it from there. Both boards do not actually use device tree overlays, so remove setting DTC_FLAGS from both. The BPi-R3 does use device tree overlays, use DEVICE_DTC_FLAGS to give it an extra 4kb of padding for overlays to be applied. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* mediatek: use DEVICE_DTC_FLAGS for BPi-R64Daniel Golle2023-06-06
| | | | | | | Make sure there is an extra 4kb of padding to apply device tree overlays on the BPi-R64. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* image: introduce DEVICE_DTC_FLAGS and DEVICE_DTCO_FLAGSDaniel Golle2023-06-06
| | | | | | | | | | | Handle compiling device tree overlay blobs separate to allow for overlays being compiled with different parameters, mostly to safe space. Allow defining DEVICE_DTC_FLAGS and DEVICE_DTCO_FLAGS as per-device parameters to be passed to dtc. Previously some boards directly used DTC_FLAGS in their build recipe which then also affected other boards. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* generic: backport initial LEDs hw control supportChristian Marangi2023-06-06
| | | | | | | | | | | | Backport initial LEDs hw control support. Currently this is limited to only rx/tx and link events for the netdev trigger but the API got accepted and the additional modes are working on and will be backported later. Refresh every patch and add the additional config flag for QCA8K new LEDs support. Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* mediatek: set new compat version if booted on R64 and R3Daniel Golle2023-06-06
| | | | | | | | | | | | | | | | | If the board comes up with OpenWrt that means that the bootloader is recent enough and knows about the new device tree overlays. Using /etc/board.d/ is not enough in this case because it doesn't overwrite existing configuration which may exist (and is fine to exist) if the user updated with 'sysupgrade -F *.itb' and has kept configuration. They would still need to manually set compat_version even though the fact that the bootloader env has been updated can be implied by the fact that the system has started. Hence we can always set compat_version=1.1 for those two boards using uci-defaults. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* mediatek: sync MT7986 device trees with upstreamDaniel Golle2023-06-05
| | | | | | | | Sync device tree files for MT7986 boards with what landed in upstream Linux tree to easy maintainance and also allow for a smooth update to Linux 6.1. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* mediatek: use updated device tree overlay mechanism for BPi-R64Daniel Golle2023-06-05
| | | | | | Use new device tree overlay mechanism for the BananaPi BPi-R64 board. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* uboot-mediatek: adapt BPi-R3 and BPi-R64 to new device tree overlayDaniel Golle2023-06-05
| | | | | | | | Update bootloader environment for BPi-R3 and BPi-R64 to adapt to new device tree overlay mechanism now that support for multiple device tree overlays has been added. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* generic: use only first element in bootconf for uImage.FITDaniel Golle2023-06-05
| | | | | | | | | Now that it is possible to load several device tree overlays by appending their config names to bootconf the uImage.FIT partition parser need to discard everything after the first '#' character in bootconf when looking up the config node to be used. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* image: improve uImage.FIT device tree overlay supportDaniel Golle2023-06-05
| | | | | | | | | | Instead of generating full config nodes incl. kernel, generate minimal config nodes for device tree overlays to be applied to the main config. In this way, multiple device tree overlays can be applied more easily. While at it change filenames to upstream style, ie. use dtso and dtbo suffix for device tree overlays. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* mediatek: convert mt7986a-zyxel-ex5601-t0-stock.dts to UNIXDaniel Golle2023-06-05
| | | | | | The device tree file was in DOS format (CR-LF). Convert it to UNIX style. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* Revert "ipq807x: add initial support for prpl Foundation Haze board"Petr Štetiar2023-06-05
| | | | | | | This reverts commit 48603a271e6ff9e5cd851e873429893115e00c94 as this was commited by accident, its still work in progress. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* Revert "ipq-wifi: add board files for prpl Foundation Haze board"Petr Štetiar2023-06-05
| | | | | | | This reverts commit 6845c53ec3bb25dbbb0e8bbcf435fc380502fc56. as this was commited by accident, its still work in progress. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* Revert "WIP: ipq-wifi: use my fork temporarily until upstreamed"Petr Štetiar2023-06-05
| | | | | | | This reverts commit 1bad93c42669061b0248ca5cff1d83e399a2ef1a as this was commited by accident, its still work in progress. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* Revert "ath11k-firmware: update to WLAN.HK.2.9.0.1-01713-QCAHKSWPL_SILICONZ-1"Robert Marko2023-06-05
| | | | | | | | | | | This reverts commit 5d2de0055504727503a050731c3ca8c75b51f185. I received multiple reports that in various configurations this FW version is not stable and crashes, so lets revert to 01385 revision which works. Fixes #12815 Signed-off-by: Robert Marko <robimarko@gmail.com> Signed-off-by: Petr Štetiar <ynezz@true.cz> [fixes tag]
* ramips: fix lzma-loader for ASIARF boardsDaniel Danzberger2023-06-05
| | | | | | | This fixes a well known "LZMA ERROR 1" error, reported previously on numerous of similar devices. Signed-off-by: Daniel Danzberger <daniel@dd-wrt.com>
* sdk: Expose CCACHE_DIR optionJeffery To2023-06-05
| | | | | | | As the CCACHE option is already exposed, it would be helpful to also make the ccache directory easily customizable. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
* tools/coreutils: rename list of installed programsMichael Pratt2023-06-05
| | | | | | | | | | | Rename the list of programs installed by coreutils to PKG_PROGRAMS, which will create a stampfile for each through a new feature in host-build.mk. Also, cleanup a bit to save lines regarding the usage of this list. Signed-off-by: Michael Pratt <mcpratt@pm.me>
* tools/findutils: define list of installed programsMichael Pratt2023-06-05
| | | | | | | | | Define the variable PKG_PROGRAMS for the list of programs installed by findutils, which will create a stampfile for each through a new feature in host-build.mk. Signed-off-by: Michael Pratt <mcpratt@pm.me>
* host-build: add support for a stampfile per installed binaryMichael Pratt2023-06-05
| | | | | | | | | | | | | | Some individual build items install a group of programs instead of a program matching the name of the build item. Add support for installing stampfiles for each of the programs installed by that build item, which will allow more control and awareness of what is installed by the rest of the build system, if, for example, prereq symlink checks are looking for the same program which is built already. Signed-off-by: Michael Pratt <mcpratt@pm.me>
* prereq-build: replace relative symlinks only if brokenMichael Pratt2023-06-05
| | | | | | | | | | | | | | | | | | | | | | Some programs installed to staging_dir/host/bin also install some symlinks to itself for an alternative name. Some of those new symlinks are overwriting symlinks that were installed by prereq stage. If prereq stage were to somehow be run again, it should not be overwriting symlinks that point to programs that are already built. To filter that out, catch all symlinks after first catching all symlinks that have an absolute target after all other cases in the case statement, make sure it is not broken, and if so exit successfully. Suggested-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk> Signed-off-by: Michael Pratt <mcpratt@pm.me>
* prereq-build: do not replace binaries with symlinksMichael Pratt2023-06-05
| | | | | | | | | | | | | | | | Some programs, like bash and patch, are checked by prereq stage and have a symlink installed, but then is later built from source. Now that the prereq-build checks are not successful just by finding the file alone, it is possible for a new symlink to overwrite the installed binary. If a normal file is found in staging_dir/host/bin, let the check look for the associated stampfile, and if found, skip creation of a symlink and exit successfully. Suggested-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk> Signed-off-by: Michael Pratt <mcpratt@pm.me>
* Revert "prereq: SetupHostCommand: fix wrong check result"Michael Pratt2023-06-05
| | | | | | | | | | | | | | | | | | | | | | | | This reverts commit 7855378fcd7ed7cb0a223238a99bac0b8e46c380. The return "exit 1" was intentional and actually just makes the symlink checks much more strict. This new level of strictness added to the checks revealed what was a confusing regression with prereq stage that already existed but was not presenting itself because of the simple way that checks used to be done before. Either way, reverting to "exit 0" was a nice workaround until the true root cause was discovered, so as to not interfere with others' pull requests and builds in the meantime. It turns out that this problem was the inconsistent value of $PATH between different commands within the SetupHostCommand recipe, now fixed in the parent commit, using the variable created in the parent of the parent commit. Ref: f75204036c ("prereq-build: allow host command symlinks to update") Signed-off-by: Michael Pratt <mcpratt@pm.me>
* prereq-build: fix inconsistent value of $PATHMichael Pratt2023-06-05
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In the recipe SetupHostCommand for checking and creating symlinks, $PATH was only overridden for one of several commands. This causes the symlinks to be included in the paths to pick a program from when the check was repeated, because staging_dir/host/bin was included in $PATH, but only *sometimes*. When the check ran again, the command succeded with a $PATH including the symlink, (eval "$$$$$$$$cmd") while the path to the program was evaluated with a $PATH NOT including the symlink, (bin=...) causing the symlink to be relinked incorrectly, instead of passing as exactly the same. Coincidentally, this was only a problem if the symlink targeted the alternative program with a different name. By overriding the value of $PATH at the invocation of Make, it will apply to the entire environment of the checks. Signed-off-by: Michael Pratt <mcpratt@pm.me>
* treewide: add ORIG_PATH variableMichael Pratt2023-06-05
| | | | | | | | | | | | | Add a variable that stores the original value of $PATH in the host system's shell, before Make alters it. This can be useful for when it is necessary to ignore symlinks and programs made by the build system. Define this new variable before all instances of 'export PATH:=' or similar. Signed-off-by: Michael Pratt <mcpratt@pm.me>
* WIP: ipq-wifi: use my fork temporarily until upstreamedPetr Štetiar2023-06-05
| | | | Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ipq-wifi: add board files for prpl Foundation Haze boardPetr Štetiar2023-06-05
| | | | | | | | | | | | QSDK based factory firmware was setting following board_ids in DTS: ath11k_pci 0001:01:00.0: chip_id 0x0 chip_family 0x0 board_id 0xa4 soc_id 0xffffffff ath11k c000000.wifi1: chip_id 0x0 chip_family 0x0 board_id 0x294 soc_id 0xffffffff Thus board-prpl_haze.qcn9074` was extracted from `bus=...qmi-board-id=164.bin` file and `board-prpl_haze.ipq8074` from `bus=...qmi-board-id=660.bin` file. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ipq807x: add initial support for prpl Foundation Haze boardPetr Štetiar2023-06-05
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Haze is prpl Foundation's reference board (WNC LVRP). Board info: - IPQ8072A SoC - 2 GiB RAM - 4 GiB eMMC - 8MiB SPI NOR (MX25U6435F) - 3x 1GigE ports (QCA8075) - 1x 10GigE port (AQR113C) - 1x SFP cage - WiFi 6GHz 160MHz (QCN9074) - WiFi 5GHz 80+80MHz (QCN5054) - WiFi 2.4G (QCN5024) - ARM Standard 20-pin 2.54mm/0.1" JTAG (1V8 !!!) - Bluetooth v5.0 + EDR with integrated Class 1 PA (CYW20704) - 1x M.2 B-key socket with PCIe 3.0 - 1x USB 3.0 port - UART 4-pin 3V3(arrow),RX,TX,GND (115200 8N1) - Reset and WPS buttons Flashing instructions: 1. From U-Boot boot OpenWrt using initramfs image: IPQ807x# tftpboot openwrt-ipq807x-generic-prpl_haze-initramfs-uImage.itb && bootm 2. In OpenWrt running from initramfs execute sysupgrade: root@OpenWrt:/# sysupgrade -n /tmp/openwrt-ipq807x-generic-prpl_haze-squashfs-sysupgrade.bin Work in progress/known issues: * SFP feature not implemented/tested * M.2 feature not implemented/tested * Bluetooth feature not implemented/tested * 6GHz wireless should be working, but not tested * MAC address assigments for LAN interfaces Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ipq807x: image: factor out common eMMC bitsPetr Štetiar2023-06-05
| | | | | | For better maintainability and reusability. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ipq807x: image: cleanup unused variablesPetr Štetiar2023-06-05
| | | | | | | BLOCKSIZE and PAGESIZE seems to be unused on qnap_301w and zyxel_nbg7815 device which use eMMC storage. Signed-off-by: Petr Štetiar <ynezz@true.cz>