The device is broken until the next release. The LEDs are currently not
working (fixed in current OpenWRT master).

Also give a brief explanation about the BROKEN status being dependent on
the WiFi chip used and not the SoC family in general.

This backports the TP-Link Archer C50 v4.

We are dropping the following upstream commits. They add support for the
TP-Link recovery-flag which enabled the web-recovery. As they are not
needed for the router to work, we drop them for now.

28cd2ca base-files: sysupgrade: support additional mtd options
1e06482 mtd: add logic for TP-Link ramips recovery magic

also added manifest aliases for gl-ar150, gl-ar300m, gl-ar750

This allows for smaller firmware images and makes it possible to reset a
device via firstboot command.

Signed-off-by: Matthias Fritzsche <matthias@chemnitz.freifunk.net>

ath5k supports only IEEE 802.11 a/b/g

Signed-off-by: Matthias Fritzsche <matthias@chemnitz.freifunk.net>

Signed-off-by: Matthias Fritzsche <matthias@chemnitz.freifunk.net>

this matches the output of
lua -e 'print(require(platform_info).get_image_name())'

This way the manifest file is accepted by the autoupdater

This commit removes the broken flag from all devices in the mt76x8
subtarget.

The stability of the mt76 driver for the mt7628 and mt7612 has greatly
improved in the last half-year. It might be still behind ath9k and
ath10k but it is suitable for daily use.

This affects the following devices:

 - GL.iNet MT300N v2
 - TP-Link Archer C50 v3
 - TP-Link TL-WR841 v13

Signed-off-by: Martin Weinelt <martin@darmstadt.freifunk.net>

The driver has stablized enough to officially support ramips-mt76x8 devices
again. At least remove BROKEN for VoCore 2 (as it was supported before).

Signed-off-by: Martin Weinelt <martin@darmstadt.freifunk.net>

Signed-off-by: Christoph Krapp <achterin@googlemail.com>

Signed-off-by: Christoph Krapp <achterin@googlemail.com>

Signed-off-by: Martin Weinelt <martin@darmstadt.freifunk.net>

Fixes #856

This adds support for the TP-Link TL-WR902Ac v1 travel router.

The device is marked as broken due to 64MB which might be insufficient
in certain environments.

kmod-jool build is broken with current kernel 4.14.y.

Some 32 MB devices like the Nanostation M2 suffer from sudden high loads
combined with a squashfs related OOM reboot:

  logd invoked oom-killer: gfp_mask=0x2420848, order=0, oom_score_adj=0
  CPU: 0 PID: 774 Comm: logd Not tainted 4.4.135 #0
  Stack : 804214dc 00000000 00000001 80480000 8182fa3c 80474803 804028d0 00000306
          804e378c 00001ade 00000040 00000000 00000000 800a7f10 00000006 00000000
          00000000 00000000 804063e0 80c69994 804e6542 800a5e8c 02420848 00000000
          00000001 801fd600 00000000 00000000 00000000 00000000 00000000 00000000
          00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
          ...
  Call Trace:
  [<800721cc>] show_stack+0x54/0x88
  [<800d5468>] dump_header.isra.4+0x48/0x130
  [<800d5c38>] check_panic_on_oom+0x48/0x84
  [<800d5d64>] out_of_memory+0xf0/0x324
  [<800d9888>] __alloc_pages_nodemask+0x6b8/0x724
  [<800d2960>] pagecache_get_page+0x154/0x270
  [<80134cb0>] __getblk_slow+0x15c/0x374
  [<80160418>] squashfs_read_data+0x1c8/0x6e8
  [<80164628>] squashfs_readpage_block+0x32c/0x4d8
  [<801622a4>] squashfs_readpage+0x5bc/0x6d0
  [<800dd030>] __do_page_cache_readahead+0x1f8/0x264
  [<800d479c>] filemap_fault+0x1a8/0x458
  [<800efc1c>] __do_fault+0x64/0xd0
  [<800f2824>] handle_mm_fault+0x4a4/0xb40
  [<80076e98>] __do_page_fault+0x134/0x470
  [<80060820>] ret_from_exception+0x0/0x10

Reduction of the SquashFS blocksize should reduce the problem slightly on
these nodes. The image size will increase slightly but this should be no
problem for ar71xx-generic (in contrast to ar71xx-tiny).

The MT76x8 is currently not stable enough for worry-free use with Gluon.
It suffers from reboots in intervals as little as 12 hours or WiFi
freezes for several hours.

It may be unflagged as soon the situation with mt76 got better.

removes cryptic debug messages from kernel ring buffer and
also reduces memory usage by as much as 20-25 MiB.

This device is a dual 5GHz device. It is recommended to manually change the
radio of the first device to the lower 5GHz channels and the second radio
to the upper 5GHz channels.

Add support for IBSS meshing. Leave target marked as BROKEN for IBSS
as stability is unknown and WiFi LEDs are not working.

Functionality was tested in the network of Freifunk Frankfurt with other
ipq40xx and ar71xx devices.

This commit adds support for the new ipq40xx target.