Skip to content
Snippets Groups Projects
  1. Mar 08, 2022
  2. Mar 07, 2022
    • INAGAKI Hiroshi's avatar
      uboot-envtools: add support for I-O DATA BSH-G24MB · 98113220
      INAGAKI Hiroshi authored
      
      This patch adds the device-specific configuration to u-boot-envtools for
      I-O DATA BSH-G24MB switch.
      
      Signed-off-by: default avatarINAGAKI Hiroshi <musashino.open@gmail.com>
      98113220
    • INAGAKI Hiroshi's avatar
      realtek: add support for I-O DATA BSH-G24MB · 7b197705
      INAGAKI Hiroshi authored
      
      I-O DATA BSH-G24MB is a 24 port gigabit switch, based on RTL8382M.
      
      Specification:
      
      - SoC		: Realtek RTL8382M
      - RAM		: DDR2 128 MiB (Nanya NT5TU128M8HE-AC)
      - Flash		: SPI-NOR 16 MiB (Macronix MX25L12835FM2I-10G)
      - Ethernet	: 10/100/1000 Mbps x24
        - port 1-8	: RTL8218B
        - port 9-16	: RTL8218B (SoC)
        - port 17-24	: RTL8218B
      - LEDs/Keys	: 2x, 1x
      - UART		: pin header on PCB
        - JP2: 3.3V, TX, RX, GND from rear side
        - 115200n8
      - Power		: 100 VAC, 50/60 Hz
        - Plug	: IEC 60320-C13
      
      Flash instruction using sysupgrade image:
      
      1. Boot BSH-G24MB normally
      2. Connect BSH-G24MB to the DHCP enabled network
      3. Find the device's IP address and open the WebUI and login
         Note: by default, the device obtains IP address from DHCP server of
               the network
      4. Open firmware update page ("ファームウェア アップデート")
      5. Rename the OpenWrt sysupgrade image to "bsh-g24mb_v100.image" and
         select it
      6. Press apply ("適用") button to perform update
      7. Wait ~150 seconds to complete flashing
      
      Note:
      
      - BSH-G24MB has a power-related LED ("電源"), but it's not connected to
        the GPIO of the SoC or RTL8231 and cannot be controlled. Instead of
        it, use system status LED on other than running-state.
      
      - "sys_loop" LED indicates system status and loop-detection status in
        stock firmware.
      
      - BSH-G24MB has 2x os-image partitions named as "RUNTIME"/"RUNTIME2" in
        16 MiB SPI-NOR flash and the size of image per partition is only
        6848 KiB. The secondary image is never used on stock firmware, so also
        use it on OpenWrt to get more space.
      
      Signed-off-by: default avatarINAGAKI Hiroshi <musashino.open@gmail.com>
      7b197705
    • Josef Schlehofer's avatar
      nftables: update to version 1.0.2 · d71928c1
      Josef Schlehofer authored
      Changelog:
      https://lwn.net/ml/netdev/YhO5Pn+6+dgAgSd9@salvia/
      
      Patches:
      
      removed:
      - 001-parser-allow-quoted-string-in-flowtable_expr_member:
      it is now part of upstream release [1]
      
      added:
      - 001-examples-compile-with-make-check.patch:
      backported from [2], it fixes:
      
      nft-json-file.c:3:10: fatal error: nftables/libnftables.h: No such file or directory
          3 | #include <nftables/libnftables.h>
            |          ^~~~~~~~~~~~~~~~~~~~~~~~
      compilation terminated.
      
      [1] https://git.netfilter.org/nftables/commit/?h=v1.0.2&id=07af4429241c9832a613cb8620331ac54257d9df
      [2] https://git.netfilter.org/nftables/commit/?id=18a08fb7f0443f8bde83393bd6f69e23a04246b3
      
      
      
      Signed-off-by: default avatarJosef Schlehofer <pepe.schlehofer@gmail.com>
      d71928c1
    • Hauke Mehrtens's avatar
      linux-firmware: Update to version 20220209 · baea8255
      Hauke Mehrtens authored
      
      This switches the iwlwifi-firmware-ax200 file to API version 66, this is
      the most recent version supported by our driver.
      
      The following files used in OpenWrt changed:
       amdgpu-firmware/lib/firmware/amdgpu/yellow_carp_dmcub.bin
       ar3k-firmware/lib/firmware/qca/nvm_usb_00130201.bin
       ar3k-firmware/lib/firmware/qca/nvm_usb_00130201_010a.bin
       ar3k-firmware/lib/firmware/qca/nvm_usb_00130201_010b.bin
       ar3k-firmware/lib/firmware/qca/nvm_usb_00130201_0303.bin
       ar3k-firmware/lib/firmware/qca/nvm_usb_00130201_gf.bin
       ar3k-firmware/lib/firmware/qca/nvm_usb_00130201_gf_010a.bin
       ar3k-firmware/lib/firmware/qca/nvm_usb_00130201_gf_010b.bin
       ar3k-firmware/lib/firmware/qca/nvm_usb_00130201_gf_0303.bin
       ar3k-firmware/lib/firmware/qca/rampatch_usb_00130200.bin
       ar3k-firmware/lib/firmware/qca/rampatch_usb_00130201.bin
       iwlwifi-firmware-ax200/lib/firmware/iwlwifi-cc-a0-66.ucode
       iwlwifi-firmware-ax210/lib/firmware/iwlwifi-ty-a0-gf-a0-66.ucode
       iwlwifi-firmware-ax210/lib/firmware/iwlwifi-ty-a0-gf-a0.pnvm
       iwlwifi-firmware-iwl9000/lib/firmware/iwlwifi-9000-pu-b0-jf-b0-46.ucode
       iwlwifi-firmware-iwl9260/lib/firmware/iwlwifi-9260-th-b0-jf-b0-46.ucode
       rtl8822ce-firmware/lib/firmware/rtw88/rtw8822c_fw.bin
      
      Signed-off-by: default avatarHauke Mehrtens <hauke@hauke-m.de>
      baea8255
    • Rafał Miłecki's avatar
      bcm4908: fix init on CFE devices · c45b5abf
      Rafał Miłecki authored
      
      exit in preinit script was stopping whole process
      
      Fixes: 93259e8c ("bcm4908: support "rootfs_data" on U-Boot devices")
      Signed-off-by: default avatarRafał Miłecki <rafal@milecki.pl>
      c45b5abf
    • Felix Fietkau's avatar
    • Felix Fietkau's avatar
      toolchain/binutils: remove old versions · b3b0a25e
      Felix Fietkau authored
      
      Signed-off-by: default avatarFelix Fietkau <nbd@nbd.name>
      b3b0a25e
  3. Mar 06, 2022
    • Felix Fietkau's avatar
      qosify: update to the latest version · 75914997
      Felix Fietkau authored
      
      3276aed81c73 move run_cmd() to main.c
      558eabc13c64 map: move dns host based lookup code to a separate function
      6ff06d66c36c dns: add code for snooping dns packets
      a78bd43c4a54 ubus: remove dnsmasq subscriber
      9773ffa70f1f map: process dns patterns in the order in which they were defined
      f13b67c9a786 dns: allow limiting dns entry matching to cname name
      
      Signed-off-by: default avatarFelix Fietkau <nbd@nbd.name>
      75914997
    • Bjørn Mork's avatar
      realtek: net: dsa: configure better brport flags when ports leave the bridge · 0890fb2d
      Bjørn Mork authored
      
      Ensures that the DSA driver sets exactly the same default flags as the
      bridge when a port joins or leaves.  Without this we end up with a
      confusing flag mismatch, where DSA and bridge ports use different sets
      of flags.
      
      This is critical as the "learning" mismatch will be harmful to the
      network, causing all traffic to be flooded on all ports.
      
      The original commit was buggy, trying to set the flags one-by-one in a
      loop.  This was not supported by the API and the end result was that
      all but the last flag were cleared.  This bug was implicitly fixed
      upstream by commit e18f4c18ab5b ("net: switchdev: pass flags and mask
      to both {PRE_,}BRIDGE_FLAGS attributes").
      
      This is a minimum temporary stop measure fix for the critical lack of
      "learning" only.  The major API change associated with a full v5.12+
      backport is neither required nor wanted. A simpler fix, moving the
      call to dsa_port_bridge_flags() out of the loop,  has therefore been
      merged into this modified backport.
      
      Fixes: afa3ab54 ("realtek: Backport bridge configuration for DSA")
      Signed-off-by: default avatarBjørn Mork <bjorn@mork.no>
      Acked-by: default avatarDaniel Golle <daniel@makrotopia.org>
      Tested-by: default avatarStijn Tintel <stijn@linux-ipv6.be>
      [fix typos in commit message]
      Signed-off-by: default avatarStijn Tintel <stijn@linux-ipv6.be>
      0890fb2d
    • INAGAKI Hiroshi's avatar
      ramips: use parser_trx for Buffalo WCR-1166DS · f7f9e6bd
      INAGAKI Hiroshi authored
      Buffalo WCR-1166DS uses trx-fomatted firmware and the custom magic
      number (0x5C436F74, "\Cot") is required for OpenWrt installation from
      OEM WebUI.
      But the current mtdsplit_trx doesn't support the custom magic number and
      fail to parse and split to kernel and rootfs when the factory image is
      flashed. Then, the kernel fails to mount rootfs automatically and panics.
      
      Before the commit fddc78bc, mtdsplit_trx
      was patched in ramips target and the device-specific magic number was
      supported only for WCR-1166DS[1].
      But the patch was not inherited to the later version of the kernel and
      deleted by the above commit, then, the custom magic number support was
      broken.
      
      [1]: https://github.com/openwrt/openwrt/blob/05d6e92594c507dcd1f4be6c1bcb2282fe1abe1f/target/linux/ramips/patches-4.4/0400-mtd-mtdsplit-add-support-for-custom-trx-magic-for-Buffalo-WCR-1166DS.patch#L27
      
      
      
      log (factory image):
      
      [    1.165312] spi-mt7621 10000b00.spi: sys_freq: 193333333
      [    1.195782] spi-nor spi0.0: w25q128 (16384 Kbytes)
      [    1.205353] 7 fixed-partitions partitions found on MTD device spi0.0
      [    1.217938] Creating 7 MTD partitions on "spi0.0":
      [    1.227436] 0x000000000000-0x000000030000 : "u-boot"
      [    1.238427] 0x000000030000-0x000000040000 : "u-boot-env"
      [    1.250123] 0x000000040000-0x000000050000 : "factory"
      [    1.261306] 0x000000050000-0x000000810000 : "firmware"
      [    1.282051] 0x000000810000-0x000000fd0000 : "firmware2"
      [    1.293594] 0x000000fd0000-0x000000fe0000 : "glbcfg"
      [    1.304719] 0x000000fe0000-0x000000ff0000 : "board_data"
      ...
      [    1.452424] /dev/root: Can't open blockdev
      [    1.460619] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
      [    1.475434] Please append a correct "root=" boot option; here are the available partitions:
      [    1.491986] 1f00             192 mtdblock0
      [    1.491989]  (driver?)
      [    1.504938] 1f01              64 mtdblock1
      [    1.504941]  (driver?)
      [    1.517885] 1f02              64 mtdblock2
      [    1.517888]  (driver?)
      [    1.530831] 1f03            7936 mtdblock3
      [    1.530834]  (driver?)
      [    1.543777] 1f04            7936 mtdblock4
      [    1.543781]  (driver?)
      [    1.556724] 1f05              64 mtdblock5
      [    1.556727]  (driver?)
      [    1.569672] 1f06              64 mtdblock6
      [    1.569675]  (driver?)
      [    1.582617] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
      [    1.598976] Rebooting in 1 seconds..
      
      This patch fixes this issue by using parser_trx with specifying custom
      magic number in dts instead of mtdsplit_trx.
      
      log (fixed factory image):
      
      [    1.202044] spi-mt7621 10000b00.spi: sys_freq: 193333333
      [    1.225369] spi-nor spi0.0: w25q128 (16384 Kbytes)
      [    1.235015] 7 fixed-partitions partitions found on MTD device spi0.0
      [    1.247603] Creating 7 MTD partitions on "spi0.0":
      [    1.257106] 0x000000000000-0x000000030000 : "u-boot"
      [    1.269447] 0x000000030000-0x000000040000 : "u-boot-env"
      [    1.281192] 0x000000040000-0x000000050000 : "factory"
      [    1.294208] 0x000000050000-0x000000810000 : "firmware"
      [    1.305774] 2 trx partitions found on MTD device firmware
      [    1.316540] Creating 2 MTD partitions on "firmware":
      [    1.326399] 0x00000000001c-0x000000214754 : "linux"
      [    1.336063] mtd: partition "linux" doesn't start on an erase/write block boundary -- force read-only
      [    1.357070] 0x000000214754-0x0000007c0000 : "rootfs"
      [    1.366994] mtd: partition "rootfs" doesn't start on an erase/write block boundary -- force read-only
      [    1.386368] mtd: device 5 (rootfs) set to be root filesystem
      [    1.398700] 1 squashfs-split partitions found on MTD device rootfs
      [    1.411027] 0x000000520000-0x0000007c0000 : "rootfs_data"
      [    1.422841] 0x000000810000-0x000000fd0000 : "firmware2"
      [    1.436282] 0x000000fd0000-0x000000fe0000 : "glbcfg"
      [    1.447408] 0x000000fe0000-0x000000ff0000 : "board_data"
      ...
      [    1.611216] VFS: Mounted root (squashfs filesystem) readonly on device 31:5.
      
      Signed-off-by: default avatarINAGAKI Hiroshi <musashino.open@gmail.com>
      f7f9e6bd
    • INAGAKI Hiroshi's avatar
      ramips: switch parser of trx for mt76x8 subtarget · 5403defb
      INAGAKI Hiroshi authored
      
      This patch enable parser_trx and disable mtdsplit_trx for mt76x8
      subtarget.
      The trx format is used only on Buffalo WCR-1166DS in mt76x8 subtarget
      and the parser need to be switched to parser_trx to use the custom magic
      number in the header for WCR-1166DS.
      
      Signed-off-by: default avatarINAGAKI Hiroshi <musashino.open@gmail.com>
      5403defb
    • INAGAKI Hiroshi's avatar
      kernel: backport patch to allow using parser_trx from ramips · d339de2e
      INAGAKI Hiroshi authored
      
      This patch adds a patch to allow using parser_trx from ramips target,
      mainly for Buffalo devices.
      
      Signed-off-by: default avatarINAGAKI Hiroshi <musashino.open@gmail.com>
      d339de2e
    • INAGAKI Hiroshi's avatar
      kernel: move parser_trx patches of custom magic to generic · cc49abc0
      INAGAKI Hiroshi authored
      
      This patch moves the patches of parser_trx in mediatek target to
      generic/backport-5.10 to use the changes from ramips target and
      backport the additional patch of the parser.
      
      Signed-off-by: default avatarINAGAKI Hiroshi <musashino.open@gmail.com>
      cc49abc0
    • INAGAKI Hiroshi's avatar
      ramips: update MAC address configuration for Buffalo WCR-1166DS · 770cfe9b
      INAGAKI Hiroshi authored
      
      This patch converts MAC address configuration of Buffalo WCR-1166DS in
      02_network to use the generic function of OpenWrt. And also, add
      label_mac.
      
      Signed-off-by: default avatarINAGAKI Hiroshi <musashino.open@gmail.com>
      770cfe9b
    • INAGAKI Hiroshi's avatar
      ramips: increase spi frequency for Buffalo WCR-1166DS · 621d88d7
      INAGAKI Hiroshi authored
      
      Use higher frequency than current and up the speed to access to the
      flash on WCR-1166DS.
      
      Signed-off-by: default avatarINAGAKI Hiroshi <musashino.open@gmail.com>
      621d88d7
    • Joe Mullally's avatar
      ramips: Add support for TP-Link TL-WPA8631P v3 · 6c743c30
      Joe Mullally authored
      
      AV1300 Gigabit Passthrough Powerline ac Wi-Fi Extender
      
      Specifications
      --------------
      * SoC: MediaTek MT7621AT
      * CPU: 880 MHz MIPS 1004KEc dual-core CPU
      * RAM: 64 MiB DDR2 (Zentel A3R12E40DBF-8E)
      * Flash: 8 MiB SPI NOR (GigaDevice GD25Q64CSIG)
      * Ethernet: SoC built-in Switch 5x 1GbE
        * Port 0: PLC (connected through AR8035-A)
        * Port 1-3: LAN
      * WLAN: 2x2 2.4GHz 300 Mbps + 2x2 5GHz 867 Mbps (MT7603EN + MT7613BEN)
      * PLC: HomePlug AV2 (Qualcomm QCA7500)
      * PLC Flash: 2MiB SPI NOR (GigaDevice GD25Q16CSIG)
      * Buttons: Reset, LED, Pair, Wi-Fi
      * LEDs: Power (green), PLC (green/amber), LAN (green), 2.4G (green),
        5G (green)
      * UART: J1 (57600 baud)
        * Pinout: (3V3) (GND) (RX) (TX)
        * Visually identify GND from connection to PCB ground plane
      
      Installation
      ------------
      Installation is possible from the OEM web interface. Make sure to install
      the latest OEM firmware first, so that the PLC firmware is at the latest
      version. However, please first check the OpenWRT Wiki page for
      confirmation that your OEM firmware version is supported.
      
      Signed-off-by: default avatarJoe Mullally <jwmullally@gmail.com>
      6c743c30
  4. Mar 05, 2022
  5. Mar 04, 2022
    • Stijn Tintel's avatar
      qosify: bump to git HEAD · c2d7896a
      Stijn Tintel authored
      
        interface: disable autorate-ingress by default
      
      Also change the example config to reflect this.
      
      Signed-off-by: default avatarStijn Tintel <stijn@linux-ipv6.be>
      c2d7896a
    • Stijn Tintel's avatar
      qosify: add PKG_RELEASE · 1848b25c
      Stijn Tintel authored
      
      Without PKG_RELEASE, it's impossible to trigger package updates when
      changing files included in the package that are not in the qosify git
      repository.
      
      Signed-off-by: default avatarStijn Tintel <stijn@linux-ipv6.be>
      Acked-by: default avatarFelix Fietkau <nbd@nbd.name>
      1848b25c
    • Rafał Miłecki's avatar
      bcm4908: support "rootfs_data" on U-Boot devices · 93259e8c
      Rafał Miłecki authored
      
      1. Create "rootfs_data" dynamicaly
      
      U-Boot firmware images can contain only 2 UBI volumes: bootfs (container
      with U-Boot + kernel + DTBs) and rootfs (e.g. squashfs). There is no way
      to include "rootfs_data" UBI volume or make firmware file tell U-Boot to
      create one.
      
      For that reason "rootfs_data" needs to be created dynamically. Use
      preinit script to handle that. Fire it right before "mount_root" one.
      
      2. Relate "rootfs_data" to flashed firmware
      
      As already explained flashing new firmware with U-Boot will do nothing
      to the "rootfs_data". It could result in new firmware reusing old
      "rootfs_data" overlay UBI volume and its file. Users expect a clean
      state after flashing firmware (even if flashing the same one).
      
      Solve that by reading flash counter of running firmware and storing it
      in "rootfs_data" UBI volume. Every mismatch will result in wiping old
      data.
      
      Signed-off-by: default avatarRafał Miłecki <rafal@milecki.pl>
      93259e8c
  6. Mar 03, 2022
    • Rui Salvaterra's avatar
      procd: remove support for mounting /tmp in zram · 247eaa44
      Rui Salvaterra authored
      The /tmp directory is mounted as tmpfs. The tmpfs filesystem is backed by
      anonymous memory, which means it can be swapped out at any time, if there is
      memory pressure [1]. For this reason, a zram swap device is a much better
      choice than mounting /tmp on zram, since it's able to compress all anonymous
      memory, and not just the memory assigned to /tmp. We already have the zram-swap
      package for this specific purpose, which means procd's tmp-on-zram is both
      redundant and more limited.
      
      A follow-up patch will remove support for mounting /tmp in zram from procd
      itself.
      
      [1] https://www.kernel.org/doc/Documentation/filesystems/tmpfs.txt
      
      
      
      Signed-off-by: default avatarRui Salvaterra <rsalvaterra@gmail.com>
      247eaa44
  7. Mar 01, 2022
Loading