Re: [OpenWrt-Devel] [PATCH V2 1/2] lua: include version number in installed files
On 22.06.2019 14:11, Rafał Miłecki wrote: From: Rafał Miłecki This will allow installing Lua 5.1 and newer versions at the same time. Signed-off-by: Rafał Miłecki --- V2: Bump PKG_RELEASE I'm going to fix: Applying ./patches-host/010-lua-5.1.3-lnum-full-260308.patch using plaintext: patching file Makefile Hunk #1 FAILED at 42. 1 out of 1 hunk FAILED -- saving rejects to file Makefile.rej and push this one. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ath79: add support for gl-ar750
Am Mittwoch, 26. Juni 2019, 12:02:23 CEST schrieb Luochongjun: > This patch supports gl-ar750, which was previously supported by ar71xx. > > Specification: > - SOC: QCA9531 (650MHz) > - Flash: 16 MiB (W25Q128FVSG) > - RAM: 128 MiB DDR2 > - Ethernet: 10/100: 2xLAN + 10/100: 1xWAN > - Wireless: 2.4GHz (bgn) and 5GHz (ac) > - USB: 1x USB 2.0 port > - Switch: 1x switch > - Button: 1x reset button > - LED: 3x LEDS (white) > > Flash instruction: > Support for sysupgrade directive upgrades, as well as luci upgrades. > Thanks for porting this device. Based on your previous patch I built an image and flashed it. Two thing to mention: * probalby you can add a line "SUPPORTED_DEVICES += gl-ar750" to the Makefile, to make sysupgrade accept the image without "-F" switch on ar71xx * the device has "printed MAC-address from case" + 1 for the LAN-ports. Not sure what is used with vendor FW. Sven ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH v2] ramips: Fix compatible for YUKAI Engineering BOCCO
Looks like an undetected copy/paste error.
Signed-off-by: Adrian Schmutzler
---
Changes in v2:
- Removed SUPPORTED_DEVICES again, as it is not required
---
target/linux/ramips/dts/BOCCO.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/ramips/dts/BOCCO.dts
b/target/linux/ramips/dts/BOCCO.dts
index 6b6ac754ea..cc9c6688dc 100644
--- a/target/linux/ramips/dts/BOCCO.dts
+++ b/target/linux/ramips/dts/BOCCO.dts
@@ -6,7 +6,7 @@
#include
/ {
- compatible = "planex,cs-qr10", "ralink,mt7620a-soc";
+ compatible = "yukai,bocco", "ralink,mt7620a-soc";
model = "YUKAI Engineering BOCCO";
keys {
--
2.20.1
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] ath10k-ct 4.19 and IBSS
> On 27 Jun 2019, at 15:49, Koen Vandeputte > wrote: > > >> On 6/27/19 7:17 AM, Koen Vandeputte wrote: > > I'm really wondering if the additional openwrt patches on top come in play > here .. > I'm not able to even send a simple ping across the link. Agreed. The ath10k-ct patches in package/kernel/ath10k-ct/patches make for disturbing reading although they apply cleanly. Cheers, Kevin D-B gpg: 012C ACB2 28C6 C53E 9775 9123 B3A2 389B 9DE2 334A signature.asc Description: Message signed with OpenPGP ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] ath10k-ct 4.19 and IBSS
On 27.06.19 16:24, Ben Greear wrote:
On 6/27/19 7:17 AM, Koen Vandeputte wrote:
On 26.06.19 18:39, Ben Greear wrote:
On 6/26/19 9:28 AM, Koen Vandeputte wrote:
On 26.06.19 18:16, Ben Greear wrote:
On 6/26/19 2:02 AM, Koen Vandeputte wrote:
On 25.06.19 15:54, Ben Greear wrote:
On 06/25/2019 02:53 AM, Koen Vandeputte wrote:
On 24.06.19 22:04, Ben Greear wrote:
On 6/24/19 8:32 AM, Koen Vandeputte wrote:
Hi Ben,
Hi All,
So I'm going to give this another try ..
As the IBSS functionality is heavily advertised as a delta to
mainline, it would be very nice to get it working also :)
Testing the latest ath10k-ct driver and firmware seems to be
a step back compared to roughly a month ago.
I'm currently seeing the firmware crashing, which was not the
case before:
ath10k-ct + htt-fw:
https://pastebin.com/raw/7Sy9yx6s
Looks like firmware ran out of some WMI event buffers and
crashed instead of handling
it more gracefully.
Please try the attached (untested) firmware and see if it
behaves better.
Hi Ben,
1 step forward here.
I'm not seeing crashes anymore using the test-firmware.
https://pastebin.com/raw/4ZeXu7iw
I've linked up 2 IBSS devices (wave 1, VHT80)
OLSR traffic (UDP) works and packets here are nicely going back
& forth.
Simply pinging (ICMP) between the 2 devices does not work.
When sending 100 pings, (64 byte large) sometimes 1 gets
through .. but with a latency of > 500ms
I think if the splat and the beacon spam below could be fixed
.. this would be a major step forward:
[ 30.328423] [ cut here ]
[ 30.333251] WARNING: CPU: 0 PID: 1578 at
/mnt/ramdisk/koen/firmware/builds/generic_rb922/build_dir/target-mips_24kc_musl/linux-ar71xx_mikrotik/ath10k-ct-2019-05-08-f98b6dc4/ath10k-4.19/mac.c:6563
ath10k_mac_vif_beacon_free+0xc7c/0x115c [ath10k_core]
[ 30.355636] Modules linked in: mbt ath9k ath9k_common
qcserial pppoe ppp_async option cdc_mbim ath9k_hw ath10k_pci
ath10k_core ath usb_wwan sierra_net sierra rndis_host qmi_wwan
pppox ppp_generic mac80211 iptable_nat iptable_mangle
iptable_filter ipt_REJECT ipt_MASQUERADE ip_tables
huawei_cdc_ncm ftdi_sio cfg80211 cdc_subset cdc_ncm cdc_ether
xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac
xt_limt
[ 30.427331] nls_utf8 nls_iso8859_1 nls_cp437 authenc
ehci_platform sd_mod scsi_mod ehci_hcd gpio_button_hotplug ext4
mbcache jbd2 usbcore nls_base usb_common ptp pps_core mii aead
crypto_null cryptomgr crc32c_generic crypto_hash
[ 30.448017] CPU: 0 PID: 1578 Comm: wpa_supplicant Not
tainted 4.14.129 #0
Please look in your code and let me know the source around the
line in mac.c (6563) that is splatting.
Also, you might grab the latest ath10k-ct repo, it has a tweak
that might fix the SWBA overrun
messages.
https://github.com/greearb/ath10k-ct
Thanks,
Ben
Hi Ben,
Here is the output based on the latest git HEAD of your ct tree,
combined with the test firmware:
https://pastebin.com/raw/kwC6c18J
Hello,
The splat decode does not match the source code, so I'm not which
is correct.
OpenWrt seems to add custom patches to your source.
Please find the complete source in subsequent mail as being build.
I did look in that code, and that is where I saw the mismatch.
Please check your own local system
and see if the splat matches your code? Maybe I made some mistake
of course...
You can paste ~20 lines of code around the proper splat line and
then I can find it in my
source...
Thanks,
Ben
Hi Ben,
Just retried again on a slightly older commit (2019-05-08) and the
splat points to another location now.
When looking it up, it again points to the WARN_ON pointed below ..
Checking shows that all calls to ath10k_mac_vif_beacon_free() calls
are way above this line (highest line nr is around line1970)
I currently can't explain where the mismatch comes from ..
Current build below is just the git HEAD of openwrt 19.07 branch,
cloned, build and flashed without any modification.
[ 31.956774] WARNING: CPU: 0 PID: 1725 at
/mnt/ramdisk/koen/firmware/builds/generic_rb922/build_dir/target-mips_24kc_musl/linux-ar71xx_mikrotik/ath10k-ct-2019-05-08-f98b6dc4/ath10k-4.19/mac.c:6563
ath10k_mac_vif_beacon_free+0xc7c/0x115c [ath10k_core]
ret = ath10k_config_ps(ar);
if (ret)
ath10k_warn(ar, "failed to setup ps on vdev
%i: %d\n",
arvif->vdev_id, ret);
}
if (changed & BSS_CHANGED_MCAST_RATE &&
---> !WARN_ON(ath10k_mac_vif_chan(arvif->vif, &def))) {
band = def.chan->band;
I think this might not be to serious of a bug, and probably does not
cause any real
trouble.
It is also probably a bug in mac80211 or similar, but not certain
about that.
The general set of bugs related to IBSS seem to be inability to
transmit frames
sometimes (though it usually works well in my lab, so I have not been
able to real
Re: [OpenWrt-Devel] ath10k-ct 4.19 and IBSS
On 6/27/19 7:17 AM, Koen Vandeputte wrote:
On 26.06.19 18:39, Ben Greear wrote:
On 6/26/19 9:28 AM, Koen Vandeputte wrote:
On 26.06.19 18:16, Ben Greear wrote:
On 6/26/19 2:02 AM, Koen Vandeputte wrote:
On 25.06.19 15:54, Ben Greear wrote:
On 06/25/2019 02:53 AM, Koen Vandeputte wrote:
On 24.06.19 22:04, Ben Greear wrote:
On 6/24/19 8:32 AM, Koen Vandeputte wrote:
Hi Ben,
Hi All,
So I'm going to give this another try ..
As the IBSS functionality is heavily advertised as a delta to mainline, it
would be very nice to get it working also :)
Testing the latest ath10k-ct driver and firmware seems to be a step back
compared to roughly a month ago.
I'm currently seeing the firmware crashing, which was not the case before:
ath10k-ct + htt-fw:
https://pastebin.com/raw/7Sy9yx6s
Looks like firmware ran out of some WMI event buffers and crashed instead of
handling
it more gracefully.
Please try the attached (untested) firmware and see if it behaves better.
Hi Ben,
1 step forward here.
I'm not seeing crashes anymore using the test-firmware.
https://pastebin.com/raw/4ZeXu7iw
I've linked up 2 IBSS devices (wave 1, VHT80)
OLSR traffic (UDP) works and packets here are nicely going back & forth.
Simply pinging (ICMP) between the 2 devices does not work.
When sending 100 pings, (64 byte large) sometimes 1 gets through .. but with a
latency of > 500ms
I think if the splat and the beacon spam below could be fixed .. this would be
a major step forward:
[ 30.328423] [ cut here ]
[ 30.333251] WARNING: CPU: 0 PID: 1578 at
/mnt/ramdisk/koen/firmware/builds/generic_rb922/build_dir/target-mips_24kc_musl/linux-ar71xx_mikrotik/ath10k-ct-2019-05-08-f98b6dc4/ath10k-4.19/mac.c:6563 ath10k_mac_vif_beacon_free+0xc7c/0x115c
[ath10k_core]
[ 30.355636] Modules linked in: mbt ath9k ath9k_common qcserial pppoe ppp_async option cdc_mbim ath9k_hw ath10k_pci ath10k_core ath usb_wwan sierra_net
sierra rndis_host qmi_wwan pppox ppp_generic mac80211 iptable_nat iptable_mangle iptable_filter ipt_REJECT ipt_MASQUERADE ip_tables huawei_cdc_ncm
ftdi_sio cfg80211 cdc_subset cdc_ncm cdc_ether xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limt
[ 30.427331] nls_utf8 nls_iso8859_1 nls_cp437 authenc ehci_platform sd_mod scsi_mod ehci_hcd gpio_button_hotplug ext4 mbcache jbd2 usbcore nls_base
usb_common ptp pps_core mii aead crypto_null cryptomgr crc32c_generic crypto_hash
[ 30.448017] CPU: 0 PID: 1578 Comm: wpa_supplicant Not tainted 4.14.129 #0
Please look in your code and let me know the source around the line in mac.c
(6563) that is splatting.
Also, you might grab the latest ath10k-ct repo, it has a tweak that might fix
the SWBA overrun
messages.
https://github.com/greearb/ath10k-ct
Thanks,
Ben
Hi Ben,
Here is the output based on the latest git HEAD of your ct tree, combined with
the test firmware:
https://pastebin.com/raw/kwC6c18J
Hello,
The splat decode does not match the source code, so I'm not which is correct.
OpenWrt seems to add custom patches to your source.
Please find the complete source in subsequent mail as being build.
I did look in that code, and that is where I saw the mismatch. Please check
your own local system
and see if the splat matches your code? Maybe I made some mistake of course...
You can paste ~20 lines of code around the proper splat line and then I can
find it in my
source...
Thanks,
Ben
Hi Ben,
Just retried again on a slightly older commit (2019-05-08) and the splat points
to another location now.
When looking it up, it again points to the WARN_ON pointed below ..
Checking shows that all calls to ath10k_mac_vif_beacon_free() calls are way
above this line (highest line nr is around line1970)
I currently can't explain where the mismatch comes from ..
Current build below is just the git HEAD of openwrt 19.07 branch, cloned, build
and flashed without any modification.
[ 31.956774] WARNING: CPU: 0 PID: 1725 at
/mnt/ramdisk/koen/firmware/builds/generic_rb922/build_dir/target-mips_24kc_musl/linux-ar71xx_mikrotik/ath10k-ct-2019-05-08-f98b6dc4/ath10k-4.19/mac.c:6563
ath10k_mac_vif_beacon_free+0xc7c/0x115c [ath10k_core]
ret = ath10k_config_ps(ar);
if (ret)
ath10k_warn(ar, "failed to setup ps on vdev %i: %d\n",
arvif->vdev_id, ret);
}
if (changed & BSS_CHANGED_MCAST_RATE &&
---> !WARN_ON(ath10k_mac_vif_chan(arvif->vif, &def))) {
band = def.chan->band;
I think this might not be to serious of a bug, and probably does not cause any
real
trouble.
It is also probably a bug in mac80211 or similar, but not certain about that.
The general set of bugs related to IBSS seem to be inability to transmit frames
sometimes (though it usually works well in my lab, so I have not been able to
really
debug it).
The simpler the test case, the better. So, if you can repr
[OpenWrt-Devel] [PATCH] ramips: Fix compatible for YUKAI Engineering BOCCO
Looks like an undetected copy/paste error.
Signed-off-by: Adrian Schmutzler
---
target/linux/ramips/dts/BOCCO.dts | 2 +-
target/linux/ramips/image/mt7620.mk | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/target/linux/ramips/dts/BOCCO.dts
b/target/linux/ramips/dts/BOCCO.dts
index 6b6ac754ea..cc9c6688dc 100644
--- a/target/linux/ramips/dts/BOCCO.dts
+++ b/target/linux/ramips/dts/BOCCO.dts
@@ -6,7 +6,7 @@
#include
/ {
- compatible = "planex,cs-qr10", "ralink,mt7620a-soc";
+ compatible = "yukai,bocco", "ralink,mt7620a-soc";
model = "YUKAI Engineering BOCCO";
keys {
diff --git a/target/linux/ramips/image/mt7620.mk
b/target/linux/ramips/image/mt7620.mk
index 077834edc8..183fe2592a 100644
--- a/target/linux/ramips/image/mt7620.mk
+++ b/target/linux/ramips/image/mt7620.mk
@@ -131,6 +131,7 @@ define Device/bocco
DTS := BOCCO
DEVICE_TITLE := YUKAI Engineering BOCCO
DEVICE_PACKAGES := kmod-sound-core kmod-sound-mt7620 kmod-i2c-ralink
+ SUPPORTED_DEVICES += planex,cs-qr10
endef
TARGET_DEVICES += bocco
--
2.20.1
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] ath10k-ct 4.19 and IBSS
On 26.06.19 18:39, Ben Greear wrote:
On 6/26/19 9:28 AM, Koen Vandeputte wrote:
On 26.06.19 18:16, Ben Greear wrote:
On 6/26/19 2:02 AM, Koen Vandeputte wrote:
On 25.06.19 15:54, Ben Greear wrote:
On 06/25/2019 02:53 AM, Koen Vandeputte wrote:
On 24.06.19 22:04, Ben Greear wrote:
On 6/24/19 8:32 AM, Koen Vandeputte wrote:
Hi Ben,
Hi All,
So I'm going to give this another try ..
As the IBSS functionality is heavily advertised as a delta to
mainline, it would be very nice to get it working also :)
Testing the latest ath10k-ct driver and firmware seems to be a
step back compared to roughly a month ago.
I'm currently seeing the firmware crashing, which was not the
case before:
ath10k-ct + htt-fw:
https://pastebin.com/raw/7Sy9yx6s
Looks like firmware ran out of some WMI event buffers and
crashed instead of handling
it more gracefully.
Please try the attached (untested) firmware and see if it
behaves better.
Hi Ben,
1 step forward here.
I'm not seeing crashes anymore using the test-firmware.
https://pastebin.com/raw/4ZeXu7iw
I've linked up 2 IBSS devices (wave 1, VHT80)
OLSR traffic (UDP) works and packets here are nicely going back &
forth.
Simply pinging (ICMP) between the 2 devices does not work.
When sending 100 pings, (64 byte large) sometimes 1 gets through
.. but with a latency of > 500ms
I think if the splat and the beacon spam below could be fixed ..
this would be a major step forward:
[ 30.328423] [ cut here ]
[ 30.333251] WARNING: CPU: 0 PID: 1578 at
/mnt/ramdisk/koen/firmware/builds/generic_rb922/build_dir/target-mips_24kc_musl/linux-ar71xx_mikrotik/ath10k-ct-2019-05-08-f98b6dc4/ath10k-4.19/mac.c:6563
ath10k_mac_vif_beacon_free+0xc7c/0x115c [ath10k_core]
[ 30.355636] Modules linked in: mbt ath9k ath9k_common qcserial
pppoe ppp_async option cdc_mbim ath9k_hw ath10k_pci ath10k_core
ath usb_wwan sierra_net sierra rndis_host qmi_wwan pppox
ppp_generic mac80211 iptable_nat iptable_mangle iptable_filter
ipt_REJECT ipt_MASQUERADE ip_tables huawei_cdc_ncm ftdi_sio
cfg80211 cdc_subset cdc_ncm cdc_ether xt_time xt_tcpudp xt_state
xt_nat xt_multiport xt_mark xt_mac xt_limt
[ 30.427331] nls_utf8 nls_iso8859_1 nls_cp437 authenc
ehci_platform sd_mod scsi_mod ehci_hcd gpio_button_hotplug ext4
mbcache jbd2 usbcore nls_base usb_common ptp pps_core mii aead
crypto_null cryptomgr crc32c_generic crypto_hash
[ 30.448017] CPU: 0 PID: 1578 Comm: wpa_supplicant Not tainted
4.14.129 #0
Please look in your code and let me know the source around the
line in mac.c (6563) that is splatting.
Also, you might grab the latest ath10k-ct repo, it has a tweak
that might fix the SWBA overrun
messages.
https://github.com/greearb/ath10k-ct
Thanks,
Ben
Hi Ben,
Here is the output based on the latest git HEAD of your ct tree,
combined with the test firmware:
https://pastebin.com/raw/kwC6c18J
Hello,
The splat decode does not match the source code, so I'm not which is
correct.
OpenWrt seems to add custom patches to your source.
Please find the complete source in subsequent mail as being build.
I did look in that code, and that is where I saw the mismatch. Please
check your own local system
and see if the splat matches your code? Maybe I made some mistake of
course...
You can paste ~20 lines of code around the proper splat line and then
I can find it in my
source...
Thanks,
Ben
Hi Ben,
Just retried again on a slightly older commit (2019-05-08) and the splat
points to another location now.
When looking it up, it again points to the WARN_ON pointed below ..
Checking shows that all calls to ath10k_mac_vif_beacon_free() calls are
way above this line (highest line nr is around line1970)
I currently can't explain where the mismatch comes from ..
Current build below is just the git HEAD of openwrt 19.07 branch,
cloned, build and flashed without any modification.
[ 31.956774] WARNING: CPU: 0 PID: 1725 at
/mnt/ramdisk/koen/firmware/builds/generic_rb922/build_dir/target-mips_24kc_musl/linux-ar71xx_mikrotik/ath10k-ct-2019-05-08-f98b6dc4/ath10k-4.19/mac.c:6563
ath10k_mac_vif_beacon_free+0xc7c/0x115c [ath10k_core]
ret = ath10k_config_ps(ar);
if (ret)
ath10k_warn(ar, "failed to setup ps on vdev %i:
%d\n",
arvif->vdev_id, ret);
}
if (changed & BSS_CHANGED_MCAST_RATE &&
---> !WARN_ON(ath10k_mac_vif_chan(arvif->vif, &def))) {
band = def.chan->band;
mcast_rate = vif->bss_conf.mcast_rate[band];
if (mcast_rate > 0)
rateidx = mcast_rate - 1;
else
rateidx = ffs(vif->bss_conf.basic_rates) - 1;
if (ar->phy_capability & WHAL_WLAN_11A_CAPABILITY)
Regards,
Koen
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
ht
Re: [OpenWrt-Devel] [PATCH, v5] uqmi: add explicit check for message type when expecting a response
On 20.06.19 12:45, Tautvydas Belgeras wrote: When the utility sends a request it expects a response type message, but does not explicitly check for it. When a device stays idle for some time, it switches into a sleep mode, and notifies the utility with an identification type message. In some configurations the device only sends this identification message when triggered by the utility, in this case by the request message. What the utility gets is two messages at the same time - an identification and a response. When it tries to decode former it obviously fails, because it is not what it expected. Signed-off-by: Tautvydas Belgeras --- dev.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/dev.c b/dev.c index 4bca429..bd10207 100644 --- a/dev.c +++ b/dev.c @@ -96,6 +96,9 @@ static void qmi_process_msg(struct qmi_dev *qmi, struct qmi_msg *msg) struct qmi_request *req; uint16_t tid; + if (msg->flags != QMI_CTL_FLAG_RESPONSE && msg->flags != QMI_SERVICE_FLAG_RESPONSE) + return; + if (msg->qmux.service == QMI_SERVICE_CTL) tid = msg->ctl.transaction; else Merged in Uqmi master Thanks for the fix! Regards, Koen ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
