Linux wireless drivers development
 help / color / mirror / Atom feed
From: Ramasamy Kaliappan <ramasamy.kaliappan@oss.qualcomm.com>
To: Benjamin Berg <benjamin@sipsolutions.net>,
	linux-wireless@vger.kernel.org,
	Jouni Malinen <jouni.malinen@oss.qualcomm.com>,
	johannes@sipsolutions.net
Cc: Rameshkumar Sundaram <rameshkumar.sundaram@oss.qualcomm.com>
Subject: Re: [RFC PATCH v2 0/8] Adding NO_STA flag and reworking RX link resolution
Date: Tue, 5 May 2026 23:09:10 +0530	[thread overview]
Message-ID: <b2232118-9117-4ead-94ba-7c5435844079@oss.qualcomm.com> (raw)
In-Reply-To: <640192308052e60589455505d31732cf2e00b1aa.camel@sipsolutions.net>



On 4/27/2026 4:43 PM, Benjamin Berg wrote:
> I believe that hostapd will need a bit of refactoring, including
> improved tracking to know whether a STA has been inserted into the
> driver and whether to TX the AUTH frames using the link address and
> NO_STA flag or using the MLD Address.
I agree with this design. Refactoring hostapd to handle all STA 
consistently both in the driver and in hostapd in scenarios where a STA 
roams with MLD and link address swaps occurs, in both legacy and MLO cases.

Additionally, the design should help accommodate upcoming requirements 
such as Wi‑Fi 8 (802.11bi). In particular, it can address scenarios 
where a non‑AP ML STA link address needs to be translated to a DS 
address in the STA mode, while on the AP mode the link address 
translated to the MLD address. I believe these aspects can be handled as 
part of this design.

Thanks,
Ramasamy.

  reply	other threads:[~2026-05-05 17:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-23 12:38 [RFC PATCH v2 0/8] Adding NO_STA flag and reworking RX link resolution Benjamin Berg
2026-02-23 12:38 ` [RFC PATCH v2 1/8] wifi: iwlwifi: use link_sta internally to the driver Benjamin Berg
2026-02-23 12:38 ` [RFC PATCH v2 2/8] wifi: mac80211: change public RX API to use link stations Benjamin Berg
2026-02-24 17:41   ` Ramasamy Kaliappan
2026-02-25  9:19     ` Berg, Benjamin
2026-02-24 18:22   ` Jeff Johnson
2026-02-23 12:38 ` [RFC PATCH v2 3/8] wifi: mac80211: refactor RX link_id and station handling Benjamin Berg
2026-02-23 12:38 ` [RFC PATCH v2 4/8] wifi: mac80211: rework RX packet handling Benjamin Berg
2026-02-23 12:38 ` [RFC PATCH v2 5/8] wifi: cfg80211: add attribute for TX/RX denoting there is no station Benjamin Berg
2026-02-23 12:38 ` [RFC PATCH v2 6/8] wifi: mac80211: report to cfg80211 when no STA is known for a frame Benjamin Berg
2026-02-23 12:38 ` [RFC PATCH v2 7/8] wifi: mac80211: pass station to ieee80211_tx_skb_tid Benjamin Berg
2026-02-24 17:45   ` Ramasamy Kaliappan
2026-02-25  9:28     ` Benjamin Berg
2026-02-23 12:38 ` [RFC PATCH v2 8/8] wifi: mac80211: pass error station if non-STA transmit was requested Benjamin Berg
2026-02-24 17:47   ` Ramasamy Kaliappan
2026-02-25  9:15     ` Benjamin Berg
2026-02-24 17:35 ` [RFC PATCH v2 0/8] Adding NO_STA flag and reworking RX link resolution Ramasamy Kaliappan
2026-04-27 10:02 ` Ramasamy Kaliappan
2026-04-27 11:13   ` Benjamin Berg
2026-05-05 17:39     ` Ramasamy Kaliappan [this message]
2026-04-27 14:24   ` Johannes Berg

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=b2232118-9117-4ead-94ba-7c5435844079@oss.qualcomm.com \
    --to=ramasamy.kaliappan@oss.qualcomm.com \
    --cc=benjamin@sipsolutions.net \
    --cc=johannes@sipsolutions.net \
    --cc=jouni.malinen@oss.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rameshkumar.sundaram@oss.qualcomm.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