Skip to content
Snippets Groups Projects
  1. Mar 13, 2022
  2. Mar 09, 2022
  3. Mar 05, 2022
  4. Mar 01, 2022
  5. Feb 28, 2022
    • Josef Schlehofer's avatar
      u-boot.mk: add LOCALVERSION (explicitly specify OpenWrt build) · d6aa9d9e
      Josef Schlehofer authored
      For debugging purposes, we need to know if users are using modified
      U-boot versions or not. Currently, the U-boot version is somehow
      stripped. This is a little bit problematic when there are
      backported/wip/to-upstream patches.
      
      To make it more confusing, there was (before this commit) two U-boot
      versioning. U-boot compiled by OpenWrt build bots are missing ``Build:``
      This is also the case when the U-boot is compiled locally.
      
      Example:
      ```
      U-Boot SPL 2022.01 (Jan 27 2022 - 00:24:34 +0000)
      U-Boot 2022.01 (Jan 27 2022 - 00:24:34 +0000)
      ```
      
      On the other hand, if you run full build, you can at least see, where it
      was compiled. Notice added ``Build:``.
      
      Example:
      ```
      U-Boot 2022.01 (Jan 27 2022 - 00:24:34 +0000), Build: jenkins-turris-os-packages-burstlab-omnia-216
      ```
      
      In both cases, it is not clear to U-boot developers if it is an unmodified
      build. This is also caused that there is a missing ``.git`` file from
      U-boot folder, and so there is no history. It leads to that it can not
      contain suffix ``-dirty`` (uncommitted modifications) or even something
      else like number of commits, etc. [1]
      
      When U-boot is compiled as it should be, the version should look like
      this: ``U-Boot 2022.04-rc1-01173-g278195ea1f (Feb 11 2022 - 14:46:50 +0100)``
      The date is not changed daily when there are new OpenWrt builds.
      
      This commit adds OpenWrt specific version, which could be verified by
      using strings.
      
      ```
      $ strings bin/targets/mvebu/cortexa9/u-boot-omnia/u-boot-spl.kwb | grep -E "OpenWrt*"
      U-Boot SPL 2022.01-OpenWrt-r18942+54-cbfce923 (Feb 21 2022 - 13:17:34 +0000)
      arm-openwrt-linux-muslgnueabi-gcc (OpenWrt GCC 11.2.0 r18942+54-cbfce923) 11.2.0
      2022.01-OpenWrt-r18942+54-cbfce923
      U-Boot 2022.01-OpenWrt-r18942+54-cbfce923 (Feb 21 2022 - 13:17:34 +0000)
      ```
      
      [1] https://u-boot.readthedocs.io/en/latest/develop/version.html
      
      
      
      Reported-by: default avatarPali Rohár <pali@kernel.org>
      Suggested-by: default avatarKarel Kočí <karel.koci@nic.cz>
      Signed-off-by: default avatarJosef Schlehofer <pepe.schlehofer@gmail.com>
      d6aa9d9e
    • Paul Spooren's avatar
      image-commands.mk: Use ERROR_MESSAGE for imagesize fails · a9478490
      Paul Spooren authored
      
      If a image is bigger than the device can handle, an error message is
      printed. This is usually silenced and silently ignored, making it harder
      to debug. While it's possible to run the build in verbose mode (via
      `make V=s`) and grep for *is too big*, it's more intuitive to print the
      error message directly. For that use the newly unlocked `$(call
      ERROR_MESSAGE,...)` definition which now also print in non-verbose mode.
      
      Fixes: FS#50 (aka #7604)
      
      Signed-off-by: default avatarPaul Spooren <mail@aparcar.org>
      a9478490
    • Paul Spooren's avatar
      verbose.mk: print ERROR messages in non-verbose · aee3594f
      Paul Spooren authored
      
      Using `make -j9` only prints a subset of messages to follow the build
      process progressing. However this silently skips over errors which might
      be of interested. Using `make V=s` easily floods the terminal making it
      hard to find error messages between the lines.
      
      A compromise is the usage of `$(call ERROR_MESSAGE,...)` which prints a
      message in red. This function is silenced in the non-verbose mode, even
      if only used at a single place in `package/Makefile` where it notifies
      about a OPKG corner case.
      
      This commit moves the `ERROR_MESSAGE` definition outside of the
      `OPENWRT_VERBOSE` condition and print error messages in every mode.
      
      With this in place further error messages are possible.
      
      Signed-off-by: default avatarPaul Spooren <mail@aparcar.org>
      aee3594f
    • Yousong Zhou's avatar
      netfilter: add kmod-nft-tproxy · 43276b60
      Yousong Zhou authored
      
      Signed-off-by: default avatarYousong Zhou <yszhou4tech@gmail.com>
      43276b60
    • Yousong Zhou's avatar
      netfilter: add kmod-nft-socket · 0225df1e
      Yousong Zhou authored
      
      Signed-off-by: default avatarYousong Zhou <yszhou4tech@gmail.com>
      0225df1e
    • Yousong Zhou's avatar
  6. Feb 22, 2022
  7. Feb 11, 2022
    • John Audia's avatar
      kernel: bump 5.10 to 5.10.100 · c391dcdf
      John Audia authored
      
      All patches automatically rebased.
      
      Build system: x86_64
      Build-tested: bcm2711/RPi4B, mt7622/RT3200
      Run-tested: bcm2711/RPi4B, mt7622/RT3200
      
      Signed-off-by: default avatarJohn Audia <graysky@archlinux.us>
      c391dcdf
    • John Audia's avatar
      kernel: bump 5.10 to 5.10.99 · 5e43dd1f
      John Audia authored
      Had to update generic defconfig (make kernel_menuconfig CONFIG_TARGET=generic)
      for this bump, but since that only modifies the target defined in .config,
      and since that target also needed to be updated for unrelated reasons, manually
      propagated the newly added symbol to the generic config.
      
      Removed upstreamed:
          pending-5.10/860-Revert-ASoC-mediatek-Check-for-error-clk-pointer.patch[1]
      
      All other patches automatically rebased.
      
      1. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.10.99&id=080f371d984e8039c66db87f3c54804b0d172329
      
      
      
      Build system: x86_64
      Build-tested: bcm2711/RPi4B, mt7622/RT3200
      Run-tested: bcm2711/RPi4B, mt7622/RT3200
      
      Signed-off-by: default avatarJohn Audia <graysky@archlinux.us>
      5e43dd1f
    • John Audia's avatar
      kernel: bump 5.10 to 5.10.98 · e9c1c836
      John Audia authored
      
      Manually rebased:
      	bcm27xx/patches-5.10/950-0675-drm-vc4-hdmi-Drop-devm-interrupt-handler-for-CEC-int.patch
      
      All other patches automatically rebased.
      
      Build system: x86_64
      Build-tested: bcm2711/RPi4B, mt7622/RT3200
      Run-tested: bcm2711/RPi4B, mt7622/RT3200
      
      Signed-off-by: default avatarJohn Audia <graysky@archlinux.us>
      e9c1c836
    • Sungbo Eo's avatar
      ramips: add support for ipTIME AX2004M · 37753f34
      Sungbo Eo authored
      
      ipTIME AX2004M is an 802.11ax (Wi-Fi 6) router, based on MediaTek
      MT7621A.
      
      Specifications:
      * SoC: MT7621A
      * RAM: 256 MiB
      * Flash: NAND 128 MiB
      * Wi-Fi:
        * MT7915D: 2.4/5 GHz (DBDC)
      * Ethernet: 5x 1GbE
        * Switch: SoC built-in
      * USB: 1x 3.0
      * UART: J4 (115200 baud)
        * Pinout: [3V3] (TXD) (RXD) (GND)
      
      MAC addresses:
      
      | interface |    MAC address    |     source     | comment
      |-----------|-------------------|----------------|---------
      |       LAN | 58:xx:xx:00:xx:9B |                | [1]
      |       WAN | 58:xx:xx:00:xx:99 |                |
      |   WLAN 2G | 58:xx:xx:00:xx:98 | factory 0x4    |
      |   WLAN 5G | 5A:xx:xx:40:xx:98 |                |
      |           | 58:xx:xx:00:xx:98 | config ethaddr |
      
      [1] Used in this patch as WLAN 5G MAC address with the local bit set
      
      Load addresses:
      * stock
        * 0x80010000: FIT image
        * 0x81001000: kernel image -> entry
      * OpenWrt
        * 0x80010000: FIT image
        * 0x82000000: uncompressed kernel+relocate image
        * 0x80001000: relocated kernel image -> entry
      
      Notes:
      * This device has a dual-boot partition scheme, but this firmware works
        only on boot partition 1. The stock web interface will flash only on the
        inactive boot partition, but the recovery web page will always flash on
        boot partition 1.
      
      Installation via recovery mode:
      1.  Press reset button, power up the device, wait >10s for CPU LED
          to stop blinking.
      2.  Upload recovery image through the recovery web page at 192.168.0.1.
      
      Revert to stock firmware:
      1.  Install stock image via recovery mode.
      
      Signed-off-by: default avatarSungbo Eo <mans0n@gorani.run>
      37753f34
  8. Feb 06, 2022
  9. Feb 02, 2022
  10. Feb 01, 2022
  11. Jan 29, 2022
    • Sungbo Eo's avatar
      ramips: add support for ipTIME AX2004M · f4a79148
      Sungbo Eo authored
      
      ipTIME AX2004M is an 802.11ax (Wi-Fi 6) router, based on MediaTek
      MT7621A.
      
      Specification:
      * SoC: MT7621A
      * RAM: 256 MiB
      * Flash: NAND 128 MiB
      * Wi-Fi:
        * MT7915D: 2.4/5 GHz (DBDC)
      * Ethernet: 5x 1GbE
        * Switch: SoC built-in
      * USB: 1x 3.0
      * UART: J4 (115200 baud)
        * Pinout: [3V3] (TXD) (RXD) (GND)
      
      MAC address:
      
      | interface |        MAC        |     source     | comment
      |-----------|-------------------|----------------|---------
      |       LAN | 58:XX:XX:00:XX:9B |                | [1]
      |       WAN | 58:XX:XX:00:XX:99 |                |
      |   WLAN 2G | 58:XX:XX:00:XX:98 | factory 0x4    |
      |   WLAN 5G | 5A:XX:XX:40:XX:98 |                |
      |           |                   |                |
      |           | 58:XX:XX:00:XX:98 | config ethaddr |
      
      [1] Used in this patch as WLAN 5G MAC address with the local bit set
      
      Load address:
      * stock
        * 0x80010000: FIT image
        * 0x81001000: kernel image -> entry
      * OpenWrt
        * 0x80010000: FIT image
        * 0x82000000: uncompressed kernel+relocate image
        * 0x80001000: relocated kernel image -> entry
      
      Installation via **recovery** mode:
      1.  Press reset button, power up the device, wait >10s for CPU LED
          to stop blinking.
      2.  Upload recovery image through the recovery web page at 192.168.0.1.
      
      Revert to stock firmware:
      1.  Install stock image via recovery mode.
      
      Signed-off-by: default avatarSungbo Eo <mans0n@gorani.run>
      f4a79148
    • Sungbo Eo's avatar
      kirkwood: add support for ipTIME NAS1 · 957f9ade
      Sungbo Eo authored
      
      ipTIME NAS1 is a 1-bay NAS, based on Marvell Kirkwood SoC.
      
      Specifications:
      * SoC: 88F6281
      * RAM: 256 MiB
      * Flash: SPI NOR 16 MiB
      * SATA: 1x 3Gb/s
      * Ethernet: 1x 1GbE
      * USB: 1x 2.0
      * Fan: 2 speed level
      * UART: JP1 (115200 8N1)
        * Pinout: [3V3] (TXD) (RXD) (GND)
      
      Notes:
      * There are several variants of the model name: "NAS-I", "NASI", "NAS1".
        Here "NAS1" is adopted for consistent naming scheme.
      * The reset button is also a USB copy button in stock FW,
        but in this patch the former is the only default behavior.
      
      Installation via web interface:
      1.  Flash sysupgrade image through the stock web interface.
      
      Revert to stock firmware:
      1.  Perform sysupgrade with stock image.
      
      Signed-off-by: default avatarSungbo Eo <mans0n@gorani.run>
      957f9ade
  12. Jan 28, 2022
  13. Jan 27, 2022
  14. Jan 24, 2022
  15. Jan 19, 2022
  16. Jan 17, 2022
    • Ansuel Smith's avatar
      treewide: drop use of which · 88204bfa
      Ansuel Smith authored
      
      Ubuntu started to flag which as deprecated and it
      seems which is not really standard and may vary
      across Distro.
      Drop the use of which and use the standard 'command -v'
      for this simple task.
      Which is still present in the prereq if some package/script
      still use which.
      A utility script called command_all.sh is implemented that
      will just mimic the output of which -a.
      
      Signed-off-by: default avatarAnsuel Smith <ansuelsmth@gmail.com>
      88204bfa
  17. Jan 16, 2022
  18. Jan 15, 2022
Loading