Home - Waterfall Grid T-Grid Console Builders Recent Builds Buildslaves Changesources - JSON API - About

Builder x86/64 Build #401

Results:

Build successful

SourceStamp:

Repositoryhttps://git.openwrt.org/openwrt/openwrt.git
Branchmaster
Revision68bf5a96595a8a0983842c8ff0eaa8af290adc51
Got Revision68bf5a96595a8a0983842c8ff0eaa8af290adc51
Changes17 changes

BuildSlave:

nomosphere-dock-03

Reason:

The SingleBranchScheduler scheduler named 'all' triggered this build

Steps and Logfiles:

  1. sharedwd Setting up shared work directory ( 0 secs )
    1. stdio
  2. nproc property 'nproc' set ( 0 secs )
    1. stdio
    2. property changes
  3. dlfindbinpl downloading to findbin.pl ( 0 secs )
    1. - no logs -
  4. gcc property 'cc_command' set ( 0 secs )
    1. stdio
    2. property changes
  5. g++ property 'cxx_command' set ( 0 secs )
    1. stdio
    2. property changes
  6. setproperty property 'ccache_command' set ( 0 secs )
    1. stdio
    2. property changes
  7. dlexpiresh dlexpiresh skipped ( 0 secs )
    1. - no logs -
  8. expire Checking for build tree expiry skipped ( 0 secs )
    1. - no logs -
  9. dlcleanupsh dlcleanupsh skipped ( 0 secs )
    1. - no logs -
  10. cleanold Cleaning previous builds skipped ( 0 secs )
    1. - no logs -
  11. cleanup Cleaning work area skipped ( 0 secs )
    1. - no logs -
  12. tools/clean User-requested "make tools/clean" skipped ( 0 secs )
    1. - no logs -
  13. toolchain/clean User-requested "make toolchain/clean" skipped ( 0 secs )
    1. - no logs -
  14. target/linux/clean User-requested "make target/linux/clean" skipped ( 0 secs )
    1. - no logs -
  15. dirclean User-requested "make dirclean" skipped ( 0 secs )
    1. - no logs -
  16. distclean User-requested "make distclean" skipped ( 0 secs )
    1. - no logs -
  17. gitcheckout Ensure that Git HEAD is sane ( 0 secs )
    1. stdio
  18. gitclean update skipped ( 0 secs )
    1. - no logs -
  19. gitfresh update ( 3 secs )
    1. stdio
  20. fetchrefs Fetching Git remote refs ( 0 secs )
    1. stdio
  21. switchtag Checking out Git tag skipped ( 0 secs )
    1. - no logs -
  22. gitverify Ensure that Git HEAD is pointing to a branch or tag ( 0 secs )
    1. stdio
  23. rmtmp Remove tmp folder ( 0 secs )
    1. stdio
  24. rmfeedlinks Remove feed symlinks ( 0 secs )
    1. stdio
  25. ccachecc downloading to ccache_cc.sh ( 0 secs )
    1. - no logs -
  26. ccachecxx downloading to ccache_cxx.sh ( 0 secs )
    1. - no logs -
  27. updatefeeds Updating feeds ( 26 secs )
    1. stdio
  28. installfeeds Installing feeds ( 23 secs )
    1. stdio
  29. dlconfigseed downloading to .config ( 0 secs )
    1. - no logs -
  30. newconfig Seeding .config ( 0 secs )
    1. stdio
  31. delbin Removing output directory ( 0 secs )
    1. stdio
  32. defconfig Populating .config ( 23 secs )
    1. stdio
  33. checkarch Checking architecture ( 0 secs )
    1. stdio
  34. libc property 'libc' set ( 0 secs )
    1. stdio
    2. property changes
  35. dlkeybuildpub downloading to key-build.pub ( 0 secs )
    1. - no logs -
  36. dlkeybuild downloading to key-build ( 0 secs )
    1. - no logs -
  37. dlkeybuilducert downloading to key-build.ucert ( 0 secs )
    1. - no logs -
  38. dldir Preparing dl/ ( 0 secs )
    1. stdio
  39. dltar Building and installing GNU tar ( 1 mins, 6 secs )
    1. stdio
  40. dlrun Populating dl/ ( 46 secs )
    1. stdio
  41. cleanbase Cleaning base-files ( 18 secs )
    1. stdio
  42. tools Building and installing tools ( 4 mins, 27 secs )
    1. stdio
  43. toolchain Building and installing toolchain ( 10 mins, 26 secs )
    1. stdio
  44. kmods Building kmods ( 7 mins, 2 secs )
    1. stdio
  45. kernelversion property 'kernelversion' set ( 0 secs )
    1. stdio
    2. property changes
  46. pkgclean Cleaning up package build ( 12 secs )
    1. stdio
  47. pkgbuild Building packages ( 16 mins, 26 secs )
    1. stdio
  48. pkginstall Installing packages ( 20 secs )
    1. stdio
  49. pkgindex Indexing packages ( 19 secs )
    1. stdio
  50. stageroot property 'stageroot' set ( 3 secs )
    1. stdio
    2. property changes
  51. filesdir Creating file overlay directory ( 0 secs )
    1. stdio
  52. kmodconfig Embedding kmod repository configuration ( 0 secs )
    1. stdio
  53. images Building and installing images ( 14 mins, 4 secs )
    1. stdio
  54. buildinfo Generating config.buildinfo, version.buildinfo and feeds.buildinfo ( 15 secs )
    1. stdio
  55. json_overview_image_info Generate profiles.json in target folder ( 11 secs )
    1. stdio
  56. checksums Calculating checksums ( 13 secs )
    1. stdio
  57. kmoddir Creating kmod directory ( 0 secs )
    1. stdio
  58. kmodprepare Preparing kmod archive ( 0 secs )
    1. stdio
  59. kmodindex Indexing kmod archive ( 16 secs )
    1. stdio
  60. signprepare Ran ( 0 secs )
    1. stdio
  61. signpack Packing files to sign ( 0 secs )
    1. stdio
  62. upload uploading sign.tar.gz ( 0 secs )
    1. - no logs -
  63. signfiles Ran ( 2 secs )
    1. stdio
  64. dlsigntargz downloading to sign.tar.gz ( 0 secs )
    1. - no logs -
  65. signunpack Unpacking signed files ( 0 secs )
    1. stdio
  66. dirprepare Preparing upload directory structure ( 0 secs )
    1. stdio
  67. linkprepare Preparing repository symlink skipped ( 0 secs )
    1. - no logs -
  68. kmoddirprepare Preparing kmod archive upload directory ( 0 secs )
    1. stdio
  69. dirupload Uploading directory structure ( 0 secs )
    1. stdio
  70. target-sha256sums Fetching remote sha256sums for target ( 0 secs )
    1. stdio
  71. dlsha2rsyncpl downloading to sha2rsync.pl ( 0 secs )
    1. - no logs -
  72. buildlist Building list of files to upload ( 0 secs )
    1. stdio
  73. dlrsync.sh downloading to rsync.sh ( 0 secs )
    1. - no logs -
  74. targetupload Uploading target files ( 24 secs )
    1. stdio
  75. targetprune Pruning target files ( 0 secs )
    1. stdio
  76. kmodupload Uploading kmod archive ( 2 secs )
    1. stdio
  77. sourcelist Finding source archives to upload ( 0 secs )
    1. stdio
  78. sourceupload Uploading source archives ( 0 secs )
    1. stdio
  79. df Reporting disk usage ( 0 secs )
    1. stdio
  80. ccachestat Reporting ccache stats ( 0 secs )
    1. stdio

Build Properties:

NameValueSource
branch master Build
builddir /builder/x86_64 slave
buildername x86/64 Builder
buildnumber 401 Build
cc_command /usr/bin/gcc-6 SetPropertyFromCommand Step
ccache_command /usr/bin/ccache SetPropertyFromCommand Step
codebase Build
cxx_command /usr/bin/g++-6 SetPropertyFromCommand Step
dl_lock None BuildSlave
do_cleanup True BuildSlave
got_revision 68bf5a96595a8a0983842c8ff0eaa8af290adc51 Git
kernelversion 5.4.52-1-97976271d9967ffd5cc92d23b4f8e650 SetPropertyFromCommand Step
libc SetPropertyFromCommand Step
max_builds 1 BuildSlave
nproc 8 SetPropertyFromCommand Step
project Build
repository https://git.openwrt.org/openwrt/openwrt.git Build
revision 68bf5a96595a8a0983842c8ff0eaa8af290adc51 Build
scheduler all Scheduler
shared_wd True BuildSlave
slavename nomosphere-dock-03 BuildSlave
stageroot /builder/shared-workdir/build/staging_dir/target-x86_64_musl/root-x86 SetPropertyFromCommand Step
ul_lock None BuildSlave
workdir /builder/x86_64 slave (deprecated)

Forced Build Properties:

NameLabelValue

Responsible Users:

  1. Adrian Schmutzler
  2. Christian Lamparter
  3. David Bauer
  4. Linus Walleij
  5. Robinson Wu
  6. Tony Ambardar

Timing:

StartFri Jul 31 21:49:14 2020
EndFri Jul 31 22:47:38 2020
Elapsed58 mins, 23 secs

All Changes:

:

  1. Change #3478

    Category None
    Changed by Robinson Wu <wurobinsonohnoyoudont@qq.com>
    Changed at Fri 31 Jul 2020 09:40:15
    Repository https://git.openwrt.org/openwrt/openwrt.git
    Branch master
    Revision 84cb0f7ace73fad15e29e1d74c469b37f90b334d

    Comments

    ramips: add support for JS76x8 series DEV boards
    This commit adds support for the Jotale JS76x8 series development boards.
    These devices have the following specifications:
    
    - SOC: MT7628AN/NN, MT7688AN, MT7628DAN
    - RAM of MT7628AN/NN and MT7688AN: 64/128/256 MB (DDR2)
    - RAM of MT7628DAN: 64 MB (DDR2)
    - FLASH:8/16/32 MB (SPI NOR)
    - Ethernet:3x 10/100 Mbps ethernet ports (MT76x8 built-in switch)
    - WIFI:1x 2T2R 2.4 GHz Wi-Fi
    - LEDs:1x system status green LED, 1x wifi green LED,
           3x ethernet green LED
    - Buttons:1x reset button
    - 1x microSD slot
    - 4x USB 2.0 port
    - 1x mini-usb debug UART
    - 1x DC jack for main power (DC 5V)
    - 1x TTL/RS232 UART
    - 1x TTL/RS485 UART
    - 13x GPIO header
    - 1x audio codec(wm8960)
    
    Installation via OpenWrt:
    
    The original firmware is OpenWrt, so both LuCI and sysupgrade can be used.
    
    Installation via U-boot web:
    
    1. Power on board with reset button pressed, release it
       after wifi led start blinking.
    2. Setup static IP 192.168.1.123/4 on your PC.
    3. Go to 192.168.1.8 in browser and upload "sysupgrade" image.
    
    Installation via U-boot tftp:
    1. Connect to serial console at the mini usb, which has been connected to UART0
       on board (115200 8N1)
    2. Setup static IP 192.168.1.123/4 on your PC.
    3. Place openwrt-firmware.bin on your PC tftp server (192.168.1.123).
    3. Connect one of LAN ports on board to your PC.
    4. Start terminal software (e.g. screen /dev/ttyUSB0 115200) on PC.
    5. Apply power to board.
    6. Interrupt U-boot with keypress of "2".
    7. At u-boot prompts:
       Warning!! Erase Linux in Flash then burn new one. Are you sure?(Y/N) Y
       Input device IP (192.168.1.8) ==:192.168.1.8
       Input server IP (192.168.1.123) ==:192.168.1.123
       Input Linux Kernel filename (root_uImage) ==:openwrt-firmware.bin
    8. board will download file from tftp server, write it to flash and reboot.
    
    Signed-off-by: Robinson Wu <wurobinson@qq.com>
    [add license to DTS files, fix state_default and reduce to the mimimum,
    move phy0tpt trigger to DTS, drop ucidef_set_led_timer, fix network ports]
    Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>

    Changed files

    • target/linux/ramips/dts/mt7628an_jotale_js76x8-16m.dts
    • target/linux/ramips/dts/mt7628an_jotale_js76x8-32m.dts
    • target/linux/ramips/dts/mt7628an_jotale_js76x8-8m.dts
    • target/linux/ramips/dts/mt7628an_jotale_js76x8.dtsi
    • target/linux/ramips/image/mt76x8.mk
    • target/linux/ramips/mt76x8/base-files/etc/board.d/02_network
  2. Change #3479

    Category None
    Changed by Adrian Schmutzler <freifunkohnoyoudont@adrianschmutzler.de>
    Changed at Fri 31 Jul 2020 09:40:15
    Repository https://git.openwrt.org/openwrt/openwrt.git
    Branch master
    Revision 6867d86e085dd4a284c8ee8878839c9e77546f46

    Comments

    build: add DEVICE_COMPAT_VERSION and DEVICE_COMPAT_MESSAGE
    We regularly encounter the situation that devices are subject to
    changes that will make them incompatible to previous versions.
    Removing SUPPORTED_DEVICES will not really be helpful in most of these
    cases, as this only helps after a rename.
    
    To solve this situation, this patchset introduces a compatibility
    version for devices. It will be implemented via a per-device
    Make variable DEVICE_COMPAT_VERSION, which will be set to 1.0
    globally by default and then can be overwritten as needed.
    
    Furthermore, a variable DEVICE_COMPAT_MESSAGE is added, where
    a message to be displayed during sysupgrade may be specified
    optionally.
    
    This patch only implements the build variables and adds them
    to the sysupgrade metadata, the evaluation will be addressed
    in a subsequent patch.
    
    To set it, one would just need to add the following to a device node:
    
    define Device/somedevice
      ...
      DEVICE_COMPAT_VERSION := 1.1
      DEVICE_COMPAT_MESSAGE := Config cannot be migrated from swconfig to DSA
    endef
    
    Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>

    Changed files

    • include/image-commands.mk
    • include/image.mk
  3. Change #3480

    Category None
    Changed by Adrian Schmutzler <freifunkohnoyoudont@adrianschmutzler.de>
    Changed at Fri 31 Jul 2020 09:40:15
    Repository https://git.openwrt.org/openwrt/openwrt.git
    Branch master
    Revision 735de53b2aae9be03611715699bf58dff44e8eff

    Comments

    base-files: add support for compat_version on device
    We regularly encounter the situation that devices are subject to
    changes that will make them incompatible to previous versions.
    Removing SUPPORTED_DEVICES will not really be helpful in most of these
    cases, as this only helps after a rename.
    
    To solve this situation, this patchset introduces a compatibility
    version for devices. To complement the DEVICE_COMPAT_VERSION set
    for the image to be flashed, this implements a compat_version on
    the device, so it will have something to compare with the image.
    
    The only viable way to achieve this seems to be via board.d files,
    i.e. this is technically adding a compat version for the device's
    config.
    
    Like for the network setup, this will set up a command
    ucidef_set_compat_version to set the compat_version in board.d.
    This will then add a string to /etc/board.json, which will be
    translated into uci system config by bin/config_generate.
    By this, the compat_version, being a version of the config, will
    also be exposed to the user.
    
    As with DEVICE_COMPAT_VERSION, missing uci entry will be assumed
    as compat_version "1.0", so we only need to add this if a device
    needs to be bumped, e.g.
    
       ucidef_set_compat_version "1.1"
    
    Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>

    Changed files

    • package/base-files/files/bin/config_generate
    • package/base-files/files/lib/functions/uci-defaults.sh
  4. Change #3481

    Category None
    Changed by Adrian Schmutzler <freifunkohnoyoudont@adrianschmutzler.de>
    Changed at Fri 31 Jul 2020 09:40:15
    Repository https://git.openwrt.org/openwrt/openwrt.git
    Branch master
    Revision ad3e1f9db4cffaec6700d780308fb6241c09a96f

    Comments

    base-files: fwtool: implement compatibility check for images
    We regularly encounter the situation that devices are subject to
    changes that will make them incompatible to previous versions.
    Removing SUPPORTED_DEVICES will not really be helpful in most of these
    cases, as this only helps after a rename.
    
    To solve this situation, this patchset introduces a compatibility
    version for devices. In this patch, the actual checks are implemented
    into fwtool_check_image():
    
    If an incompatible change is introduced, one can increase either
    the minor version (1.0->1.1) or the major version (1.0->2.0).
    
    Minor version increment:
    This will still allow sysupgrade, but require to reset config
    (-n or SAVE_CONFIG=0). If sysupgrade is called without -n, a
    corresponding message will be printed. If sysupgrade is called
    with -n, it will just pass, with supported devices being checked
    as usual. (Which will allow us to add back SUPPORTED_DEVICES for
    many cases.)
    
    Major version increment:
    This is meant for potential (rare) cases where sysupgrade is
    not possible at all, because it would break the device.
    In this case, a warning will be printed, and -n won't help.
    
    If image check fails because of one of the versions parts not
    matching, the content of DEVICE_COMPAT_MESSAGE is printed in
    addition to the generic message (if set).
    
    For both cases, upgrade can still be forced with -F as usual.
    
    Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>

    Changed files

    • package/base-files/files/lib/upgrade/fwtool.sh
  5. Change #3482

    Category None
    Changed by Adrian Schmutzler <freifunkohnoyoudont@adrianschmutzler.de>
    Changed at Fri 31 Jul 2020 09:40:15
    Repository https://git.openwrt.org/openwrt/openwrt.git
    Branch master
    Revision 02d6ac1060b4a937adce5912cc22177cac86c318

    Comments

    base-files: fwtool: make compat_version backward compatible
    So far, the compatibility mechanism only works if both device and
    image are already updated to the new routines. This patch extends
    the sysupgrade metadata and fwtool_check_image() to account for
    "older" images as well:
    
    The basic mechanism for older devices to check for image compatibility
    is the supported_devices entry. This can be exploited by putting
    a custom message into this variable of the metadata, so older FW
    will produce a mismatch and print the message as it thinks it's the
    list of supported devices. So, we have two cases:
    
    device 1.0, image 1.0:
      The metadata will just contain supported_devices as before.
    
    device 1.0, image 1.1:
      The metadata will contain:
    
      "new_supported_devices":["device_string1", "device_string2", ...],
      "supported_devices":["Image version 1.1 incompatible to device: ..."]
    
      If the device is "legacy", i.e. does not have the updated fwtool.sh,
      it will just fail with image check and print the content of
      supported_devices. If DEVICE_COMPAT_MESSAGE is set, this will be
      printed on old devices as well through the same mechanism. Otherwise
      a generic "Please check documentation ..." is appended.
    
      Upgrade can still be performed with -F like when
      SUPPORTED_DEVICES has been removed to prevent bricking.
    
      If the device has updated fwtool.sh (but is 1.0), it will just use
      the new_supported_devices instead, and work as intended (flashing
      with -n will work, flashing without will print the appropriate
      warning).
    
    This mechanism should provide a fair tradeoff between simplicity
    and functionality.
    
    Since we touched a lot of fields in metadata, this also bumps
    metadata_version to 1.1.
    
    Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>

    Changed files

    • include/image-commands.mk
    • package/base-files/files/lib/upgrade/fwtool.sh
  6. Change #3483

    Category None
    Changed by Adrian Schmutzler <freifunkohnoyoudont@adrianschmutzler.de>
    Changed at Fri 31 Jul 2020 09:40:15
    Repository https://git.openwrt.org/openwrt/openwrt.git
    Branch master
    Revision 494f12c52df6767ec0fabf2b2fac8f453323a4c5

    Comments

    mvebu: implement compatibility version for DSA migration
    This implements the newly introduced compat-version to prevent
    upgrade between swconfig and DSA for mvebu.
    
    Just define a compat version with minor increment and an appropriate
    message for both image (in Makefile) and device (in base-files).
    
    Having taken care of sysupgrade, we can put back the SUPPORTED_DEVICES
    that have been removed in previous patches to prevent broken config.
    
    Attention:
    
    All users that already updated to the DSA versions in master will
    receive the same incompatibility warning since their devices are still
    "1.0" as far as fwtool can tell.
    Those, and only those, can bypass the upgrade check by using force (-F)
    without having to reset config again. In addition, the new version
    string needs to be put into uci config manually, so the new fwtool
    knows that it actually deals with a "1.1":
    
       uci set "system.@system[-1].compat_version=1.1"
       uci commit system
    
    Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>

    Changed files

    • target/linux/mvebu/cortexa9/base-files/etc/board.d/05_compat-version
    • target/linux/mvebu/image/cortexa9.mk
  7. Change #3484

    Category None
    Changed by Adrian Schmutzler <freifunkohnoyoudont@adrianschmutzler.de>
    Changed at Fri 31 Jul 2020 09:40:15
    Repository https://git.openwrt.org/openwrt/openwrt.git
    Branch master
    Revision 090779b24e436bb5113719eb7067c7b8151abd14

    Comments

    kirkwood: implement compatibility version for DSA migration
    This implements the newly introduced compat-version to prevent
    upgrade between swconfig and DSA for kirkwood.
    
    Just define a compat version with minor increment and an appropriate
    message for both image (in Makefile) and device (in base-files).
    
    Since we never removed SUPPORTED_DEVICES for this target, we don't
    have to add it back either.
    
    Attention:
    
    All users that already updated to the DSA versions in master will
    receive the same incompatibility warning since their devices are still
    "1.0" as far as fwtool can tell.
    Those, and only those, can bypass the upgrade check by using force (-F)
    without having to reset config again. In addition, the new version
    string needs to be put into uci config manually, so the new fwtool
    knows that it actually deals with a "1.1":
    
       uci set "system.@system[-1].compat_version=1.1"
       uci commit system
    
    Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>

    Changed files

    • target/linux/kirkwood/base-files/etc/board.d/05_compat-version
    • target/linux/kirkwood/image/Makefile
  8. Change #3485

    Category None
    Changed by Adrian Schmutzler <freifunkohnoyoudont@adrianschmutzler.de>
    Changed at Fri 31 Jul 2020 09:40:15
    Repository https://git.openwrt.org/openwrt/openwrt.git
    Branch master
    Revision e496eefccca90c0b244434a11393f6f86fd9194a

    Comments

    mvebu: increase compat version for SolidRun ClearFog Base
    When changing the Pro variant to DSA, the ethernet interface rename
    script was dropped by all devices to keep them in sync:
    
      be309bfd7445 ("mvebu: drop 06_set_iface_mac preinit script")
    
    Therefore, network config will be broken after upgrade for the
    Base variant as well. Increase the compat version and provide a
    message to signal that to the users.
    
    Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>

    Changed files

    • target/linux/mvebu/cortexa9/base-files/etc/board.d/05_compat-version
    • target/linux/mvebu/image/cortexa9.mk
  9. Change #3486

    Category None
    Changed by Adrian Schmutzler <freifunkohnoyoudont@adrianschmutzler.de>
    Changed at Fri 31 Jul 2020 09:40:15
    Repository https://git.openwrt.org/openwrt/openwrt.git
    Branch master
    Revision 664237deaa76d46a3047bc9afd6f57aac800753a

    Comments

    mvebu: fix alphabetic sorting in 02_network
    This has been overlooked when removing solidrun,clearfog-a1 entry.
    
    Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>

    Changed files

    • target/linux/mvebu/cortexa9/base-files/etc/board.d/02_network
  10. Change #3487

    Category None
    Changed by Adrian Schmutzler <freifunkohnoyoudont@adrianschmutzler.de>
    Changed at Fri 31 Jul 2020 09:40:15
    Repository https://git.openwrt.org/openwrt/openwrt.git
    Branch master
    Revision c4dd7fc23bfcf3b3f1a838668bb070edc9db5d4b

    Comments

    hostapd: reorganize config selection hierarchy for WPA3
    The current selection of DRIVER_MAKEOPTS and TARGET_LDFLAGS is
    exceptionally hard to read. This tries to make things a little
    easier by inverting the hierarchy of the conditions, so SSL_VARIANT
    is checked first and LOCAL_VARIANT is checked second.
    
    This exploits the fact that some of the previous conditions were
    unnecessary, e.g. there is no hostapd-mesh*, so we don't need
    to exclude this combination.
    
    It also should make it a little easier to see which options are
    actually switched by SSL_VARIANT and which by LOCAL_VARIANT.
    
    The patch is supposed to be cosmetic.
    
    Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>

    Changed files

    • package/network/services/hostapd/Makefile
  11. Change #3488

    Category None
    Changed by Tony Ambardar <itugrokohnoyoudont@yahoo.com>
    Changed at Fri 31 Jul 2020 12:42:14
    Repository https://git.openwrt.org/openwrt/openwrt.git
    Branch master
    Revision a4856dab0d7d68b03b4925e8fea183fe788eb7d7

    Comments

    kernel: mips: restore missing MIPS32 cBPF JIT
    Kernel v5.1 included an eBPF JIT for MIPS32 kernels, but problems were
    discovered [1] and the changes later reverted in kernel v5.5 with commits:
    
      * f8fffebdea75 ("MIPS: BPF: Disable MIPS32 eBPF JIT")
      * 36366e367ee9 ("MIPS: BPF: Restore MIPS32 cBPF JIT")
    
    Only the first of these was backported to LTS kernel 5.4, leaving cBPF
    programs without a JIT and introducing a performance regression for any
    such users e.g. libpcap, tcpdump, etc.
    
    Restore cBPF performance by backporting the second commit above:
      * 070-v5.5-MIPS-BPF-Restore-MIPS32-cBPF-JIT.patch
    
    [1] https://lore.kernel.org/bpf/20191205182318.2761605-1-paulburton@kernel.org/
    
    Signed-off-by: Tony Ambardar <itugrok@yahoo.com>

    Changed files

    • target/linux/generic/backport-5.4/070-v5.5-MIPS-BPF-Restore-MIPS32-cBPF-JIT.patch
  12. Change #3489

    Category None
    Changed by Tony Ambardar <itugrokohnoyoudont@yahoo.com>
    Changed at Fri 31 Jul 2020 12:43:03
    Repository https://git.openwrt.org/openwrt/openwrt.git
    Branch master
    Revision 217877d046414878126e5c8013162e3b7edc774c

    Comments

    base-files: mount bpffs at boot
    Explicitly mount the BPF filesystem if available. This is used for pinning
    eBPF programs and maps, making them accessible to other eBPF programs or
    from userspace with the help of libbpf or bpftool.
    
    Signed-off-by: Tony Ambardar <itugrok@yahoo.com>
    [daniel@makrotopia.org: bumped PKG_RELEASE]
    Signed-off-by: Daniel Golle <daniel@makrotopia.org>

    Changed files

    • package/base-files/Makefile
    • package/base-files/files/etc/init.d/boot
  13. Change #3490

    Category None
    Changed by Adrian Schmutzler <freifunkohnoyoudont@adrianschmutzler.de>
    Changed at Fri 31 Jul 2020 13:03:43
    Repository https://git.openwrt.org/openwrt/openwrt.git
    Branch master
    Revision 65305cb44869774a7db10c517b871dce5ab46ccb

    Comments

    kirkwood: use real model names for Linksys devices
    This replaces the internal device names "Audi" and "Viper" with the
    real model names, which a user would look for. This makes the
    Linksys devices on this target consistent with the names recently
    changed for mvebu based on the same idea.
    
    As a consequence, the "viper" device definition is split into two
    separate definitions with the correct names for both real models.
    
    Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>

    Changed files

    • package/boot/uboot-envtools/files/kirkwood
    • target/linux/kirkwood/base-files/etc/board.d/01_leds
    • target/linux/kirkwood/base-files/etc/board.d/02_network
    • target/linux/kirkwood/base-files/etc/board.d/05_compat-version
    • target/linux/kirkwood/base-files/etc/init.d/bootcount
    • target/linux/kirkwood/base-files/lib/upgrade/platform.sh
    • target/linux/kirkwood/files-5.4/arch/arm/boot/dts/kirkwood-e4200-v2.dts
    • target/linux/kirkwood/files-5.4/arch/arm/boot/dts/kirkwood-ea3500.dts
    • target/linux/kirkwood/files-5.4/arch/arm/boot/dts/kirkwood-ea4500.dts
    • target/linux/kirkwood/image/Makefile
    • target/linux/kirkwood/patches-5.4/105-linksys-viper-dts.patch
  14. Change #3491

    Category None
    Changed by Christian Lamparter <chunkeeyohnoyoudont@gmail.com>
    Changed at Fri 31 Jul 2020 16:17:34
    Repository https://git.openwrt.org/openwrt/openwrt.git
    Branch master
    Revision caa6ada969ddf63eb753840fe9fa2acc726e5d57

    Comments

    apm821xx: disable WNDR4700 5.4 image
    The compressed image that the buildbots are building is too large for
    the netgear uboot and it crashes and soft-bricks the device.
    
    | Uncompressing Kernel Image ...
    | LZMA: uncompress or overwrite error 1 - must RESET board to recover
    
    The whole target likely needs to be switched zImage which is a major
    hassle due to powerpc's legacy bootwrapper setup as compared to ARM.
    So for now, disable the device.
    
    Reported-by: Wiktor Stasiak (FS#3258)
    Signed-off-by: Christian Lamparter <chunkeey@gmail.com>

    Changed files

    • target/linux/apm821xx/image/nand.mk
  15. Change #3492

    Category None
    Changed by Linus Walleij <linus.walleijohnoyoudont@linaro.org>
    Changed at Fri 31 Jul 2020 16:34:40
    Repository https://git.openwrt.org/openwrt/openwrt.git
    Branch master
    Revision 9e02580d52ef6f2ee1eb38ae4e5977bb6002a552

    Comments

    gemini: Add swap partition to DNS-313
    Sometimes when using the DNS-313 memory usage can peak and
    with a simple swap partition we can avoid running into the
    roof and invoking the OOM killer. Set this partition to
    128MB (twice the size of the memory of the DNS-313).
    
    Signed-off-by: Linus Walleij <linus.walleij@linaro.org>

    Changed files

    • target/linux/gemini/image/dns313_gen_hdd_img.sh
  16. Change #3493

    Category None
    Changed by David Bauer <mailohnoyoudont@david-bauer.net>
    Changed at Fri 31 Jul 2020 17:51:51
    Repository https://git.openwrt.org/openwrt/openwrt.git
    Branch master
    Revision 8b3e170526cf0f1d9b15a6dd7787789d15e52cd4

    Comments

    hostapd: fix incorrect service name
    When retrieving the PID for hostapd and wpa_supplicant via ubus the
    wrong service name is currently used. This leads to the following error
    in the log:
    
    netifd: radio0 (1409): WARNING (wireless_add_process):
    executable path /usr/sbin/wpad does not match process  path (/proc/exe)
    
    Fixing the service name retrieves the correct PID and therefore the
    warning won't occur.
    
    Signed-off-by: David Bauer <mail@david-bauer.net>

    Changed files

    • package/kernel/mac80211/files/lib/netifd/wireless/mac80211.sh
    • package/network/services/hostapd/files/hostapd.sh
  17. Change #3494

    Category None
    Changed by David Bauer <mailohnoyoudont@david-bauer.net>
    Changed at Fri 31 Jul 2020 17:52:03
    Repository https://git.openwrt.org/openwrt/openwrt.git
    Branch master
    Revision 68bf5a96595a8a0983842c8ff0eaa8af290adc51

    Comments

    mac80211: don't kill wireless daemon on teardown
    Don't kill the wireless daemon on teardown. hostapd as well as
    wpa_supplicant are managed by procd which would detect the shutdown of
    either process as a crash loop.
    
    Signed-off-by: David Bauer <mail@david-bauer.net>

    Changed files

    • package/kernel/mac80211/files/lib/netifd/wireless/mac80211.sh