1. 20 Sep, 2019 3 commits
  2. 16 Sep, 2019 1 commit
  3. 13 Sep, 2019 4 commits
  4. 12 Sep, 2019 1 commit
    • Yousong Zhou's avatar
      tools: mkimage: fix __u64 typedef conflict with new glibc · 6f677d68
      Yousong Zhou authored
      Including "sys/stat.h" from newer glibc will cause __u64 from linux uapi
      header to be included, causing compilation failure for u-boot tools
      Remove typedef for __u64 in include/compiler.h to fix the issue.  It should be
      safe because as of u-boot-2018.03, no ref to __u64 is found under u-boot tools/
      Error message snippet follows
      	  HOSTCC  tools/mkenvimage.o
      	In file included from /usr/include/asm-generic/types.h:7,
      			 from /usr/include/asm/types.h:5,
      			 from /usr/include/linux/types.h:5,
      			 from /usr/include/linux/stat.h:5,
      			 from /usr/include/bits/statx.h:30,
      			 from /usr/include/sys/stat.h:446,
      			 from tools/mkenvimage.c:21:
      	/usr/include/asm-generic/int-ll64.h:31:42: error: conflicting types for '__u64'
      	   31 | __extension__ typedef unsigned long long __u64;
      	      |                                          ^~~~~
      	In file included from <command-line>:
      	././include/compiler.h:69:18: note: previous declaration of '__u64' was here
      	   69 | typedef uint64_t __u64;
      	      |                  ^~~~~
      	make[5]: *** [scripts/Makefile.host:116: tools/mkenvimage.o] Error 1
      Ref: https://forum.openwrt.org/t/compile-error-19-07/44423
      Ref: https://bugzilla.redhat.com/show_bug.cgi?id=1699194
      Signed-off-by: default avatarYousong Zhou <yszhou4tech@gmail.com>
  5. 11 Sep, 2019 2 commits
  6. 09 Sep, 2019 4 commits
  7. 03 Sep, 2019 1 commit
  8. 30 Aug, 2019 2 commits
    • Michal Cieslakiewicz's avatar
      ar71xx: WNR2200: remove redundant GPIO for WLAN LED · 7ac60446
      Michal Cieslakiewicz authored
      Without this patch, an extra entry appears for AR9287 GPIO
      that duplicates WLAN LED but in fact drives nothing:
      gpiochip1: GPIOs 502-511, ath9k-phy0:
       gpio-502 (                    |netgear:blue:wlan   ) out hi
       gpio-503 (                    |netgear:amber:test  ) out hi
       gpio-504 (                    |netgear:green:power ) out lo
       gpio-505 (                    |rfkill              ) in  hi
       gpio-507 (                    |wps                 ) in  hi
       gpio-508 (                    |reset               ) in  hi
       gpio-510 (                    |ath9k-phy0          ) out hi <===!
      The pin pointed above is default LED GPIO (8) for AR9287.
      For WNR2200 it is not connected anywhere - pin 0 drives blue WLAN
      LED instead - but initialization code is missing that information.
      This fix calls ap9x_pci_setup_wmac_led_pin() function at device
      setup, forcing WLAN LED pin to be 0 and removing redundant entry.
      Signed-off-by: default avatarMichal Cieslakiewicz <michal.cieslakiewicz@wp.pl>
    • Koen Vandeputte's avatar
      kernel: bump 4.14 to 4.14.141 · 9d1cd9d0
      Koen Vandeputte authored
      Refreshed all patches.
      Compile-tested on: cns3xxx
      Runtime-tested on: cns3xxx
      Signed-off-by: default avatarKoen Vandeputte <koen.vandeputte@ncentric.com>
  9. 28 Aug, 2019 3 commits
    • Koen Vandeputte's avatar
      ath9k: backport dynack improvements · 4b5c77ca
      Koen Vandeputte authored
      Close cooperation with Lorenzo Bianconi resulted
      in these patches which fix all remaining seen issues
      when using dynack.
      Fix link losses when:
      - Late Ack's are not seen or not present
      - switching from too low static coverage class to dynack on a live link
      These are fixed by setting the Ack Timeout/Slottime to
      the max possible value for the currently used channel width when
      a new station has been discovered.
      When traffic flows, dynack is able to adjust to optimal values
      within a few packets received (typically < 1 second)
      These changes have been thoroughly tested on ~60 offshore devices
      all interconnected using mesh over IBSS and dynack enabled on all.
      Distances between devices varied from <100m up to ~35km
      [move patches to correct folder + renumber]
      Signed-off-by: default avatarKoen Vandeputte <koen.vandeputte@ncentric.com>
      Signed-off-by: default avatarLorenzo Bianconi <lorenzo@kernel.org>
      (cherry picked from commit f6e8ba0238fe349b7529357793e2fb18635819ed)
    • Koen Vandeputte's avatar
      kernel: bump 4.14 to 4.14.140 · 73bba470
      Koen Vandeputte authored
      Refreshed all patches.
      Compile-tested on: cns3xxx
      Runtime-tested on: cns3xxx
      Signed-off-by: default avatarKoen Vandeputte <koen.vandeputte@ncentric.com>
    • Koen Vandeputte's avatar
      kernel: bump 4.9 to 4.9.190 · 8bc800aa
      Koen Vandeputte authored
      Refreshed all patches.
      - CVE-2019-3900
      Compile-tested on: ar71xx
      Runtime-tested on: ar71xx
      Signed-off-by: default avatarKoen Vandeputte <koen.vandeputte@ncentric.com>
  10. 27 Aug, 2019 1 commit
  11. 18 Aug, 2019 1 commit
    • Hauke Mehrtens's avatar
      musl: Fix CVE-2019-14697 · 09d63fb0
      Hauke Mehrtens authored
      musl libc through 1.1.23 has an x87 floating-point stack adjustment
      imbalance, related to the math/i386/ directory. In some cases, use of
      this library could introduce out-of-bounds writes that are not present
      in an application's source code.
      This problem only affects x86 and no other architectures.
      Signed-off-by: default avatarHauke Mehrtens <hauke@hauke-m.de>
      (cherry picked from commit c262daf3)
  12. 17 Aug, 2019 3 commits
  13. 14 Aug, 2019 7 commits
  14. 09 Aug, 2019 2 commits
  15. 07 Aug, 2019 2 commits
  16. 06 Aug, 2019 3 commits