Hi,
wouldn't this solution stop to work as soon as some OEM-OpenWrt is
rebased on OpenWrt and knows about compat_version?
If i'm wrong, please enlighten me.
Regards
Andreas
Adrian Schmutzler wrote on 06.02.21 17:42:
> Hi,
>
> when reviewing device-support PRs, I frequently encounter the cas
add definition of LAN LED to board.d/01_leds
rename WiFi LED with correct color red
rename status LED with correct color green
(like they are used in stock firmware)
Signed-off-by: Andreas Ziegler
---
target/linux/ath79/base-files/etc/board.d/01_leds| 4
target/linux/ath79/dts
Hi Jeff,
thanks for your updated Patch.
I tested it and it basically works - but you missed to adjust
target/linux/ath79/base-files/etc/board.d/01_leds
again.
Please look at my patch and specify the LAN LED accordingly in this file.
Regards
Andreas
Jeff Kletsky schrieb am 01.03.19 um 23:18:
>
Martin Weinelt schrieb am 14.03.19 um 22:58:
> On 3/14/19 9:59 PM, Moritz Warning wrote:
>> Hi,
>>
>> I submitted a GSoC 2019 idea to create a Firmware Wizard for openwrt.org:
>> https://projects.freifunk.net/#/projects?project=openwrt_firmware_wizard&lang=en
>>
>
> Hi,
>
> the upstream for the
The port labled as "LAN" is eth1.
That's different from the -lite variant,
where the only existing port eth0 is used as LAN
---
target/linux/ath79/base-files/etc/board.d/01_leds | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/ath79/base-files/etc/board.d/01_leds
b
The port labled as "LAN" is eth1.
That's different from the -lite variant,
where the only existing port eth0 is used as LAN
Signed-off-by: Andreas Ziegler
---
target/linux/ath79/base-files/etc/board.d/01_leds | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tar
Dmitry Tunin schrieb am 30.07.19 um 14:29:
> Are you taking in account that many devices added during the last year
> as ath79 won't be supported by a stable release.
> Master is no good now for normal use. That will mean that for the next
> year or so many users will require custom 19.07 builds.
This fixes the 5GHz WiFi LED which was previously not working.
Signed-off-by: Andreas Ziegler
---
target/linux/ramips/dts/ZBT-WG3526.dtsi | 4
1 file changed, 4 insertions(+)
diff --git a/target/linux/ramips/dts/ZBT-WG3526.dtsi
b/target/linux/ramips/dts/ZBT-WG3526.dtsi
index afe99e8673
remove USB as this is no LED but power control
rename WiFi LED with correct color red (like in stock firmware)
set middle LED to be used for LAN link/activity
Signed-off-by: Andreas Ziegler
---
target/linux/ar71xx/base-files/etc/board.d/01_leds | 1 +
.../linux/ar71xx/files/arch/mips
Hi Jeff,
thanks for your suggested change!
Although i agree with your change regarding USB GPIO, i don't with the
other part.
Using stock/vendor firmware, GPIO 12 is a green system/status LED and
GPIO 14 is a red wifi LED.
I just sent a patch to the list which fixes this in ar71xx target, maybe
The Unifi AC-LR has identical hardware to the Unifi AC-Lite.
The antenna setup is different according to the vendor,
which explains the thicker enclosure.
Therefore, it is helpful to know the exact device variant,
instead of having "Ubiquiti UniFi-AC-LITE/MESH".
Signed-off-by: Andre
Adrian Schmutzler schrieb am 14.10.19 um 14:18:
> Since we are using a lot of hyphens for other Ubiquiti devices, too, I
> wouldn't bother for this commit.
this was my only intention: keeping it consistent with already supported
unifi devices.
i don't mind anyone changing this before committing
-by: Andreas Ziegler
---
target/linux/ar71xx/base-files/lib/ar71xx.sh | 3 +++
target/linux/ar71xx/image/generic-ubnt.mk| 6 ++
2 files changed, 9 insertions(+)
diff --git a/target/linux/ar71xx/base-files/lib/ar71xx.sh
b/target/linux/ar71xx/base-files/lib/ar71xx.sh
index 03dfbcebf9
Hi Adrian,
> Since this is ar71xx, where vendor_model scheme is not used at all, I would
> prefer using "ubnt-unifiac-lr" for consistency.
i don't mind.
Do i need to send a V2 for such a small change? Maybe this can be done
if it gets merged?
Kr,
Andreas
___
Hi,
although i'm more a user than a developer, i would also prefer a sooner
release based on 4.19 over a later release based on 5.4.
Maybe it's the same problem, too atheros-centric ;-)
Regards
Andreas
Michal Cieslakiewicz wrote on 16.01.20 19:43:
> Hi!
>
> Speaking as a small part-time contri
Mateusz Jończyk wrote on 06.04.23 14:18:
W dniu 28.03.2023 o 00:54, hauke at hauke-m.de (Hauke Mehrtens) pisze:
Hi,
I would like to create a new OpenWrt 22.03 and 21.02 minor release in
the next week.
OpenWrt 21.02.6 would be the final release of the OpenWrt 21.02 series.
Hello,
Last week,
16 matches
Mail list logo