Re: [OpenWrt-Devel] New ath10k-ct driver, supports vlans on 10.1 firmware.
Hello, Ben. Does it mean that AP VLAN mode will use software encryption for every tx frame? Best regards, Kirill Lukonin вт, 18 февр. 2020 г., 7:34 Ben Greear : > Thanks to Matthias Larisch for adding support for AP vlans on 10.1 ct > firmware and testing it out. > > Upstream commit ID: > > bed49a5f6824fcd8757fd27f6b2a4f6ea933bf2f > > If someone can pull this into OpenWRT and test I'd appreciate it. > > Thanks, > Ben > > -- > Ben Greear > Candela Technologies Inc http://www.candelatech.com > > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel > ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH v2 2/2] ath10k-ct: update to version 2019-09-09
Hello, Christian.
This bug was fixed in ath10k-ct by this previous commit.
https://github.com/greearb/ath10k-ct/commit/9e5ab25027e0971fa24ccf93373324c08c4e992d
As I understand, update should be harmless this time.
Best Regards,
Lukonin Kirill
сб, 14 сент. 2019 г. в 00:33, Christian Lamparter :
> On Friday, September 13, 2019 12:15:39 PM CEST Robert Marko wrote:
> > Update the ath10k-ct driver version to
> 5e8cd86f90dac966d12df6ece84ac41458d0e95f
> > to enable dynamic VLANs to work.
> > Packages refreshed while bump.
> >
> > Signed-off-by: Robert Marko
> >
> > Changes from v1:
> > * Fixed wrong mirror hash
>
> Watch out, there's a request to revert the ath10k-ct, since the
> previous "ath10k-ct: update to HEAD of 2019-08-14 - 9e5ab2" patch
> apparently broke 160MHz.
>
>
> https://github.com/openwrt/openwrt/commit/e9d875a5371c89a3f351df5aec593ac90ba89ecc#commitcomment-34992683
>
> I didn't see any 160MHz related fixes in the update here... So what to do?
> Update or revert?
>
> > ---
> > package/kernel/ath10k-ct/Makefile | 6 +++---
> > ...h10k-add-support-for-configuring-management-packet.patch | 4 ++--
> > ...h10k-fix-possible-out-of-bound-access-of-ath10k_ra.patch | 2 +-
> > ...h10k-fix-incorrect-multicast-broadcast-rate-settin.patch | 4 ++--
> > .../patches/164-ath10k-commit-rates-from-mac80211.patch | 6 +++---
> > ...-and-GPIO-controlling-support-for-various-chipsets.patch | 6 +++---
> > .../202-ath10k-4.16-use-tpt-trigger-by-default.patch| 4 ++--
> > ...h10k-Limit-available-channels-via-DT-ieee80211-fre.patch | 2 +-
> > ...h10k-Check-if-station-exists-before-forwarding-tx-.patch | 2 +-
> > 9 files changed, 18 insertions(+), 18 deletions(-)
> >
> > diff --git a/package/kernel/ath10k-ct/Makefile
> b/package/kernel/ath10k-ct/Makefile
> > index 05d30891f5..dbf75fe174 100644
> > --- a/package/kernel/ath10k-ct/Makefile
> > +++ b/package/kernel/ath10k-ct/Makefile
> > @@ -8,9 +8,9 @@ PKG_LICENSE_FILES:=
> >
> > PKG_SOURCE_URL:=https://github.com/greearb/ath10k-ct.git
> > PKG_SOURCE_PROTO:=git
> > -PKG_SOURCE_DATE:=2019-08-14
> > -PKG_SOURCE_VERSION:=9e5ab25027e0971fa24ccf93373324c08c4e992d
> >
> -PKG_MIRROR_HASH:=95dc42a5615f80528223859b4f9618feafb5a0a29a9eb4c4bc983f76c74fb535
> > +PKG_SOURCE_DATE:=2019-09-09
> > +PKG_SOURCE_VERSION:=5e8cd86f90dac966d12df6ece84ac41458d0e95f
> >
> +PKG_MIRROR_HASH:=dc1097f3a7b4b7e346918f206746d00a0b7df07ae3be9b89be55dfaef3cbbe45
> >
> > # Build the 5.2 ath10k-ct driver version. Other option is "-4.19".
> > # Probably this should match as closely as
> > diff --git
> a/package/kernel/ath10k-ct/patches/161-ath10k-add-support-for-configuring-management-packet.patch
> b/package/kernel/ath10k-ct/patches/161-ath10k-add-support-for-configuring-management-packet.patch
> > index d62a1cfcf5..e67003c5a7 100644
> > ---
> a/package/kernel/ath10k-ct/patches/161-ath10k-add-support-for-configuring-management-packet.patch
> > +++
> b/package/kernel/ath10k-ct/patches/161-ath10k-add-support-for-configuring-management-packet.patch
> > @@ -43,7 +43,7 @@ Origin: backport,
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux
> > static int ath10k_mac_get_max_vht_mcs_map(u16 mcs_map, int nss)
> > {
> > switch ((mcs_map >> (2 * nss)) & 0x3) {
> > -@@ -6388,9 +6404,10 @@ static void ath10k_bss_info_changed(stru
> > +@@ -6405,9 +6421,10 @@ static void ath10k_bss_info_changed(stru
> > struct cfg80211_chan_def def;
> > u32 vdev_param, pdev_param, slottime, preamble;
> > u16 bitrate, hw_value;
> > @@ -56,7 +56,7 @@ Origin: backport,
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux
> >
> > mutex_lock(>conf_mutex);
> >
> > -@@ -6596,6 +6613,30 @@ static void ath10k_bss_info_changed(stru
> > +@@ -6613,6 +6630,30 @@ static void ath10k_bss_info_changed(stru
> > arvif->vdev_id, ret);
> > }
> >
> > diff --git
> a/package/kernel/ath10k-ct/patches/162-ath10k-fix-possible-out-of-bound-access-of-ath10k_ra.patch
> b/package/kernel/ath10k-ct/patches/162-ath10k-fix-possible-out-of-bound-access-of-ath10k_ra.patch
> > index ab360b7261..a24029983c 100644
> > ---
> a/package/kernel/ath10k-ct/patches/162-ath10k-fix-possible-out-of-bound-access-of-ath10k_ra.patch
> > +++
> b/package/kernel/ath10k-ct/patches/162-ath10k-fix-possible-out-of-bound-access-of-ath10k_ra.patch
> > @@ -26,7 +26,7 @@ Origin: backport,
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux
> > if (ath10k_rates[i].bitrate == bitrate)
> > return hw_value_prefix | ath10k_rates[i].hw_value;
> > }
> > -@@ -6619,22 +6619,22 @@ static void ath10k_bss_info_changed(stru
> > +@@ -6636,22 +6636,22 @@ static void ath10k_bss_info_changed(stru
> > return;
> > }
> >
> > diff --git
> a/package/kernel/ath10k-ct/patches/163-ath10k-fix-incorrect-multicast-broadcast-rate-settin.patch
>
Re: [OpenWrt-Devel] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 0, skipped old beacon
Hello. This bug was fixed in the master branch. Please try latest snapshot. Best Regards, Lukonin Kirill чт, 22 авг. 2019 г. в 23:06, Yaroslav Petrov : > Hello all, > > > I use OpenWrt 19.07 on BT Home Hub 5A, but it seams ath10k-ct driver is > really unstable (it work only first 2-10 minutes). The ath10k driver > work without problem. Can somebody help me with this issue ? > > > OpenWrt 19.07-SNAPSHOT, r10323-7d300326ee > > dmesg: > ... > [ 16.523669] ath10k_pci :02:00.0: qca988x hw2.0 target 0x4100016c > chip_id 0x043202ff sub : > [ 16.531585] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 > tracing 0 dfs 1 testmode 0 > [ 16.548528] ath10k_pci :02:00.0: firmware ver > 10.1-ct-8x-__fW-022-fddd041b api 2 features > wmi-10.x,has-wmi-mgmt-tx,adaptive-cca,mfp,txstatus-noack,wmi-10.x-CT,ratemask-CT,txrate-CT,get-temp-CT,tx-rc-CT,cust-stats-CT,retry-gt2-CT,txrate2-CT,beacon-cb-CT,wmi-block-ack-CT > > crc32 01d1f13e > [ 16.600527] ath10k_pci :02:00.0: Direct firmware load for > ath10k/QCA988X/hw2.0/board-2.bin failed with error -2 > [ 16.609654] ath10k_pci :02:00.0: Falling back to user helper > [ 16.865926] firmware ath10k!QCA988X!hw2.0!board-2.bin: > firmware_loading_store: map pages failed > [ 16.874176] ath10k_pci :02:00.0: board_file api 1 bmi_id N/A > crc32 bebc7c08 > [ 17.754597] ath10k_pci :02:00.0: 10.1 wmi init: vdevs: 16 peers: > 127 tid: 256 > [ 17.769910] ath10k_pci :02:00.0: wmi print 'P 128 V 8 T 410' > [ 17.774908] ath10k_pci :02:00.0: wmi print 'msdu-desc: 1424 > sw-crypt: 0 ct-sta: 0' > [ 17.782548] ath10k_pci :02:00.0: wmi print 'alloc rem: 24648 > iram: 26168' > [ 17.846700] ath10k_pci :02:00.0: htt-ver 2.1 wmi-op 2 htt-op 2 > cal file max-sta 128 raw 0 hwcrypto 1 > [ 17.858172] ath10k_pci :02:00.0: NOTE: Firmware DBGLOG output > disabled in debug_mask: 0x1000 > ... > [ 9397.052366] ath10k_pci :02:00.0: SWBA overrun on vdev 0, skipped > old beacon > [ 9397.154773] ath10k_pci :02:00.0: SWBA overrun on vdev 0, skipped > old beacon > [ 9397.257174] ath10k_pci :02:00.0: SWBA overrun on vdev 0, skipped > old beacon > [ 9397.359596] ath10k_pci :02:00.0: SWBA overrun on vdev 0, skipped > old beacon > [ 9397.461992] ath10k_pci :02:00.0: SWBA overrun on vdev 0, skipped > old beacon > [ 9397.564396] ath10k_pci :02:00.0: SWBA overrun on vdev 0, skipped > old beacon > [ 9397.666805] ath10k_pci :02:00.0: SWBA overrun on vdev 0, skipped > old beacon > [ 9397.769214] ath10k_pci :02:00.0: SWBA overrun on vdev 0, skipped > old beacon > [ 9397.871646] ath10k_pci :02:00.0: SWBA overrun on vdev 0, skipped > old beacon > [ 9397.974036] ath10k_pci :02:00.0: SWBA overrun on vdev 0, skipped > old beacon > [ 9398.076445] ath10k_pci :02:00.0: SWBA overrun on vdev 0, skipped > old beacon > [ 9398.178844] ath10k_pci :02:00.0: SWBA overrun on vdev 0, skipped > old beacon > [ 9398.281259] ath10k_pci :02:00.0: SWBA overrun on vdev 0, skipped > old beacon > [ 9398.383675] ath10k_pci :02:00.0: SWBA overrun on vdev 0, skipped > old beacon > [ 9398.486071] ath10k_pci :02:00.0: SWBA overrun on vdev 0, skipped > old beacon > [ 9398.588478] ath10k_pci :02:00.0: SWBA overrun on vdev 0, skipped > old beacon > [ 9398.690883] ath10k_pci :02:00.0: SWBA overrun on vdev 0, skipped > old beacon > [ 9398.793301] ath10k_pci :02:00.0: SWBA overrun on vdev 0, skipped > old beacon > [ 9398.895708] ath10k_pci :02:00.0: SWBA overrun on vdev 0, skipped > old beacon > [ 9398.998112] ath10k_pci :02:00.0: SWBA overrun on vdev 0, skipped > old beacon > [ 9399.100512] ath10k_pci :02:00.0: SWBA overrun on vdev 0, skipped > old beacon > [ 9399.202918] ath10k_pci :02:00.0: SWBA overrun on vdev 0, skipped > old beacon > [ 9399.305328] ath10k_pci :02:00.0: SWBA overrun on vdev 0, skipped > old beacon > [ 9399.407740] ath10k_pci :02:00.0: SWBA overrun on vdev 0, skipped > old beacon > [ 9399.510149] ath10k_pci :02:00.0: SWBA overrun on vdev 0, skipped > old beacon > [ 9399.612543] ath10k_pci :02:00.0: SWBA overrun on vdev 0, skipped > old beacon > [ 9399.714959] ath10k_pci :02:00.0: SWBA overrun on vdev 0, skipped > old beacon > [ 9399.817366] ath10k_pci :02:00.0: SWBA overrun on vdev 0, skipped > old beacon > [ 9399.919780] ath10k_pci :02:00.0: SWBA overrun on vdev 0, skipped > old beacon > [ 9400.022177] ath10k_pci :02:00.0: SWBA overrun on vdev 0, skipped > old beacon > [ 9400.124590] ath10k_pci :02:00.0: SWBA overrun on vdev 0, skipped > old beacon > [ 9400.184417] ath10k_pci :02:00.0: wmi command 36893 timeout, > restarting hardware > [ 9400.191096] ath10k_pci :02:00.0: failed to delete peer > 99:99:99:99:99:99 for vdev 0: -11 > [ 9400.199527] ath10k_pci :02:00.0: found sta peer 99:99:99:99:99:99 > (ptr 8698a600 id 361) entry on vdev 0 after it was supposedly removed > [ 9400.212109] [ cut here
Re: [OpenWrt-Devel] [B.A.T.M.A.N.] [RFC openwrt-routing] batman-adv: Split batadv proto in meshif and hardif part
Hello. That looks pretty cool. But what about ELP interval parameter? As I think, it should be covered by UCI config too. Best Regards, Lukonin Kirill пн, 25 февр. 2019 г. в 12:36, Sven Eckelmann : > > On Monday, 25 February 2019 02:24:56 CET Gui Iribarren wrote: > > have you considered, to simplify backwards compatibility, to keep proto > > "batadv" as it currently is (hardif) and naming "batadv_mesh" the new proto? > > It was one of the goals to *not* name the batadv hardif interface proto > "batadv". And I wanted to have the batman-adv interface proto named "batadv" > because this is the rtnl kind string. So you actually create batman-adv > meshifs using: > >ip link add dev bat0 type batadv > > But we can call this proto also "batadv_meshif" if there is a strong > preference for this name. > > Kind regards, > Sven ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
