add new lines
rename OEMs

Omit manifest aliases for versions whose upgrade path is no longer supported
Add comment to two manifest aliases regarding the version

Co-authored-by: David Lutz <kpanic@kpanicroom.de>

Remove due to ticket #2939

These devices risk being bricked in a way that can not be recovered
without running full TFTP or serial recovery, as the flash ends up in a
read-only state with no way of upgrading to a fixed version.

Thus, remove the support for the time being. Don't just flag them as
BROKEN, as this would deliberately brick these boards when installating
such an image.

Signed-off-by: David Bauer <mail@david-bauer.net>

Signed-off-by: Florian Maurer <f.maurer@outlook.de>

Signed-off-by: Linus Lüssing <linus.luessing@c0d3.blue>

device fails to build

This reverts commit 97efc8ab. (#2580)

Since the commit was openend the device was moved from ath79-generic to ath79-tiny ([4b5bd15](https://github.com/openwrt/openwrt/commit/4b5bd1509195bc8f19999ebe481b59356b5c3512)).

Therefore the commit breaks builds of the ath79-generic target (`unable to enable device 'ubnt_rocket-m'`).

It might be possible to add support for the ath79-tiny target, and with it the Rocket M2/M5 (XM), in the future.

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

This partially reverts commit 22c47df2.

Devices in ath79-generic like the TP-Link EAP225-Outdoor v1 are really
unstable with the non -ct Wave2 firmware and regulary crash with 100% memory
consumption when only a handful devices are connected via 5 GHz.

closes freifunk-gluon/gluon#2827

The device was introduced in #2332 and merged in 102a4b93.

It appears that the autoupdater name wasn't correct and devices therefore don't receive updates.

root@64295-ggw3-20b399bb366f-132:~# lua -e 'print(require("platform_info").get_image_name())'
enterasys-ws-ap3705i

Now that OpenWrt implements a proper fix for the stalled boots on 74kc
boards, the previous workaround can be removed.

Signed-off-by: David Bauer <mail@david-bauer.net>

This is a temporary measure that fixes #2692.

This reverts commit 15ef8858.

add comments about lacking radios
Co-authored-by: Jan-Niklas Burfeind <git@aiyionpri.me>
Co-authored-by: Matthias Schiffer <mschiffer@universe-factory.net>

It looks like boot hangs on an AC-Mesh for unknown reasons. The last
message seen on the console is:

    [    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes, linear)

But interestingly, it seems like enabling AIO somehow works around this
problem. Changing any off the following options seem to have the same
effect at the moment for Linux 5.10.160+5.10.161

    # CONFIG_KERNEL_AIO is not set
    # CONFIG_KERNEL_CGROUPS is not set
    # CONFIG_KERNEL_FANOTIFY is not set
    # CONFIG_KERNEL_FHANDLE is not set
    # CONFIG_KERNEL_IO_URING is not set
    # CONFIG_KERNEL_IPV6_MROUTE is not set
    # CONFIG_KERNEL_IPV6_SEG6_LWTUNNEL is not set
    # CONFIG_KERNEL_IP_MROUTE is not set
    CONFIG_KERNEL_PROC_STRIPPED=y

Just enable CONFIG_AIO until the actual problem was fixed.

Link: https://github.com/freifunk-gluon/gluon/issues/2784

Signed-off-by: David Bauer <mail@david-bauer.net>

fixes OOM reboots due too limited ram with ath10k 5Ghz enabled
add some comments to describe the need for ath10k-ct replacement
tested stable on an TP-Link Archer C25v1
more details
https://github.com/openwrt/openwrt/commit/694757a08f620a9f24b70003542d9dcd0abeac46

Ubiquiti Nanostation Loco M XW was renamed in v2022.1.x, but the alias to the old name was missing, so devices running the old release did not update.

Gone due to
commit 45c84a11 ("ar71xx: drop target")

Note: Buffalo has introduced hardware changes without bumping the
revision number. 19.07 did not support the rb-variant so there's no need
to implement a migration for the rb-variant.
Every g300nh supported by Gluon should either be the s-variant or
been flashed wrongly.

Gone due to
commit 45c84a11 ("ar71xx: drop target")

Gone due to
commit 45c84a11 ("ar71xx: drop target")

Gone due to
commit 45c84a11 ("ar71xx: drop target")

Gone due to
commit 45c84a11 ("ar71xx: drop target")

Gone due to
commit 45c84a11 ("ar71xx: drop target")

Note that it was wrongly marked as device class tiny in
commit 7fd7116e ("targets: add device-class flags") in the past,
the device has 64MB RAM and not 32MB.

Also, the device has no "led-running" assigned in DTS. The device has
three LEDs: "green:vpn", "green:lan" and "green:wlan". The first LED,
"green:vpn", has a "V" icon and was used to show the VPN connection
status in the vendor firmware. This LED will be used via the newly
added "led-boot" fallback in gluon-setup-mode. But will be unused
during normal operation due to the unassigned "led-running" in DTS.

Signed-off-by: Linus Lüssing <linus.luessing@c0d3.blue>

Gone due to
commit 45c84a11 ("ar71xx: drop target")

The CN/RU variant of the device has the same hardware
as the EU already supported, but contains a 16M flash chip.

Gone due to
commit 45c84a11 ("ar71xx: drop target")

ar71xx only supported the 8M variant

Specifications:
* SoC: AR7242 (Virian 400MHz)
* RAM: 64 MB DDR (W9751G6JB-25)
* Flash: 16MB SPI flash (S25FL129PIF)
* WiFi: AR9382 (2.4/5GHz) + 2x SE2595L
* LAN: 1x1000M (PEF7071V)

To install via EVA bootloader, a FTP connection need to be
established to 192.168.178.1 within the first seconds after power on:

  ftp> quote USER adam2
  ftp> quote PASS adam2
  ftp> binary
  ftp> debug
  ftp> passive
  ftp> quote MEDIA FLSH
  ftp> put lede-ar71xx-generic-fritz300e-squashfs-sysupgrade.bin mtd1