This adds GLUON_BUILDTYPE, which is an option that allows specifying an alternate
base configuration
Other additions:
- GLUON_PREFIX option to specify the filename prefix, if
VERSION_DIST is set
- Skip gluon target-definitions if TARGET_ALL_PROFILES is set
- Allow overriding any file in targets/ by adding the file to site/
- Allow loading the original file using include_gluon() from gluon
We migrate to dnsmasq-full, while disabling most of its features.
Notably, dhcp and dnssec are compiled in, while other features of the
full variant are deselected.
The main difference between the non-EFI and EFI images generated by
OpenWrt is that the former uses an MS-DOS partition table, while the
latter uses GPT. The EFI images still have a BIOS-compatible MBR, so
they work fine on non-EFI systems.
Closes#2403
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
694757a08f
AVM Fritz!Box 7520 and Fritz!Box 7530 use the same hardware platform and can
only be distinguished by using the urlader partition or the fritz-tffs tools
and read the ProductID (Fritz_Box_HW247).
Upstream added a standalone SPI kernel-loader which fixes the unbootable
image for the WDR4900. Thus, we can re-introduce this device to Gluon.
Signed-off-by: David Bauer <mail@david-bauer.net>
Specification:
SoC: MediaTek MT7628AN
RAM: 64MiB
Flash: 8MiB
Wifi:
- 2.4GHz: MT7628AN
- 5GHz: MT7612EN
LAN: 1x 10/100 Mbps
Flash instructions:
Flash factory image through stock firmware WEB UI.
Back to stock is possible by using TFTP and stripping down the Firmware
provided by TP-Link to a initramfs.
The flash space between 0x650000 and 0x7f0000
is blank in the stock firmware so I left it out as well.
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 45c84a117b ("ar71xx: drop target")
Gone due to
commit 45c84a1 ("ar71xx: drop target")
Note that it was wrongly marked as device class tiny in
commit 7fd7116e2a ("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>
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
