From: Ben Greear <greearb@candelatech.com>
To: Sven Eckelmann <sven@narfation.org>, ath10k@lists.infradead.org
Cc: Sebastian Gottschall <s.gottschall@dd-wrt.com>
Subject: Re: EAP AP/VLAN: multicast not send to client
Date: Sun, 7 Feb 2021 09:42:42 -0800 [thread overview]
Message-ID: <fe6fa272-30ac-9588-d2a2-c89647beefbb@candelatech.com> (raw)
In-Reply-To: <2516016.JH6pyVjoBS@sven-edge>
On 2/7/21 9:13 AM, Sven Eckelmann wrote:
> On Sunday, 7 February 2021 17:50:11 CET Ben Greear wrote:
>> Here are the images:
>>
>> http://www.candelatech.com/downloads/ath10k-4019-10-4b/bisect/
>
> Thanks, will try to have look at them tomorrow evening. Can you confirm which
> QCA ath10k version was used as the base for this one? I've read somewhere on
> your page 10.4.3.3-25 - which doesn't seem to be in Kalles' repository. And my
> original plan was to test the relevant QCA firmware first and check if the
> problem might already be in the base version which you've used for your
> builds. But maybe I will just start with the oldest one in you tree and check
> if the problem is also there and based on the result decide how to continue.
I don't know exactly how qca versioning works, but my notes are that the initial
upstream wave-2 code was 3.5.3-00050, from back in 2018.
The first commit in the series should be very similar to stock FW, though perhaps
missing some feature flags. Maybe try forcing the driver to try to allow
vlans...if it is missing feature flag only, that might work around it.
Somewhere along the way I fixed up raw transmit in my firmware, so possibly
only then will vlans really have a chance of working.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2021-02-07 17:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 20:54 EAP AP/VLAN: multicast not send to client Sven Eckelmann
2021-02-02 7:04 ` Sebastian Gottschall
2021-02-02 8:23 ` Sven Eckelmann
2021-02-02 8:58 ` Sebastian Gottschall
2021-02-02 9:06 ` Sven Eckelmann
2021-02-02 9:12 ` Sebastian Gottschall
2021-02-02 10:12 ` Sven Eckelmann
2021-02-02 13:27 ` Ben Greear
2021-02-02 13:57 ` Sven Eckelmann
2021-02-07 16:50 ` Ben Greear
2021-02-07 17:13 ` Sven Eckelmann
2021-02-07 17:42 ` Ben Greear [this message]
2021-02-08 20:32 ` Sven Eckelmann
2021-02-08 20:50 ` Ben Greear
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fe6fa272-30ac-9588-d2a2-c89647beefbb@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=s.gottschall@dd-wrt.com \
--cc=sven@narfation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).