Skip to content
Snippets Groups Projects
  1. Dec 09, 2019
  2. Dec 08, 2019
  3. Dec 07, 2019
  4. Dec 06, 2019
  5. Dec 05, 2019
    • John Crispin's avatar
      mediatek: fix pcie bringup issue · a512123a
      John Crispin authored
      
      Signed-off-by: default avatarJohn Crispin <john@phrozen.org>
      a512123a
    • Jason A. Donenfeld's avatar
      wireguard: bump to 0.0.20191205 · 82a8f91c
      Jason A. Donenfeld authored
      
      * wg-quick: linux: suppress error when finding unused table
      
      This fixes a spurious warning messages seen with recent versions of iproute2
      and kernels.
      
      * wg-quick: linux: ensure postdown hooks execute
      * wg-quick: linux: have remove_iptables return true
      * wg-quick: linux: iptables-* -w is not widely supported
      
      Adding in iptables had some hiccups. For the record, I'm very unhappy about
      having to put any firewalling code into wg-quick(8). We'll of course need to
      support nftables too at some point if this continues. I'm investigating with
      upstream the possibility of adding a sysctl to patch the issue that iptables
      is handling now, so hopefully at somepoint down the line we'll be able to shed
      this dependency once again.
      
      * send: use kfree_skb_list
      * device: prepare skb_list_walk_safe for upstreaming
      * send: avoid touching skb->{next,prev} directly
      
      Suggestions from LKML.
      
      * ipc: make sure userspace communication frees wgdevice
      
      Free things properly on error paths.
      
      Signed-off-by: default avatarJason A. Donenfeld <Jason@zx2c4.com>
      82a8f91c
  6. Dec 04, 2019
  7. Dec 03, 2019
    • Kevin Darbyshire-Bryant's avatar
      kernel: act_ctinfo: update backport · 1d608a10
      Kevin Darbyshire-Bryant authored
      
      Since the original backports from kernel 5.3 a few things have been
      tweaked by kernel bumps & other upstream changes.  Update the backport
      to reflect upstream as closely as possible and remove the bitrot.
      
      Functions remain the same, error reporting improved.
      
      Signed-off-by: default avatarKevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
      1d608a10
    • Adrian Schmutzler's avatar
      ath79: fix source of label MAC address for Ubiquiti XM devices · f6385f30
      Adrian Schmutzler authored
      
      In d421a8b9 ("ath79: read label MAC address from flash instead
      of using phy0/phy1") the source of the label MAC address was changed
      for devices just reading it from phy0. To get rid of the dependency
      from phy startup, addresses were read directly from the flash
      locations that are used to initialize the phy MAC addresses.
      
      Unfortunately, it turned out that Ubiquiti XM devices seem to have
      different flash locations than expected, and also seem to have
      specific locations for different devices (all in art/EEPROM):
      
      0xe012 AR9280 Nanostation M2 - 0x120c
      0xe035 AR9280 Nanostation M3 - 0x120c
      0xe1b2 AR9280 Rocket M2 - 0x120c
      0xe1c3 AR9280 Rocket M3 - 0x120c
      0xe1b5 AR9280 Rocket M5 - 0x120c
      0xe2d5 AR9280 Bullet M2 Titanium - 0x120c
      0xe2b5 AR9280 Nanobridge M5 - 0x120c
      0xe202 AR9280 Bullet M2 - 0x120c
      0xe232 AR9287 Nanobridge M2 - 0x110c
      0xe4a2 AR9285 AirRouter - 0xa0bf
      Picostation M2 - 0x120c and 0xa0bf
      Nanostation Loco M2 - not in 0x120c, other locations not checked
      
      An additional problem of the Ubiquiti device support in OpenWrt is
      that we provide images that match several subvariants of the devices,
      which might have different MAC address locations.
      
      Given that reading the address from phy0 in 02_network _is_ working
      for the ath79 target in general, it does not seem reasonable to
      rebuild a complex MAC address retrieval mechanism which is already
      present in the ath9k driver.
      
      So, this patch reverts the label MAC address source for Ubiquiti XM
      devices (and the Unifi AP) to /sys/class/ieee80211/phy0/macaddress.
      
      This doesn't affect XW and Unifi AC devices, where the label MAC
      address source is defined via device tree.
      
      For alfa-network,ap121f the location 0x1002 is kept, as this has
      been verified during device support preparation in PR #2199.
      
      Fixes: d421a8b9 ("ath79: read label MAC address from flash
      instead of using phy0/phy1")
      
      Signed-off-by: default avatarAdrian Schmutzler <freifunk@adrianschmutzler.de>
      f6385f30
  8. Dec 02, 2019
  9. Nov 30, 2019
    • Stijn Tintel's avatar
      octeon: fix sysupgrade · 291d7993
      Stijn Tintel authored
      
      Sysupgrade was failing due to incorrect replacement of backticks:
      /sbin/sysupgrade: /lib/upgrade/platform.sh: line 101: syntax error: missing '))'
      
      Fixes: 0bbfc3df ("octeon: replace backticks by $(...)")
      Signed-off-by: default avatarStijn Tintel <stijn@linux-ipv6.be>
      291d7993
    • David Bauer's avatar
      generic ar8xxx: increase VLAN table for AR83x7 · 3f79aaa2
      David Bauer authored
      
      The Atheros AR8327 and AR8337 have (according to their datasheet) a
      VLAN table with a maximum of 4096 entries.
      
      Currently, there's a hard limit of 128 VLANs, which is the same as
      for most other Atheros switches. Increase this limit only for the
      AR83x7 series and modify some shared functions to allow them to work
      with a variable max VLAN count.
      
      Signed-off-by: default avatarDavid Bauer <mail@david-bauer.net>
      3f79aaa2
    • Christian Lamparter's avatar
      mac80211: switch to upstream owl-loader driver · 82a741c7
      Christian Lamparter authored
      
      The Owl Loader (named after the codename that Atheros gave
      these devices back in the day) has been accepted upstream.
      
      This patch removes the "misc" driver OpenWrt had and adds
      the remaining differences against the version that ships
      with 5.4-rc1 into a separate "120-owl-loader-compat.patch"
      file that can be cut down once AR71XX is being dealt with.
      
      Note: I decided to keep the existing (kmod-)owl-loader
      package name around for now. The kernel module file in
      the kmod package will be called ath9k_pci_owl_loader.ko
      though.
      
      Acked-by: default avatarHauke Mehrtens <hauke@hauke-m.de>
      Signed-off-by: default avatarChristian Lamparter <chunkeey@gmail.com>
      82a741c7
  10. Nov 29, 2019
Loading