aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* x86/64: Add support for AMD SOC Ethernet controllerZheng Bao2021-04-172-1/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This feature is already supported in kernel. Add definition and configuration in Makefile of OpenWRT. It is tested on board Dibbler with processor V1605B. Dmesg is as below. -------------------------------------------- [ 0.317122] smpboot: CPU0: AMD Ryzen Embedded V1605B with Radeon Vega Gfx (family: 0x17, model: 0x11, stepping: 0x0) [ 8.227270] libphy: amd-xgbe-mii: probed [ 8.228189] amd-xgbe 0000:02:00.1 eth0: net device enabled [ 8.228999] libphy: amd-xgbe-mii: probed [ 8.229921] amd-xgbe 0000:02:00.2 eth1: net device enabled ..... [ 11.760869] br-lan: port 1(eth0) entered blocking state [ 11.761365] br-lan: port 1(eth0) entered disabled state [ 11.762019] device eth0 entered promiscuous mode [ 11.785285] 8021q: adding VLAN 0 to HW filter on device eth1 [ 16.881431] amd-xgbe 0000:02:00.1 eth0: Link is Up - 1Gbps/Full - flow control off [ 16.882108] br-lan: port 1(eth0) entered blocking state [ 16.882583] br-lan: port 1(eth0) entered forwarding state [ 16.883249] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready ----------------------------------------------- Signed-off-by: Zheng Bao <fishbaozi@gmail.com>
* ath79: mikrotik: update nand-rb4xx driverRoger Pueyo Centelles2021-04-174-12/+98
| | | | | | | | | | | | | | | This updates the NAND driver for MikroTik RB4XX series to work with kernel 5.10, similarly to the ar934x-nand driver (fb64e2c3). Support for kernel 5.10 was added to all ath79 subtargets except for the mikrotik one by commit d6b785d, since patch 920-mikrotik-rb4xx.patch needed to be reworked. Later, commit f8512661 enabled kernel 5.10 for the mikrotik subtarget with the nand-rb4xx driver still pending, which is updated and added back by this patch. Compile-tested only. Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>
* mvebu: Fix sysupgrade for GL.iNet GL-MV1000Sven Eckelmann2021-04-171-0/+3
| | | | | | | | | | | The GL.iNet GL-MV1000 is booting from eMMC and the images for it are in theory sysupgrade compatible. But the platform upgrade scripts were not adjusted to select the mmcblock device as upgrade target. This resulted in a failed sysupgrade because the mtd device (NOR flash) was instead tried to be modified by the sysupgrade script. Fixes: 050c24f05c85 ("mvebu: add support for GL.iNet GL-MV1000") Signed-off-by: Sven Eckelmann <sven@narfation.org>
* mvebu: armada 370: dts: fix the crypto engineDaniel González Cabanelas2021-04-172-0/+58
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The crypto engine in Armada 370 SoCs is currently broken. It can be checked installing the required packages for testing openssl with hw acceleration: opkg install openssl-util opkg install kmod-cryptodev opkg install libopenssl-devcrypto After configuring /etc/ssl/openssl.cnf to let openssl use the crypto engine for digest operations, and performing some checksums.. md5sum 10M-file.bin openssl md5 10M-file.bin ...we can see they don't match. There might be an alignment or size constraint issue caused by the idle-sram area. Use the whole crypto sram and disable the idle-sram area to fix it. Also disable the idle support by adding the broken-idle property to prevent accessing the disabled idle-sram. We don't care about disabling the idle support since it is already broken in Armada 370 causing a huge performance loss because it disables permanently the L2 cache. This was reported in the Openwrt forum and elsewhere by Debian users with different board models. Signed-off-by: Daniel González Cabanelas <dgcbueu@gmail.com>
* ramips: replace mt7621s hack with upstream patchIlya Lipnitskiy2021-04-174-68/+80
| | | | | | | | | | | | | | Refresh patches. Tested on a dual-core MT7621 device (Ubiquiti ER-X) and a single-core MT7621 device (Netgear R6220). This change will make future kernel upgrades easier (avoids conflicts with upstream). Link: https://lore.kernel.org/lkml/20210407200738.149207-1-ilya.lipnitskiy@gmail.com/ Signed-off-by: Ilya Lipnitskiy <ilya.lipnitskiy@gmail.com> Cc: Chuanhong Guo <gch981213@gmail.com>
* ramips: reduce spi-max-frequency for Xiaomi MI Router 4AGDavid Bentham2021-04-171-1/+1
| | | | | | | | | | | | | | | | | | | | | | | Reduce spi-max-frequency for Xiaomi MI Router 4AG model Xiaomi MI Router 4AG MTD uses two flash chips (no specific on router versions when produced from factory) - GD25Q128C and W25Q128BV. These flash chips are capable of high frequency, but due to poor board design or manufacture process. We are seeing the following errors in the linux kernel bootup: `spi-nor spi0.0: unrecognized JEDEC id bytes: cc 60 1c cc 60 1c spi-nor: probe of spi0.0 failed with error -2` This causes the partitions not to be detected `VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6` Then creates a bootloop and a bricked router. The solution to limit this race condition is to reduce the frequency from 80 mhz to 50 mhz. Signed-off-by: David Bentham <db260179@gmail.com>
* archs38: set device vendor and model variablesMoritz Warning2021-04-171-0/+2
| | | | | | This fixes the profiles.json output. Signed-off-by: Moritz Warning <moritzwarning@web.de>
* arc770: set device vendor and model variablesMoritz Warning2021-04-171-0/+2
| | | | | | This fixes the profiles.json output. Signed-off-by: Moritz Warning <moritzwarning@web.de>
* toolchain/gdb: fix compilation with ccacheRosen Penev2021-04-171-0/+1
| | | | | | | | | | For some reason, one of the configure checks results in some infinite loop and ends up spawning endless gcc processes, causing OOM. Just pass a configure var to avoid it. Same fix as 6e23813c1ed7494a9da3b5e59cfcafd71097c420 Signed-off-by: Rosen Penev <rosenp@gmail.com>
* kernel/modules: move act_gact into kmod-sched-coreDENG Qingfang2021-04-171-2/+2
| | | | | | | As the name suggests, act_gact has the generic actions such as dropping and accepting packets, so move it into kmod-sched-core. Signed-off-by: DENG Qingfang <dqfext@gmail.com>
* linux-firmware: ath10k: add support for Qualcomm Atheros QCA9377Josef Schlehofer2021-04-171-0/+17
| | | | | | | | | Add firmware and board file for Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) recognized as [168c:0042]. This card supports standard 1x1 802.11ac Wave2, BT5, and MU-MIMO. Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com>
* ltq-vdsl-app: extent dsl metrics with state_num and power_state_numFlorian Eckert2021-04-171-14/+58
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | With the old ubus dsl API, the numbers for the individual line_states and power_states were also returned. These were not ported to the new DSL C-API. This commit adds the missing information. For this the internal values are mapped to numbers. * additional JSON output for state_num: "state_num": <map_state_number> Since not all values are meaningful only the following values are implemented, this can be extended if the future. * LSTATE_MAP_NOT_INITIALIZED * LSTATE_MAP_EXCEPTION * LSTATE_MAP_IDLE * LSTATE_MAP_SILENT * LSTATE_MAP_HANDSHAKE * LSTATE_MAP_FULL_INIT * LSTATE_MAP_SHOWTIME_NO_SYNC * LSTATE_MAP_SHOWTIME_TC_SYNC * LSTATE_MAP_RESYNC * additinal JSON output for power_level: "power_state_num": <map_power_satte_number>, Since there are not so many here, all are mapped. * PSTATE_MAP_NA, * PSTATE_MAP_L0, * PSTATE_MAP_L1, * PSTATE_MAP_L2, * PSTATE_MAP_L3, Signed-off-by: Florian Eckert <fe@dev.tdt.de> v6: Add state LSTATE_MAP_NOT_INITILIZED at the beginning of the list Start the list LSTATE_MAP with -1 Reviewed-by: Andre Heider <a.heider@gmail.com>
* kernel: Disable IXP4xx physmap by defaultLinus Walleij2021-04-171-0/+1
| | | | | | | | This makes no sense on anything but the IXP4xx platform that we do not even support anymore. If we bring it back, it can be selectively enabled for that platform only. Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
* kernel: Disable CPU_THERMAL by defaultLinus Walleij2021-04-172-1/+1
| | | | | | | | | | | This config is for platforms that have: A) CONFIG_THERMAL set (we disable it by default) B) Has thermal zones that need to control cpufreq This is not suitable for default config, it needs to be enabled on a per-target basis in individual configs. Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
* kernel: Disable GPIO_CDEV_V1 by defaultLinus Walleij2021-04-171-0/+1
| | | | | | | | | We do not enable GPIO_CDEV so do not enable CDEV_V1 either. As we rebuild the whole userspace and kernel in OpenWRT it doesn't make any sense to support the old ABI anyway: the new one should be used by default. Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
* kernel: Disable CONFIG_DMA_PERNUMA_CMA by defaultLinus Walleij2021-04-173-2/+1
| | | | | | | | | | | This CMA memory allocation option only applies to NUMA (Non-Uniform Memory Access) systems which are seldom the kind of systems that OpenWRT address. It is safe to assume that any system that need this option would turn it on locally. Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
* kernel: Remove dead scheduler optionsLinus Walleij2021-04-171-4/+0
| | | | | | | | | The non-MQ CFQ, deadline and noop IO schedulers are deleted from the Linux kernel since commit f382fb0bcef4c37dc049e9f6963e3baf204d815c "block: remove legacy IO schedulers". Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
* kernel: bump 5.4 to 5.4.113John Audia2021-04-172-5/+5
| | | | | | | | | | | | | Ran update_kernel.sh in a fresh clone without any existing toolchains. No manual intervention needed. Build system: x86_64 Build-tested: ipq806x/R7800 Run-tested: ipq806x/R7800 No dmesg regressions, everything functional Signed-off-by: John Audia <graysky@archlinux.us>
* kernel: bump 5.4 to 5.4.112John Audia2021-04-1710-383/+220
| | | | | | | | | | | | | | | Ran update_kernel.sh in a fresh clone without any existing toolchains. Removed upstreamed: mvebu/patches-5.4/319-ARM-dts-turris-omnia-configure-LED-2--INTn-pin-as-interrupt-pin.patch Build system : x86_64 Build-tested : ipq806x/R7800 Run-tested : ipq806x/R7800 No dmesg regressions, everything functional Signed-off-by: John Audia <graysky@archlinux.us>
* kernel: bump 5.4 to 5.4.111John Audia2021-04-174-5/+5
| | | | | | | | | | | | Refreshed with update_kernel.sh. No manual tweaks needed. Build system: x86_64 Build-tested: ipq806x/R7800 Run-tested: ipq806x/R7800 No dmesg regressions, everything functional Signed-off-by: John Audia <graysky@archlinux.us>
* kernel: bump 5.10 to 5.10.31Rui Salvaterra2021-04-172-5/+5
| | | | | | | Automatically refreshed: ramips/patches-5.10/710-at803x.patch Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com>
* glibc: update to latest 2.33 commitHans Dedecker2021-04-171-2/+2
| | | | | | | | | | | | | | | | | | | 12ff80b312 Remove PR_TAGGED_ADDR_ENABLE from sys/prctl.h 1bf38e7260 Fix SXID_ERASE behavior in setuid programs (BZ #27471) a7b8e8ec9b Enhance setuid-tunables test ee16c81063 tst-env-setuid: Use support_capture_subprogram_self_sgid 267e174f19 support: Add capability to fork an sgid child 249c486ce8 support: Pass environ to child process 45b2c57d34 support: Typo and formatting fixes e07abf59b2 tunables: Fix comparison of tunable values 3e9ca60a58 linux: always update select timeout (BZ #27706) 8380ca5833 linux: Normalize and return timeout on select (BZ #27651) 85e4dc415a libsupport: Add support_select_normalizes_timeout b5b4aa62c1 libsupport: Add support_select_modifies_timeout 3d525dd639 misc: Fix tst-select timeout handling (BZ#27648) 830674605f tst: Provide test for select Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* odhcp6c: read user scripts from directoryLeon M. George2021-04-172-2/+6
| | | | | | | | | | | | | | Placeholder DHCP user scripts were added recently. These files make package-based installations of such scripts more difficult. Pull user callbacks from directories instead to allow packages and users to install co-existing scripts more easily. References: b4f3d93b5 odhcp6c: add a odhcp6c.user placeholder script Signed-off-by: Leon M. George <leon@georgemail.eu> Signed-off-by: Hans Dedecker <dedeckeh@gmail.com> [PKG_RELEASE increase]
* netifd: read udhcpc user scripts from directoryLeon M. George2021-04-172-1/+6
| | | | | | | | | | | | | | Placeholder DHCP user scripts were added recently. These files make package-based installations of such scripts more difficult. Pull user callbacks from directories instead to allow packages and users to install co-existing scripts more easily. References: 130118f7a netifd: add a udhcpc.user placeholder script Signed-off-by: Leon M. George <leon@georgemail.eu> Signed-off-by: Hans Dedecker <dedeckeh@gmail.com> [PKG_RELEASE increase]
* ath79: update spi-nor patchesDavid Bauer2021-04-163-111/+38
| | | | | | | Update the 4 bit BP patches for Ubiquiti boards with the second iteration sent upstream. Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: remove unused patchDavid Bauer2021-04-161-21/+0
| | | | | | | | | | | This patch ist not required, as it only has an effect in case the GPIO descriptors supplied to num-cs are valid. As this is not the case for ath79, this patch can safely be omitted. The issue it tried to fix is actually fixed with 0054-spi-sync-up-initial-chipselect-state. Signed-off-by: David Bauer <mail@david-bauer.net>
* mediatek: fix Ubiquiti UniFi 6 LR LEDDavid Bauer2021-04-162-0/+215
| | | | | | | | | | When adding Kernel 5.10 support, the kernel configuration did not include the LED driver required for the UniFi 6 LR. Also the actual driver source went missing. Fixes commit c46ccb69d17e ("mediatek: mt7622: add Linux 5.10 support") Signed-off-by: David Bauer <mail@david-bauer.net>
* kernel: bump 5.10 to 5.10.30Rui Salvaterra2021-04-1614-87/+23
| | | | | | | | | | | | | | | | | | | | | Deleted (reverse-applicable): mvebu/patches-5.10/101-ARM-dts-turris-omnia-configure-LED-2--INTn-pin-as-interrupt-pin.patch Automatically refreshed: bcm63xx/patches-5.10/143-gpio-fix-device-tree-gpio-hogs-on-dual-role-gpio-pin.patch generic/backport-5.10/610-v5.13-02-netfilter-Fix-fall-through-warnings-for-Clang.patch generic/backport-5.10/610-v5.13-10-netfilter-nftables-update-table-flags-from-the-commi.patch generic/hack-5.10/204-module_strip.patch generic/hack-5.10/902-debloat_proc.patch generic/pending-5.10/203-kallsyms_uncompressed.patch generic/pending-5.10/670-ipv6-allow-rejecting-with-source-address-failed-policy.patch generic/pending-5.10/920-mangle_bootargs.patch mediatek/patches-5.10/115-dts-bpi64-add-snand-support.patch mediatek/patches-5.10/602-arm64-dts-mediatek-Split-PCIe-node-for-MT2712-MT7622.patch mediatek/patches-5.10/900-dts-mt7622-bpi-r64-aliases-for-dtoverlay.patch ramips/patches-5.10/323-mt7621-memory-detect.patch Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com>
* ath79: mikrotik: enable SFP on RB922UAGS-5HPaCDRoger Pueyo Centelles2021-04-164-2/+51
| | | | | | | | | | | | | | | | This patch enables the SFP cage on the MikroTik RouterBOARD 922UAGS-5HPacD. GPIO16 (tx-disable-gpios) should be governed by the SFP driver to enable or disable transmission, but no change is observed. Therefore, it is left as output high to ensure the SFP module is forced to transmit. Tested on a RouterBOARD 922UAGS-5HPacD board, with a CISCO GLC-LH-SMD 1310nm module and an unbranded GLC-T RJ45 Gigabit module. PC=>router iperf3 tests deliver 440/300 Mbps up/down, both via regular eth0 port or SFP port with RJ45 module. Bridge between eth0 and eth1 delivers 950 Mbps symmetric. Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>
* gemini,layerscape,oxnas: don't disable option CONFIG_BPF_SYSCALLTony Ambardar2021-04-165-5/+0
| | | | | | | | Respect the generic kernel config setting, which is "enabled" tree-wide, as previously done for sunxi. Ref: 247ef4d98bab ("sunxi: enable CONFIG_BPF_SYSCALL and CONFIG_EMBEDDED") Signed-off-by: Tony Ambardar <itugrok@yahoo.com>
* ath79: fix 10 Mbit PLL data for TP-Link EAP2xxDavid Bauer2021-04-151-0/+1
| | | | | | | | | | | Fix the PLL register value for 10 Mbit/s link modes on TP-Link EAP boards using a AR8033 SGMII PHY. Otherwise, 10 Mbit/s links do not transfer data. Reported-by: Tom Herbers <freifunk@tomherbers.de> Tested-by: Tom Herbers <freifunk@tomherbers.de> Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: fix 10 Mbit PLL data for UniFi ACDavid Bauer2021-04-151-0/+2
| | | | | | | Fix the PLL register value for 10 Mbit/s link modes on the UniFi AC Lite / Mesh / LR. Otherwise, 10 Mbit/s links do not transfer data. Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: fix link mode support list on UniFi ACDavid Bauer2021-04-152-0/+72
| | | | | | | | | | | | | | | | | | | | This fixes incorrect supported link modes indicated when using ethtool on the Ubiquiti UniFi AC lite / LR / Mesh. eroot@OpenWrt:~# ethtool eth0 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 100baseT/Half 100baseT/Full 1000baseT/Full 1000baseX/Full The reason for this is, that since kernel 5.4 the PHY capabilities are read dynamically from the PHY. As Ubiquiti leaves the PHY in a wrong state, the capabilities of the SGMII side of the PHY are read. As a side effect, 10 Mbit/s link modes did not work on these boards. Signed-off-by: David Bauer <mail@david-bauer.net>
* ramips/mediatek: import a patch fixing bug in flow-offloadingDaniel Golle2021-04-151-0/+24
| | | | | | | | | | | From Frank Wunderlich <frank-w@public-files.de>: Issue were traffic problems after a while with increased ping times if flow offload is active. It turns out that key_offset with cookie is needed in rhashtable_params and head_offset was defined twice. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* libsemanage: fix pkgconfig pathsRosen Penev2021-04-151-1/+3
| | | | | | The pkgconfig file currently points to host paths. Signed-off-by: Rosen Penev <rosenp@gmail.com>
* uboot-sunxi: update ATF dependencies for 3 boardsZoltan HERPAI2021-04-151-3/+3
| | | | | | | Fix 3 board definitions that were missed in the process of moving to the a64/h6 ATF blobs. Signed-off-by: Zoltan HERPAI <wigyori@uid0.hu>
* ramips: gpio-ralink: use ngpios, not ralink,num-gpiosIlya Lipnitskiy2021-04-1513-29/+51
| | | | | | | | | | | | | | | | DTS properties that match *-gpios are treated specially. Use ngpios instead, as most GPIO drivers upstream do. Fixes 5.10 DTS errors such as: OF: /palmbus@300000/gpio@600: could not find phandle Fixes DTC warnings such as: Warning (gpios_property): /palmbus@300000/gpio@600:ralink,num-gpios: Could not get phandle node for (cell 0) Signed-off-by: Ilya Lipnitskiy <ilya.lipnitskiy@gmail.com> Cc: Daniel Golle <daniel@makrotopia.org>
* ramips: rt288x: replace hack with a kconfig changeIlya Lipnitskiy2021-04-152-45/+32
| | | | | | | | | Use an existing kernel config symbol to fix devices whose ramstart is not zero. See upstream patch message for more details. Signed-off-by: Ilya Lipnitskiy <ilya.lipnitskiy@gmail.com> Cc: Tobias Wolf <dev-NTEO@vplace.de> Cc: Daniel Golle <daniel@makrotopia.org>
* ramips: mt7530 swconfig: fix race condition in register accessDENG Qingfang2021-04-151-6/+10
| | | | | | | | | | | | | | | | The mt7530_{r,w}32 operation over MDIO uses 3 mdiobus operations and does not hold a lock, which causes a race condition when multiple threads try to access a register, they may get unexpected results. To avoid this, handle the MDIO lock manually, and use the unlocked __mdiobus_{read,write} in the critical section. This fixes the "Ghost VLAN" artifact[1] in MT7530/7621 when the VLAN operation and the swconfig LED link status poll race between each other. [1] https://forum.openwrt.org/t/mysterious-vlan-ids-on-mt7621-device/64495 Signed-off-by: DENG Qingfang <dqfext@gmail.com>
* ramips: drop obsolete arcs_cmdline override patchIlya Lipnitskiy2021-04-151-21/+0
| | | | | | | | CONFIG_MIPS_CMDLINE_FROM_DTB is set to 'y' for all ramips targets already, which will ensure that the value of 'bootargs' will take precedence over whatever is in arcs_cmdline. Signed-off-by: Ilya Lipnitskiy <ilya.lipnitskiy@gmail.com>
* firmware-utils: tplink-safeloader: support displaying fw infoRafał Miłecki2021-04-141-4/+127
| | | | | | | | | | Add "-i" option for reading & displaying firmware info. First it lists in-firmware partitions ("fwup-ptn"). Then it checks for human understandable partitions and prints data found in each of them. This new feature is meant for development & debug purposes. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* uci: update to the latest masterRafał Miłecki2021-04-141-3/+3
| | | | | | 4b3db11 cli: add option for changing save path Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm53xx: add pending TRX patch for "firmware" partitionRafał Miłecki2021-04-141-0/+43
| | | | | | | This fixes partitioning on Linksys EA9500. With this change only the currently used firmware MTD partition gets parsed. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* kernel: limit crypto-hw-ccp to the x86Rafał Miłecki2021-04-131-0/+1
| | | | | | | | | | | | | | CRYPTO_DEV_CCP depends on X86 or ARM64 CRYPTO_DEV_CCP_DD depends on CPU_SUP_AMD or ARM64 Compiling this driver makes sense for x86 mainly. If one day support for ARM64 board with AMD Secure Processor gets added this package may be updated. Trying to build this package on bcm4908 was causing: ERROR: module 'build_dir/target-aarch64_cortex-a53_musl/linux-bcm4908_generic/linux-5.4.110/drivers/crypto/ccp/ccp-crypto.ko' is missing. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* kernel: crypto: format "crypto-hw-ccp" dependenciesRafał Miłecki2021-04-131-1/+8
| | | | | | | Use multiples lines for better readability and sort lines. Suggested-by: Stijn Tintel <stijn@linux-ipv6.be> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* firmware-utils: mkmylofw: fix blocks paddingRafał Miłecki2021-04-131-1/+1
| | | | | | | | | | | | | | | The old code didn't make sense as it was using "len" variable which was guaranteed to be always 0. Loop right above broken code is: while (len > 0) { } With this recent ALIGN macro fix this resulted in subtracting block size from 0 and calling write_out_padding() with a negative length. To calculate amount of bytes needed for padding & alignment it should be enough to use % 4. Fixes: a2f66229450d ("firmware-utils: fix few random warnings") Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* firmware-utils: zyimage: drop POSIX SOURCE definesRafał Miłecki2021-04-131-2/+0
| | | | | | | | | | This fixes: src/zyimage.c:10:0: warning: "_POSIX_SOURCE" redefined src/zyimage.c:11:0: warning: "_POSIX_C_SOURCE" redefined This change has been tested on Linux with -Wextra and on Mac OS. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* tplink-safeloader: fix C7v5 factory flashing from vendor fw > v1.1.xPetr Štetiar2021-04-131-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently it's not possible to flash factory images on devices shipped with vendor firmware versions 1.1.0 Build 20201120 rel. 50406 (published 2020-12-22): (curFw_ver, newFw_ver) == (1.1, 1.0) [NM_Error](nm_checkSoftVer) 00848: Firmwave not supports, check failed. [NM_Error](nm_checkUpdateContent) 01084: software version dismatched [NM_Error](nm_buildUpgradeStruct) 01188: checkUpdateContent failed. They've even following note in release notes: Note: You will be unable to downgrade to the previous firmware version after updating this firmware. This version check in vendor firmware is implemented in /usr/bin/nvrammanager binary likely as following C code[1]: sscanf(buf, "%d.%d.%*s",&upd_fw_major, &upd_fw_minor); ... if (((int)upd_fw_major < (int)cur_fw_major) || ((ret = 1, cur_fw_major == upd_fw_major && (upd_fw_minor < (int)cur_fw_minor)))) { ret = 0; printf("[NM_Error](%s) %05d: Firmwave not supports, check failed.\r\n\r\n","nm_checkSoftVer" ,0x350); } ... return ret; So in order to fix this and make it future proof it should be enough to ship our factory firmware images with major version 7 (lucky number). Tested on latest firmware version 1.1.2 Build 20210125 rel.37999: Firmwave supports, check OK. (curFw_ver, newFw_ver) == (1.1, 7.0) check firmware ok! Flashing back to vendor firmware c7v5_us-up-ver1-1-2-P1[20210125-rel37999]_2021-01-25_10.33.55.bin works as well: U-Boot 1.1.4-gbec22107-dirty (Nov 18 2020 - 18:19:12) ... Firmware downloaded... filesize = 0xeeae77 fileaddr = 0x80060000. Firmware Recovery file length : 15642231 Firmware process id 2. handle_fw_cloud 146 Image verify OK! Firmware file Verify ok! product-info:product_name:Archer C7 product_ver:5.0.0 special_id:55530000 [Error]sysmgr_cfg_checkSupportList(): 1023 @ specialId 45550000 NOT Match. Firmware supports, check OK. Firmware Recovery check ok! 1. https://gist.github.com/ynezz/2e0583647d863386a66c3d231541b6d1 Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ath79: add missing patch for kernel 5.10David Bauer2021-04-131-0/+9
| | | | | | | | | When adding the patch for the missing register, the patch file for the testing kernel 5.10 was not included. Fixes commit fbbad9a9a629 ("ath79: force SGMII SerDes mode to MAC operation") Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: force SGMII SerDes mode to MAC operationDavid Bauer2021-04-132-0/+14
| | | | | | | | | | | | | | | | | The mode on the SGMII SerDes on the QCA9563 is 1000 Base-X by default. This only allows for 1000 Mbit/s links, however when used with an SGMII PHY in 100 Mbit/s link mode, the link remains dead. This strictly has nothing to do with the SerDes calibration, however it is done at the same point in the QCA reference U-Boot which is the blueprint for everything happening here. As the current state is more or less a hack, this should be fine. This fixes the issues outlined above on a TP-Link EAP-225 Outdoor. Reported-by: Tom Herbers <freifunk@tomherbers.de> Tested-by: Tom Herbers <freifunk@tomherbers.de> Signed-off-by: David Bauer <mail@david-bauer.net>
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-28 20:34:50 +0000