- Apr 21, 2021
-
-
Edit by Chrissi^: Patch taken from: https://github.com/freifunkh/site/blob/master/patches/0003-added-TP-Link-TL-WR841ND-N-Devices-for-8M-and-16M-Va.patch This Patch adds support for 8M and 16M Flash variants of TP-Link TL-WR841 with hand-made modifications.
-
- Apr 05, 2021
-
-
David Bauer authored
Upstream removed the factory images for the Archer C20 v1 as they potentially brick the device. Remove them from Gluon to avoid build failures on the next OpenWrt 19.07 bump. Signed-off-by:
David Bauer <mail@david-bauer.net> (cherry picked from commit 7d100bc4)
-
- Aug 16, 2020
-
-
Matthias Schiffer authored
-
Matthias Schiffer authored
Only include the major version in the base image name or aliases.
-
- Aug 11, 2020
-
-
David Bauer authored
The packages necessary to get the DSL modem working increase the squashfs size by around 1MB. Remove them from Gluon, as this functionality is not supported. (cherry picked from commit 43b95cfc)
-
- Jun 12, 2020
-
-
Matthias Schiffer authored
Normally, we build all nonshared packages (which includes all kernel modules) to generate an opkg feed for later package installations by users. On targets without opkg, this just wastes time - disable it. (cherry picked from commit b3edfd29)
-
- Jun 04, 2020
-
-
chrissi^ authored
This change stores a Kernel with Debug-Symbols for the current architecture in a new output directory '<outputdir>/debug'. This allows a developer or operator of a network to store the kernel along with the actual images. In case of a kernel oops the debug information can be used with the script 'scripts/decode_stacktrace.sh' in the kernel source tree to get the names to the symbols of the stack trace. OpenWRT already provides the CONFIG_COLLECT_KERNEL_DEBUG -option that creates a kernel with debug-symbols in the OpenWRT output directory. This change enables this option and copies the generated kernel to the gluon output directory. Signed-off-by:
Chrissi^ <chris@tinyhost.de>
-
David Bauer authored
The D-Link DIR-825 has only 6M of usable firmware space.
-
- May 31, 2020
-
-
Matthias Schiffer authored
target_config.lua and target_config_check.lua don't pass a table of callbacks anymore, so target_config_lib.lua can by simplified by moving all the code that was in the returned function to the toplevel.
-
Matthias Schiffer authored
So far, we were using a sort operation on the generated .config to implement precedence of =y packages over =m, and =m over unset. Unfortunately, this sort not only used for packages, but for all config lines. This made it impossible to override settings from targets/generic in a target config when the new setting was sorted before the generic setting. To fix this, track configurations by their keys, so we can properly override config keys that were set before. Value-based precedence is only preserved for package configuration. The config() and try_config() calls always take key and value as separate arguments now. Strings are quoted automatically; the values true, nil and false map to y, m and unset for tristate options. config() can take an optional third argument to override the error message to display when the setting fails to apply. All existing target configs generate the same .config with the old and the new code. The new code is also a bit faster on targets with many devices.
-
- May 28, 2020
-
-
Matthias Schiffer authored
In OpenWrt 19.07, the block size was increased to 1024KiB for "tiny" devices by default to save flash. Unfortunately, this also significantly increases the cache memory required by squashfs. In my test, the increased block size reduced the image size by ~64KiB, but increased the RAM usage by ~2.6MiB. As most tiny devices have only 32MiB of RAM, this is not a reasonable tradeoff. The ar71xx-generic target already defines an even lower block size of 64KiB.
-
Matthias Schiffer authored
This is unused by Gluon.
-
- May 16, 2020
-
-
Vieno Hakkerinen authored
As x86-generic is compiled to pentium4 (and newer) there is a need for a subtarget for older devices. The x86-legacy subtarget is set to compile to pentium (and newer) and should support even very old devics. x86-legacy includes the packages from x86.inc to only maintain one package list. The three excludes are because the packages do not exist for x86-legacy.
-
- May 13, 2020
-
-
Matthias Schiffer authored
-
- May 12, 2020
-
-
lemoer authored
-
- May 03, 2020
-
-
ctr49 authored
-
Matthias Schiffer authored
The precedence of different package lists was broken since #1876, disallowing removal of GLUON_FEATURES packages via GLUON_SITE_PACKAGES. Including all package selections, both implicit defaults and explicit handling in Gluon, the order of precedence is now the following: 1. OpenWrt defaults (including target-specific defaults) 2. Device-specific packages from OpenWrt 3. Generic default packages (from target/generic) 4. Target default packages (target/$(GLUON_TARGET)) 5. Removal of opkg for tiny targets 6. Packages derived from GLUON_FEATURES + GLUON_FEATURES_$(class) 7. GLUON_SITE_PACKAGES 8. GLUON_SITE_PACKAGES_$(class) 9. Device-specific packages from target/$(GLUON_TARGET) 10. Device-specific packages from GLUON_$(device)_SITE_PACKAGES This also contains various pieces of cleanup: - No hardcoded order of device classes for target_config.lua arguments anymore (in fact, the Makefile doesn't know anything about device classes now) - target_conifg_lib.lua only hardcodes the fallback class for x86, no other occurences of specific class names - Feature -> package list mapping is moved from Makefile to the Lua code as well (still implemented in Shell though)
-
- Apr 27, 2020
-
-
André Fiedler authored
-
- Apr 26, 2020
-
-
David Bauer authored
This device has broken Ethernet on both ports. Remove support for those devices. for now, as there was no feedback from the original author. Closes #1943
-
- Apr 25, 2020
-
-
aiyion.prime authored
v2 is available on the market, but apparently has no upstream support, yet: https://forum.openwrt.org/t/v2-of-cudy-wr1000/56965
-
- Apr 09, 2020
-
-
Jan Alexander authored
-
- Apr 06, 2020
-
-
David Bauer authored
x86-geode does not include the common x86 target-settings. Thus we need to specify the device class in order to build images with all necessary packages included.
-
- Mar 27, 2020
-
-
David Bauer authored
When adding device classes, targets without devices such as x86 were not handled. As site and feature packages are included on such a per-device decision, x86 images ended up without most packages. Include a class setting for a target and include the class-packages target-wide when this setting is configured. Fixes 9c523650 ("build: introduce device classes")
-
- Mar 25, 2020
-
-
David Bauer authored
This commit assigns class-flags to devices. The following scheme is used: - ath9k & ath10k: tiny if RAM <128M - ath10k & ath10k: tiny if RAM <256M - all: tiny if RAM <64M - all: tiny if flash <8M All other devices automatically have the default device-class selected.
-
- Mar 23, 2020
-
-
David Bauer authored
-
- Mar 14, 2020
-
-
Matthias Schiffer authored
Signed-off-by:
Matthias Schiffer <mschiffer@universe-factory.net>
-
Andreas Ziegler authored
-
- Mar 09, 2020
-
-
Andreas Ziegler authored
-
Martin Weinelt authored
There is no factory image, they are flashed using the sysupgrade image.
-
David Lutz authored
-
Jan Alexander authored
-
- Feb 04, 2020
-
-
Matthias Schiffer authored
-
Matthias Schiffer authored
Fixes: c3435607 ("generic: increase RootFS size when GLUON_DEBUG is enabled")
-
- Feb 02, 2020
-
-
Manu.WTF authored
-
Andreas Ziegler authored
-
Andreas Ziegler authored
-
- Jan 31, 2020
-
-
Jan Alexander authored
-
- Jan 26, 2020
-
-
Nudelsalat authored
-
- Jan 20, 2020
-
-
Steffen Förster authored
Specification: - MediaTek MT7620A (580 Mhz) - 64 MB of RAM - 8 MB of FLASH - 2T2R 2.4 GHz and 1T1R 5 GHz - 5x 10/100 Mbps Ethernet - 2x external, non-detachable antennas - UART (J1) header on PCB (115200 8n1) - 8x LED (GPIO-controlled*), 2x button, power input switch - 1 x USB 2.0 port
-
- Jan 18, 2020
-
-
Jan Alexander authored
-