[sdwalker/sdwalker.github.io] 5b5aa2: This week's update

2022-03-06 Thread Stephen Walker via openwrt-devel
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 ---
  Branch: refs/heads/master
  Home:   https://github.com/sdwalker/sdwalker.github.io
  Commit: 5b5aa2ee552ecdb82952ac6caeda30affc063c46
  
https://github.com/sdwalker/sdwalker.github.io/commit/5b5aa2ee552ecdb82952ac6caeda30affc063c46
  Author: Stephen Walker 
  Date:   2022-03-06 (Sun, 06 Mar 2022)

  Changed paths:
M uscan/index-19.07.html
M uscan/index-21.02.html
M uscan/index.html

  Log Message:
  ---
  This week's update



--- End Message ---
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


[PATCH] linux-firmware: Update to version 20220209

2022-03-06 Thread Hauke Mehrtens
This switches the iwlwifi-firmware-ax200 file to API version 66, this is
the most recent version supported by our driver.

The following files used in OpenWrt changed:
 amdgpu-firmware/lib/firmware/amdgpu/yellow_carp_dmcub.bin
 ar3k-firmware/lib/firmware/qca/nvm_usb_00130201.bin
 ar3k-firmware/lib/firmware/qca/nvm_usb_00130201_010a.bin
 ar3k-firmware/lib/firmware/qca/nvm_usb_00130201_010b.bin
 ar3k-firmware/lib/firmware/qca/nvm_usb_00130201_0303.bin
 ar3k-firmware/lib/firmware/qca/nvm_usb_00130201_gf.bin
 ar3k-firmware/lib/firmware/qca/nvm_usb_00130201_gf_010a.bin
 ar3k-firmware/lib/firmware/qca/nvm_usb_00130201_gf_010b.bin
 ar3k-firmware/lib/firmware/qca/nvm_usb_00130201_gf_0303.bin
 ar3k-firmware/lib/firmware/qca/rampatch_usb_00130200.bin
 ar3k-firmware/lib/firmware/qca/rampatch_usb_00130201.bin
 iwlwifi-firmware-ax200/lib/firmware/iwlwifi-cc-a0-66.ucode
 iwlwifi-firmware-ax210/lib/firmware/iwlwifi-ty-a0-gf-a0-66.ucode
 iwlwifi-firmware-ax210/lib/firmware/iwlwifi-ty-a0-gf-a0.pnvm
 iwlwifi-firmware-iwl9000/lib/firmware/iwlwifi-9000-pu-b0-jf-b0-46.ucode
 iwlwifi-firmware-iwl9260/lib/firmware/iwlwifi-9260-th-b0-jf-b0-46.ucode
 rtl8822ce-firmware/lib/firmware/rtw88/rtw8822c_fw.bin

Signed-off-by: Hauke Mehrtens 
---
 package/firmware/linux-firmware/Makefile | 6 +++---
 package/firmware/linux-firmware/intel.mk | 2 +-
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/package/firmware/linux-firmware/Makefile 
b/package/firmware/linux-firmware/Makefile
index e46c8870f109..c387e6e4b025 100644
--- a/package/firmware/linux-firmware/Makefile
+++ b/package/firmware/linux-firmware/Makefile
@@ -8,12 +8,12 @@
 include $(TOPDIR)/rules.mk
 
 PKG_NAME:=linux-firmware
-PKG_VERSION:=20211216
-PKG_RELEASE:=2
+PKG_VERSION:=20220209
+PKG_RELEASE:=1
 
 PKG_SOURCE_URL:=@KERNEL/linux/kernel/firmware
 PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.xz
-PKG_HASH:=eeddb4e6bef31fd1a3757f12ccc324929bbad97855c0b9ec5ed780f74de1837d
+PKG_HASH:=e2e46fa618414952bbf2f6920cd3abcddbef45bfb7d1352994b4bfc35394d177
 
 PKG_MAINTAINER:=Felix Fietkau 
 
diff --git a/package/firmware/linux-firmware/intel.mk 
b/package/firmware/linux-firmware/intel.mk
index 908aa9dde0bd..97694572b0bb 100644
--- a/package/firmware/linux-firmware/intel.mk
+++ b/package/firmware/linux-firmware/intel.mk
@@ -171,7 +171,7 @@ $(eval $(call BuildPackage,iwlwifi-firmware-iwl9260))
 Package/iwlwifi-firmware-ax200 = $(call Package/firmware-default,Intel AX200 
firmware)
 define Package/iwlwifi-firmware-ax200/install
$(INSTALL_DIR) $(1)/lib/firmware
-   $(INSTALL_DATA) $(PKG_BUILD_DIR)/iwlwifi-cc-a0-62.ucode 
$(1)/lib/firmware
+   $(INSTALL_DATA) $(PKG_BUILD_DIR)/iwlwifi-cc-a0-66.ucode 
$(1)/lib/firmware
 endef
 $(eval $(call BuildPackage,iwlwifi-firmware-ax200))
 
-- 
2.30.2


___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: [PATCH] command-nas: fix cmd_nas_get_cell_location_info_cb

2022-03-06 Thread Cezary Jackiewicz
Dnia 2022-03-06, o godz. 18:25:57
Jan-Niklas Burfeind  napisał(a):

> Correct order of rsrp and rsrq parameters for print_lte_info.
> 
> Signed-off-by: Jan-Niklas Burfeind 

Hi,
BTW, syntax is invalid. Output is not valid json format.
Could you also proper format output?

Ex: missing keys after serving_cell_id:

# uqmi -d /dev/cdc-wdm0 --get-cell-location-info
{
"intrafrequency_lte_info": {
"tracking_area_code": 11041,
"global_cell_id": 2742796,
"channel": 3526,
"band": 8,
"frequency": 900,
"duplex": "FDD",
"serving_cell_id": 49,
{
"physical_cell_id": 49,
"rsrq": -70.80,
"rsrp": -10.40,
"rssi": -47.20
},
{
"physical_cell_id": 10,
"rsrq": -78.50,
"rsrp": -17.90,
"rssi": -50.90
},
{
"physical_cell_id": 50,
"rsrq": -78.40,
"rsrp": -18.50,
"rssi": -50.90
}
}
}


-- 
Pozdrawiam,
 Cezary Jackiewicz

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


[PATCH] command-nas: fix cmd_nas_get_cell_location_info_cb

2022-03-06 Thread Jan-Niklas Burfeind
Correct order of rsrp and rsrq parameters for print_lte_info.

Signed-off-by: Jan-Niklas Burfeind 
---

This was introduced in
d647f8d89f68 uqmi: add more diagnostics commands

Currently --get-cell-location-info prints the rsrq and rsrp values
swapped.
I ignored the checkpatch.pl warning for line lengths, as the long line is
already in the codebase and only got swapped in their order.


 commands-nas.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/commands-nas.c b/commands-nas.c
index 01ca3b8..ff7a6c3 100644
--- a/commands-nas.c
+++ b/commands-nas.c
@@ -772,8 +772,8 @@ cmd_nas_get_cell_location_info_cb(struct qmi_dev *qmi, 
struct qmi_request *req,
for (i = 0; i < res.data.intrafrequency_lte_info_v2.cell_n; 
i++) {
cell = blobmsg_open_table(, NULL);

print_lte_info(res.data.intrafrequency_lte_info_v2.cell[i].physical_cell_id,
-  
res.data.intrafrequency_lte_info_v2.cell[i].rsrq,
   
res.data.intrafrequency_lte_info_v2.cell[i].rsrp,
+  
res.data.intrafrequency_lte_info_v2.cell[i].rsrq,
   
res.data.intrafrequency_lte_info_v2.cell[i].rssi);
if (res.data.intrafrequency_lte_info_v2.ue_in_idle)
blobmsg_add_u32(, 
"cell_selection_rx_level",
@@ -798,8 +798,8 @@ cmd_nas_get_cell_location_info_cb(struct qmi_dev *qmi, 
struct qmi_request *req,
for (j = 0; j < 
res.data.interfrequency_lte_info.frequency[i].cell_n; j++) {
cell = blobmsg_open_table(, NULL);

print_lte_info(res.data.interfrequency_lte_info.frequency[i].cell[j].physical_cell_id,
-  
res.data.interfrequency_lte_info.frequency[i].cell[j].rsrq,
   
res.data.interfrequency_lte_info.frequency[i].cell[j].rsrp,
+  
res.data.interfrequency_lte_info.frequency[i].cell[j].rsrq,
   
res.data.interfrequency_lte_info.frequency[i].cell[j].rssi);
if (res.data.interfrequency_lte_info.ue_in_idle)
blobmsg_add_u32(, 
"cell_selection_rx_level",
-- 
2.35.1


___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


[PATCH] ath79: fix button labels for WZR-HP-AG300H and WZR-600DHP

2022-03-06 Thread Jeffery To
These were present in ar71xx but overlooked when porting to ath79.

Fixes: 480bf2827392 ("ath79: add support for Buffalo WZR-HP-AG300H")

Signed-off-by: Jeffery To 
---
 target/linux/ath79/dts/ar7161_buffalo_wzr-hp-ag300h.dtsi | 6 ++
 1 file changed, 6 insertions(+)

diff --git a/target/linux/ath79/dts/ar7161_buffalo_wzr-hp-ag300h.dtsi 
b/target/linux/ath79/dts/ar7161_buffalo_wzr-hp-ag300h.dtsi
index 006755e418..35e083bc61 100644
--- a/target/linux/ath79/dts/ar7161_buffalo_wzr-hp-ag300h.dtsi
+++ b/target/linux/ath79/dts/ar7161_buffalo_wzr-hp-ag300h.dtsi
@@ -75,24 +75,28 @@
compatible = "gpio-keys";
 
reset {
+   label = "reset";
linux,code = ;
gpios = < 11 GPIO_ACTIVE_LOW>;
debounce-interval = <60>;
};
 
usb {
+   label = "usb";
linux,code = ;
gpios = < 3 GPIO_ACTIVE_LOW>;
debounce-interval = <60>;
};
 
aoss {
+   label = "aoss";
linux,code = ;
gpios = < 5 GPIO_ACTIVE_LOW>;
debounce-interval = <60>;
};
 
router_auto {
+   label = "router_auto";
linux,code = ;
linux,input-type = ;
gpios = < 6 GPIO_ACTIVE_LOW>;
@@ -100,6 +104,7 @@
};
 
router_off {
+   label = "router_off";
linux,code = ;
linux,input-type = ;
gpios = < 7 GPIO_ACTIVE_LOW>;
@@ -107,6 +112,7 @@
};
 
movie_engine {
+   label = "movie_engine";
linux,code = ;
linux,input-type = ;
gpios = < 8 GPIO_ACTIVE_LOW>;
-- 
2.32.0


___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: [PATCH] realtek: net: dsa: configure better brport flags when ports leave the bridge

2022-03-06 Thread Daniel Golle
On Sat, Mar 05, 2022 at 10:36:07AM +0100, Bjørn Mork wrote:
> Ensures that the DSA driver set exactly the same default flags as the
> bridge when a port joins or leaves.  Without this we end up with a
> confusing flag mismatch, where DSA and bridge ports use different sets
> of flags.
> 
> This is critical as the "learning" mismatch will be harmful to the
> network, causing all traffic to be flooded on all ports.
> 
> The original commit was buggy, trying to set the flags one-by-one in a
> loop.  This was not supported by the API and the end result was that
> all but the last flag were cleared.  This bug was implicitly fixed
> upstream by commit e18f4c18ab5b ("net: switchdev: pass flags and mask
> to both {PRE_,}BRIDGE_FLAGS attributes").
> 
> This is a minimum temporary stop meaure fix for the critical lack of
> "learning" only.  The major API change associated with a full v5.12+
> backport is neither required nor wanted. A simpler fix, moving the
> call to dsa_port_bridge_flags() out of the loop,  has therefore been
> merged into this modified backport.
> 
> Fixes: afa3ab54c03d ("realtek: Backport bridge configuration for DSA")
> Signed-off-by: Bjørn Mork 
Acked-by: Daniel Golle 
(reviewed and lgtm, but can't test it before thursday)


___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel