next OpenWrt 22.03 and 21.02 minor release
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. On github the following pull requests are tagged for the releases: https://github.com/openwrt/openwrt/pulls?q=is%3Apr+is%3Aopen+label%3Arelease%2F22.03 https://github.com/openwrt/openwrt/pulls?q=is%3Apr+is%3Aopen+label%3Arelease%2F21.02 If we should backport more changes please create a pull request on github, send a patch with the 22.03 or 21.02 prefix to the mailing list or send a mail with a link to the master commit we should backport as an answer to this mail and I will have a look at the commit. Hauke ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [PATCH] ipq40xx: google (gale) add LED aliases
From: Jan-Niklas Burfeind
this is similar to
commit 583ac0e11df7 ("mpc85xx: update lp5521 led-controller node for
5.10")
Google uses white for running and red for an issue
Signed-off-by: Jan-Niklas Burfeind
---
Good morning.
Currently the tristate LED does not have an assigned function,
while it does have several in stock firmware.
Once the multi-intensity section becomes active, the device should use
white/blueish light as running indicator.
For now blue is used for LED_RUNNING.
If there's a way to use white instead of blue, just let me know;
I'd gladly fix that at once.
Thanks for reviewing this,
Aiyion
.../files/arch/arm/boot/dts/qcom-ipq4019-wifi.dts | 11 +--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/target/linux/ipq40xx/files/arch/arm/boot/dts/qcom-ipq4019-wifi.dts
b/target/linux/ipq40xx/files/arch/arm/boot/dts/qcom-ipq4019-wifi.dts
index e4f47431e5..f92c289738 100644
--- a/target/linux/ipq40xx/files/arch/arm/boot/dts/qcom-ipq4019-wifi.dts
+++ b/target/linux/ipq40xx/files/arch/arm/boot/dts/qcom-ipq4019-wifi.dts
@@ -15,6 +15,10 @@
aliases {
label-mac-device =
+ led-boot = _blue;
+ led-failsafe = _red;
+ led-running = _blue;
+ led-upgrade = _red;
};
chosen {
@@ -255,12 +259,13 @@
clock-mode = /bits/ 8 <1>;
#if 1
- led@0 {
+ led0_red: led@0 {
reg = <0>;
chan-name = "LED0_Red";
led-cur = /bits/ 8 <0x64>;
max-cur = /bits/ 8 <0x78>;
color = ;
+ function = LED_FUNCTION_FAULT;
};
led@1 {
@@ -271,12 +276,13 @@
color = ;
};
- led@2 {
+ led0_blue: led@2 {
reg = <2>;
chan-name = "LED0_Blue";
led-cur = /bits/ 8 <0x64>;
max-cur = /bits/ 8 <0x78>;
color = ;
+ function = LED_FUNCTION_POWER;
};
#else
/*
@@ -285,6 +291,7 @@
* # echo 255 > /sys/class/leds/tricolor/brightness
*/
multi-led@2 {
+ function = LED_FUNCTION_POWER;
reg = <2>;
color = ;
#address-cells = <1>;
Can confirm that this is working. Thanks @Aiyion!
Tested-by: Andrijan Möcker
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Problem building libsepol on some systems
Getting straight to the topic I get this error with my custom GitLab
builder (based on Ubuntu 20.04):
make[3]: Entering directory
'/builds/openwrt/openwrt-21.02/package/libs/libsepol'
mkdir -p /builds/openwrt/openwrt-21.02/dl
SHELL= flock /builds/openwrt/openwrt-21.02/tmp/.libsepol-3.2.tar.gz.flock -c '
/builds/openwrt/openwrt-21.02/scripts/download.pl "/builds/openwrt/openwrt-21.02/dl" "libsepol-3.2.tar.gz"
"dfc7f662af8000116e56a01de6a0394ed79be1b34b999e551346233c5dd19508" ""
"https://github.com/SELinuxProject/selinux/releases/download/3.2;'
rm -rf /builds/openwrt/openwrt-21.02/tmp/stage-libsepol
mkdir -p /builds/openwrt/openwrt-21.02/tmp/stage-libsepol/host
/builds/openwrt/openwrt-21.02/staging_dir/target-mipsel_24kc_musl/packages
install -d -m0755 /builds/openwrt/openwrt-21.02/tmp/stage-libsepol/usr/include
cp -fpR
/builds/openwrt/openwrt-21.02/build_dir/target-mipsel_24kc_musl/libsepol-3.2/ipkg-install/usr/include/*
/builds/openwrt/openwrt-21.02/tmp/stage-libsepol/usr/include/
cp: cannot stat
'/builds/openwrt/openwrt-21.02/build_dir/target-mipsel_24kc_musl/libsepol-3.2/ipkg-install/usr/include/*':
No such file or directory
make[3]: *** [Makefile:98:
/builds/openwrt/openwrt-21.02/staging_dir/target-mipsel_24kc_musl/stamp/.libsepol_installed]
Error 1
make[3]: Leaving directory '/builds/openwrt/openwrt-21.02/package/libs/libsepol'
time: package/libs/libsepol/compile#0.32#0.27#0.51
ERROR: package/libs/libsepol failed to build.
I did some debugging and I can share some hints but I'm clueless about
the solution though.
1. Other targets
Above error comes from building ramips/mt7621. I can't reproduce it
building bcm53xx or bcm4908.
2. Local builds
On my local system directory
build_dir/target-mipsel_24kc_musl/libsepol-3.2/ipkg-install/usr/include/
is populated with headers. It seems to be done by
make package/libsepol/compile V=s
during its "make -C include install" step
3. # CONFIG_PACKAGE_libsepol is not set
On both systems I have PACKAGE_libsepol actually disabled. I don't even
know why my local builds compile that package.
4. Setting PACKAGE_libsepol=y
I made my GitLab / Ubuntu 20.04 build actually set PACKAGE_libsepol=y
but it results in exactly the same error. It seems that package just
doesn't get properly build on that system.
5. Broken package?
I suspect this package / its dependencies may be just broken. There was
some problem with buildbot and 3.2 → 3.3 bump too, see commit
ae4069c577fc ("Revert "libsepol: update to version 3.3"").
Is that maybe host packge that depends on target package that doesn't
always get build?
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
octeon: Help with PCIe driver needed
Hi, back in January [1], I reported trouble with networking and PCIe on a Avaya / Xirrus AP. In the meantime, I've found out that it uses a CN7020 CPU (not a CN5020 as previously believed) and that the PCIe driver does not work properly (interrupts don't fire, setup is probably wrong). Comparing the in-tree driver with the SDK driver, it looks like a lot of functionalities and checks for newer CPUs are missing. Is anyone experienced with the Octeon PCIe driver and can shed some light on this? Thanks, Andreas [1] http://lists.openwrt.org/pipermail/openwrt-devel/2023-January/040278.html ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Monitorowanie pracy kontrahentów
The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- Dzień dobry, W 2021 roku aż 77% firm średnich i dużych w Polsce doświadczyło ataku ransomware. Statystyki rosną w zatrważającym tempie – w 2020 roku było to tylko 13%. 8 na 10 ataków skutkuje szyfrowaniem danych firmowych, przez co firma staje w obliczu wysokich strat finansowych wynikających z przerwania ciągłości operacyjnej, utraconych możliwości biznesowych, kosztów operacyjnych czy nadszarpniętego wizerunku. Czy interesuje Państwa niezobowiązująca rozmowa na temat zabezpieczenia infrastruktury w Państwa firmie? Pozdrawiam Tomasz Gonicki --- End Message --- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
