From: "Nicolas Escande" <nico.escande@gmail.com>
To: "Karthikeyan Periyasamy" <quic_periyasa@quicinc.com>,
<ath12k@lists.infradead.org>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] wifi: ath12k: fbx: fix ath12k_hal_tx_cmd_ext_desc_setup() info1 override
Date: Sat, 25 Jan 2025 13:53:22 +0100 [thread overview]
Message-ID: <D7B63ACJOYD0.1XBZ5VB991KOW@gmail.com> (raw)
In-Reply-To: <a979cbc5-5cfe-160d-d5b9-9e5ed7513ed1@quicinc.com>
On Fri Jan 24, 2025 at 4:31 PM CET, Karthikeyan Periyasamy wrote:
> On 1/24/2025 5:03 PM, Nicolas Escande wrote:
>> Since inception there is an obvious typo laying around in
>> ath12k_hal_tx_cmd_ext_desc_setup(). Instead of intitializing + adding
>> flags to tcl_ext_cmd->info1, we initialize + override. This is needed to
>> make broadcast frames work with ethernet encapsulation.
>>
>
> SUPPORTS_TX_ENCAP_OFFLOAD not yet advertised by ath12k. How it work with
> ethernet encapsulation ?
Yes indeed, I made a small patch that adds the right hw features via a module
param like one of your CLO patches did:
+ if (ath12k_frame_mode == ATH12K_HW_TXRX_ETHERNET) {
+ ieee80211_hw_set(hw, SUPPORTS_TX_ENCAP_OFFLOAD);
+ ieee80211_hw_set(hw, SUPPORTS_RX_DECAP_OFFLOAD);
+ }
+
But maybe as this feature is not yet enabled upstream I need remove the fixes
tag ? After all It seems that in native wifi this bug causes no harm...
next prev parent reply other threads:[~2025-01-25 12:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-24 11:33 [PATCH] wifi: ath12k: fbx: fix ath12k_hal_tx_cmd_ext_desc_setup() info1 override Nicolas Escande
2025-01-24 15:31 ` Karthikeyan Periyasamy
2025-01-25 12:53 ` Nicolas Escande [this message]
2025-01-25 14:54 ` Vasanthakumar Thiagarajan
2025-01-25 20:21 ` Nicolas Escande
2025-01-26 3:14 ` Karthikeyan Periyasamy
2025-01-26 18:16 ` Jeff Johnson
2025-01-27 7:07 ` Nicolas Escande
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=D7B63ACJOYD0.1XBZ5VB991KOW@gmail.com \
--to=nico.escande@gmail.com \
--cc=ath12k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_periyasa@quicinc.com \
/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