aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* bmips: add support for Comtrend VR-3025unÁlvaro Fernández Rojas2023-06-11
| | | | | | | | | | | | | | | | | | | | | | | | | | The Comtrend VR-3025un is a wifi gigabit router, 2.4 GHz single band with two external antennas. Hardware: - SoC: Broadcom BCM6368 - CPU: dual core BMIPS4350 @ 400Mhz - RAM: 64 MB DDR - Flash: 8 MB parallel NOR - Ethernet LAN: 4x 100Mbit - Wifi 2.4 GHz: miniPCI Broadcom BCM43222 802.11bgn - USB: 1x 2.0 - Buttons: 1x (reset) - LEDs: yes - UART: yes Installation via CFE web UI: 1. Power off the router. 2. Press reset button near the antenna. 3. Keep it pressed while powering up during ~20+ seconds. 4. Browse to http://192.168.1.1 and upload the firmware. 5. Wait a few minutes for it to finish. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* swconfig: fix memory leak when cli call swlib_get_attr()nichel Chen2023-06-11
| | | | | | | The cli is a one-time run, and memory leaks would have been irrelevant. But people call libsw with cli programs as samples. Doing a good job of memory management calls means that people who call libsw are not so easy to make mistakes. Signed-off-by: nichel Chen <nichelnich@gmail.com>
* bmips: dgnd3700v1/dgnd3800b: add missing kmod-leds-gpioÁlvaro Fernández Rojas2023-06-11
| | | | | | | Commit ed79519b8d89 missed adding kmod-leds-gpio to these devices. Fixes: ed79519b8d89 ("bmips: add support for Netgear DGND3700 v1, DGND3800B") Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bmips: image: rename Device/bcm63xx_netgearÁlvaro Fernández Rojas2023-06-11
| | | | | | | Every other Device definition in the target is using hyphens instead of underscores. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bmips: dts: improve and align device tree filesÁlvaro Fernández Rojas2023-06-11
| | | | | | | Align all the device tree files and follow the same criteria before more devices are ported from bcm63xx and this goes out of control. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bmips: add support for Netgear EVG2000Daniel González Cabanelas2023-06-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | The Netgear EVG2000 is a wifi gigabit router, 2.4 GHz single band with two internal antennas integrated in the main PCB. Hardware: - SoC: Broadcom BCM6369 - CPU: dual core BMIPS4350 V3.1 @400Mhz - RAM: 64 MB DDR - Flash: 16 MB parallel NOR - LAN switch: Broadcom BCM53115, 5x 1Gbit - Wifi 2.4 GHz: Broadcom BCM4322 802.11bgn - USB: 2x 2.0 - Buttons: 2x, 1 reset - LEDs: 10x - FXS: 2x - UART: yes Installation via CFE web UI: 1. Power off the router and make a temporal TX-RX shortcircuit on the serial pins. 2. Power on the router and wait 3 or more seconds 3. Remove the TX-RX shortcircuit 4. Browse to http://192.168.1.1 or http://192.168.0.1 and upload the firmware 5. Wait a few minutes for it to finish Signed-off-by: Daniel González Cabanelas <dgcbueu@gmail.com>
* ramips: Add support for Beeline SmartBox TURBO+Maximilian Weinmann2023-06-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds support for Beeline Smart Box TURBO+ (Serсomm S3 CQR) router. Device specification -------------------- SoC Type: MediaTek MT7621AT (880 MHz, 2 cores) RAM (Nanya NT5CC64M16GP): 128 MiB Flash (Macronix MX30LF1G18AC): 128 MiB Wireless 2.4 GHz (MT7603EN): b/g/n, 2x2 Wireless 5 GHz (MT7615N): a/n/ac, 4x4 Ethernet: 5 ports - 5×GbE (WAN, LAN1-4) USB ports: 1xUSB3.0 Buttons: 2 button (reset, wps) LEDs: Red, Green, Blue Zigbee (EFR32MG1B232GG): 3.0 Stock bootloader: U-Boot 1.1.3 Power: 12 VDC, 1.5 A Installation (fw 2.0.9) ----------------------- 1. Login to the web interface under SuperUser (root) credentials. Password: SDXXXXXXXXXX, where SDXXXXXXXXXX is serial number of the device written on the backplate stick. 2. Navigate to Setting -> WAN. Add: Name - WAN1 Connection Type - Static IP Address - 172.16.0.1 Netmask - 255.255.255.0 Save -> Apply. Set default: WAN1 3. Enable SSH and HTTP on WAN. Setting -> Remote control. Add: Protocol - SSH Port - 22 IP Address - 172.16.0.1 Netmask - 255.255.255.0 WAN Interface - WAN1 Save ->Apply Add: Protocol - HTTP Port - 80 IP Address - 172.16.0.1 Netmask - 255.255.255.0 WAN interface - WAN1 Save -> Apply 4. Set up your PC ethernet: Connection Type - Static IP Address - 172.16.0.2 Netmask - 255.255.255.0 Gateway - 172.16.0.1 5. Connect PC using ethernet cable to the WAN port of the router 6. Connect to the router using SSH shell under SuperUser account 7. Make a mtd backup (optional, see related section) 8. Change bootflag to Sercomm1 and reboot: printf 1 | dd bs=1 seek=7 count=1 of=/dev/mtdblock3 reboot 9. Login to the router web interface under admin account 10. Remove dots from the OpenWrt factory image filename 11. Update firmware via web using OpenWrt factory image Revert to stock --------------- Change bootflag to Sercomm1 in OpenWrt CLI and then reboot: printf 1 | dd bs=1 seek=7 count=1 of=/dev/mtdblock3 mtd backup ---------- 1. Set up a tftp server (e.g. tftpd64 for windows) 2. Connect to a router using SSH shell and run the following commands: cd /tmp for i in 0 1 2 3 4 5 6 7 8 9 10; do nanddump -f mtd$i /dev/mtd$i; \ tftp -l mtd$i -p 172.16.0.2; md5sum mtd$i >> mtd.md5; rm mtd$i; done tftp -l mtd.md5 -p 171.16.0.2 Recovery -------- Use sercomm-recovery tool. Link: https://github.com/danitool/sercomm-recovery MAC Addresses (fw 2.0.9) ------------------------ +-----+------------+---------+ | use | address | example | +-----+------------+---------+ | LAN | label | *:e8 | | WAN | label + 1 | *:e9 | | 2g | label + 4 | *:ec | | 5g | label + 5 | *:ed | +-----+------------+---------+ The label MAC address was found in Factory 0x21000 Factory image format -------------------- +---+-------------------+-------------+--------------------+ | # | Offset | Size | Description | +---+-------------------+-------------+--------------------+ | 1 | 0x0 | 0x200 | Tag Header Factory | | 2 | 0x200 | 0x100 | Tag Header Kernel1 | | 3 | 0x300 | 0x100 | Tag Header Kernel2 | | 4 | 0x400 | SIZE_KERNEL | Kernel | | 5 | 0x400+SIZE_KERNEL | SIZE_ROOTFS | RootFS(UBI) | +---+-------------------+-------------+--------------------+ Co-authored-by: Mikhail Zhilkin <csharper2005@gmail.com> Signed-off-by: Maximilian Weinmann <x1@disroot.org>
* scripts: sercomm-kernel-header.py: improve compatibilityMikhail Zhilkin2023-06-11
| | | | | | | | | | | | | This improves compatibility with the elder stock firmwares of the following devices, which have not yet been merged into OpenWrt: - Beeline SmartBox Pro - Beeline SmartBox Turbo+ - WiFire S1500.NBN Without this, OpenWrt factory image installation may fail. Signed-off-by: Mikhail Zhilkin <csharper2005@gmail.com> Signed-off-by: Maximilian Weinmann <x1@disroot.org>
* uboot-armsr: add support for QEMU armv7/armv8Petr Štetiar2023-06-10
| | | | | | | | | | | Add new package so we can use self-compiled bootloader during QEMU based testing and development. Backported fix[1] is needed for EFI boot from virtio devices. 1. https://patchwork.ozlabs.org/project/uboot/patch/20230424134946.v10.7.Ia5f5e39c882ac22b5f71c4d576941b34e868eeba@changeid/ Signed-off-by: Petr Štetiar <ynezz@true.cz>
* u-boot.mk: add support for config customizationPetr Štetiar2023-06-10
| | | | | | | | | | | | | | | | | | | | | Make it possible to easily customize U-Boot config options via new `UBOOT_CUSTOMIZE_CONFIG` variable, so we don't need to patch config files or override config step with shell hackery. This generic approach uses `config` CLI to tweak the .config as needed, for example: UBOOT_CUSTOMIZE_CONFIG := \ --enable CMD_EFIDEBUG \ --enable CMD_BOOTMENU \ --enable AUTOBOOT \ --enable AUTOBOOT_MENU_SHOW \ --disable AUTOBOOT_KEYED \ --disable AUTOBOOT_USE_MENUKEY \ --disable BOOTMENU_DISABLE_UBOOT_CONSOLE \ --set-val BOOTDELAY 2 Signed-off-by: Petr Štetiar <ynezz@true.cz>
* CI: change armvirt reference to armsrMathew McBride2023-06-10
| | | | | | The armvirt target has been renamed to armsr. Signed-off-by: Mathew McBride <matt@traverse.com.au>
* scripts: qemustart: change armvirt references to armsrMathew McBride2023-06-10
| | | | | | | | The armvirt target has been renamed to 'armsr' (Arm SystemReady) after inclusion of EFI support. Change references (including subtargets) accordingly. Signed-off-by: Mathew McBride <matt@traverse.com.au>
* wolfssl: change armvirt reference to armsrMathew McBride2023-06-10
| | | | | | armvirt target has been renamed to armsr (Arm SystemReady). Signed-off-by: Mathew McBride <matt@traverse.com.au>
* kernel: netdevices: change armvirt references to armsrMathew McBride2023-06-10
| | | | | | armvirt target has been renamed to armsr (Arm SystemReady) Signed-off-by: Mathew McBride <matt@traverse.com.au>
* grub2: change armvirt reference to armsrMathew McBride2023-06-10
| | | | | | | The armvirt target has been renamed to armsr (Arm SystemReady), so the GRUB configuration also needs to change. Signed-off-by: Mathew McBride <matt@traverse.com.au>
* config: change references from armvirt to armsrMathew McBride2023-06-10
| | | | | | | armvirt target has been renamed to armsr (Arm SystemReady), so the config defaults need to be changed as well. Signed-off-by: Mathew McBride <matt@traverse.com.au>
* armsr: rename from armvirtMathew McBride2023-06-10
| | | | | | | | | | | | | | | | | | Now that the armvirt target supports real hardware, not just VMs, thanks to the addition of EFI, rename it to something more appropriate. 'armsr' (Arm SystemReady) was chosen after the name of the Arm standards program. The 32 and 64 bit targets have also been renamed armv7 and armv8 respectively, to allow future profiles where required (such as armv9). See https://developer.arm.com/documentation/102858/0100/Introduction for more information. Signed-off-by: Mathew McBride <matt@traverse.com.au>
* armvirt: remove 5.15 configsMathew McBride2023-06-10
| | | | | | | | | | | armvirt was migrated to 6.1 as part of the EFI implementation. As we are renaming the target, there is no need to take the old kernel configs with us. See abcb30d ("armvirt: switch to kernel 6.1") for the previous change. Signed-off-by: Mathew McBride <matt@traverse.com.au>
* ipq807x: image: fix eMMC flashing/recovery from within initramfsPetr Štetiar2023-06-10
| | | | | | | | | | | | | | | | | | | | | Having initramfs image built with same config as on buildbots: CONFIG_TARGET_MULTI_PROFILE=y CONFIG_TARGET_ALL_PROFILES=y CONFIG_TARGET_PER_DEVICE_ROOTFS=y Its currently impossible to flash/recover the device using that image as losetup is missing: root@OpenWrt:/# sysupgrade -v /tmp/openwrt-ipq807x-generic-prpl_haze-squashfs-sysupgrade.bin ... /lib/upgrade/do_stage2: line 38: losetup: not found Failed to detach all loop devices. Skip this try. So lets fix it by including the needed utils for sysupgrade in DEFAULT_PACKAGES set. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ipq807x: add initial support for prpl Foundation Haze boardPetr Štetiar2023-06-10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 marked J6 is 4-pin 2.54mm/0.1" connector 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>
* ipq-wifi: update to version 2023-06-03Petr Štetiar2023-06-10
| | | | | | | | | | | | | Contains following updates: * ipq8074: update RegDB in new submitted BDF * Revert "ipq8074: update RegDB in new submitted BDF" * qcn9074: update RegDB in new submitted BDF * ipq8074: update RegDB in new submitted BDF * qca-wireless: ipq40xx: add BDFs for ZTE MF287+ * Add BDFs for prpl Foundation Haze board Signed-off-by: Petr Štetiar <ynezz@true.cz>
* kernel: qca-ssdk: renumber patchesRobert Marko2023-06-10
| | | | | | Lets reexport the patches in order to have them renumbered from 0 again. Signed-off-by: Robert Marko <robimarko@gmail.com>
* kernel: qca-ssdk: drop 5.15 supportRobert Marko2023-06-10
| | | | | | | There is no need for SSDK to support 5.15 anymore since the only user and possible future ones are on 6.1. Signed-off-by: Robert Marko <robimarko@gmail.com>
* mpc85xx: 5.15: refresh kernel patchesChristian Marangi2023-06-10
| | | | | | Refresh kernel patches for 5.15 kernel version for mpc85xx. Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* generic: 5.15: refresh patchesChristian Marangi2023-06-10
| | | | | | Refresh kernel patches for generic 5.15 kernel version. Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* generic: 5.15: backport patch supporting "big" kernel symbolsChristian Marangi2023-06-10
| | | | | | | | | | | | Backport patch supporting "big" kernel symbols. This is needed for powerpc arch that seems to suffer from this problem when CONFIG_ALL_KMODS is selected and fail to compile with the error: Inconsistent kallsyms data Try make KALLSYMS_EXTRA_PASS=1 as a workaround Backport this patch to handle these corner case. Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* generic: backport PPC boot wrapper VDSO executable stack fixChristian Marangi2023-06-10
| | | | | | | | | | | | Backport upstream fix for PowerPC that fix VDSO executable stack warning for the boot wrapper. Fix the compilation error: powerpc-openwrt-linux-musl-ld.bin: warning: div64.o: missing .note.GNU-stack section implies executable stack powerpc-openwrt-linux-musl-ld.bin: NOTE: This behaviour is deprecated and will be removed in a future version of the linker powerpc-openwrt-linux-musl-ld.bin: warning: arch/powerpc/boot/simpleImage.ws-ap3825i has a LOAD segment with RWX permissions Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* bmips: add support for Netgear DGND3700 v1, DGND3800BDaniel González Cabanelas2023-06-10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The Netgear DGND3700 v1 and DGND3800B are the same device but with different factory firmwares. It's an xDSL wifi router with a slim black shiny casing and 4 PCB internal antennas connected via UFL to a miniPCI detachable card. Hardware: - SoC: Broadcom BCM6368 - CPU: dual core BMIPS4350 V3.1 @400Mhz - RAM: 128 MB DDR - NOR Flash: 32 MB parallel (CFE and OS) - NAND flash: 128 MB (empty) - Ethernet LAN: 5x 1Gbit - Wifi 2.4 GHz: Broadcom BCM43222 802.11bgn - Wifi 5 GHz: Broadcom BCM43222 802.11abgn - USB: 2x 2.0 - Buttons: 3x, 1 reset - LEDs: 11x - UART: yes Installation via OEM web UI: 1. Open the Netgear administration web interface, by default: http://192.168.0.1 user: admin password: password 2. Look for "upgrade firmware" and proceed 3. Wait some minutes until it finishes Signed-off-by: Daniel González Cabanelas <dgcbueu@gmail.com>
* lantiq: replace random_ether_addr with eth_random_addrAleksander Jan Bajkowski2023-06-10
| | | | | | | | | | | Random_ether_addr() is a helper function which was kept for backward compatibility. It is available in the kernel from version 3.6 to 5.16. In newer kernel verions, it has been completely replaced by eth_random_addr(). There should be no functional changes. Ref: https://github.com/torvalds/linux/commit/ba530fea8ca1b57ee71d4e62f287a5d7ed92f789 Signed-off-by: Aleksander Jan Bajkowski <olek2@wp.pl>
* uboot-envtools: Add u-boot env config for GL-MT3000Jianhui Zhao2023-06-09
| | | | | | | | This commit add u-boot env config for GL-MT3000, so that we can use fw_printenv to print u-boot env and use fw_setenv to set u-boot env in GL-MT3000. Signed-off-by: Jianhui Zhao <zhaojh329@gmail.com>
* ramips: fix first boot network configuration for TOZED ZLT S12 PROArınç ÜNAL2023-06-09
| | | | | | | | | | | The network configuration at first boot for TOZED ZLT S12 PRO lacks setting up the LAN and WAN network interfaces. Address this. The WAN port is advertised as WAN/LAN on the device and is put on LAN on stock firmware so put it on LAN here as well. Fixes: ce1f9fa625 ("ramips: add support for TOZED ZLT S12 PRO") Reported-by: Andre Cruz <me@1conan.com> Signed-off-by: Arınç ÜNAL <arinc.unal@arinc9.com>
* kernel: modules: fix mdio-bus-mux descriptionLuiz Angelo Daros de Luca2023-06-09
| | | | | | | Simple error during copy/paste Fixes: 2dbeb607251b ("kernel: add mdio-bus-mux support") Signed-off-by: Luiz Angelo Daros de Luca <luizluca@gmail.com>
* ramips: fix button definitions for Zyxel WSM20Thomas Schröder2023-06-09
| | | | | | | | Setting the events of the WPS and LED buttons to the best matching values based from the documentation: <https://openwrt.org/docs/guide-user/hardware/hardware.button#procd_buttons> Signed-off-by: Thomas Schröder <tschroeder_github@outlook.com>
* apm821xx: switch over from DTB_SIZE to DEVICE_DTC_FLAGSChristian Lamparter2023-06-09
| | | | | | | DEVICE_DTC_FLAGS is more flexible and can be used in place of APM821xx own DTB_SIZE. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: add kmod-ata-dwc to sata targetChristian Lamparter2023-06-09
| | | | | | | though, ata-dwc is built-in on the target already. Fixes: fd9dc10530ef ("apm821xx: make ata-dwc as a standalone module") Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* bmips: bump LZMA Loader addressÁlvaro Fernández Rojas2023-06-09
| | | | | | | | This allows booting bigger ramdisk images via TFTP at the cost of breaking 32M RAM compatibility, but those devices have been unable to boot ramdisks on this target for some time anyway due to not having enough RAM. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bmips: add support for Observa VH4032NDaniel González Cabanelas2023-06-09
| | | | | | | | | | | | | | | | | | | | | | | | The Observa VH4032N is an xDSL wifi router with a vertical white casing and two internal antennas connected via UFL. Hardware: - SoC: Broadcom BCM6368 - CPU: dual core BMIPS4350 V3.1 @400MHz - RAM: 128 MB DDR - Flash: 32 MB parallel NOR - Ethernet LAN: 4x 100Mbit - Wifi 2.4/5 GHz: onboard Broadcom BCM43222 802.11abgn - USB: 3x 2.0 - Buttons: 2x, 1 reset - LEDs: 8x, blue and red - UART: 1x Installation via OEM web UI: 1. Use the admin credentials to login via web UI 2. Go to Managament->Update firmware and select the OpenWrt CFE firmware 3. Press "Update Firmware" button and wait some minutes until it finish Signed-off-by: Daniel González Cabanelas <dgcbueu@gmail.com>
* bcm27xx: remove kernel v5.15 supportÁlvaro Fernández Rojas2023-06-09
| | | | | | | Due to the amount of patches from the RPi foundation, maintaining two kernels version is an insane effort. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm27xx: switch to kernel v6.1Álvaro Fernández Rojas2023-06-09
| | | | | | Enable kernel v6.1 as the default kernel for bcm27xx. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* 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>
Powered by cgit, Themed by Ted Yin.