Linux wireless drivers development
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: <linux-wireless@vger.kernel.org>
Cc: <ku920601@realtek.com>, <kevin_yang@realtek.com>
Subject: [PATCH v2 rtw-next 0/3] wifi: rtw89: 8922d: increase firmware format to 1
Date: Wed, 7 Oct 2026 09:10:54 +0800	[thread overview]
Message-ID: <20261007011057.12125-1-pkshih@realtek.com> (raw)

The firmware commands/events formats are changed since 0.35.119.0, and
BT-coxistence has much changes needed implementation in driver side.
Update the firmware format version to support newer formats and features.

v2:
 - add patch 2/3 to support NZ/BR/AR specific regulation.
 - in patch 3/3, mention the changes of patch 2/3 is one of reason
   to increase the fw version.

Ching-Te Ku (1):
  wifi: rtw89: coex: Update Wi-Fi/Bluetooth coexistence version to
    9.24.2

Ping-Ke Shih (1):
  wifi: rtw89: 8922d: update supported firmware format to 1

Zong-Zhe Yang (1):
  wifi: rtw89: regd: add NZ/BR/AR for individual TX power settings

 drivers/net/wireless/realtek/rtw89/coex.c     | 2 +-
 drivers/net/wireless/realtek/rtw89/core.h     | 3 +++
 drivers/net/wireless/realtek/rtw89/regd.c     | 3 +++
 drivers/net/wireless/realtek/rtw89/rtw8922d.c | 4 ++--
 4 files changed, 9 insertions(+), 3 deletions(-)


base-commit: 7cde94dab0e74434ccc0a387d7ad373fb3becda0
-- 
2.25.1


             reply	other threads:[~2026-10-07  1:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-07  1:10 Ping-Ke Shih [this message]
2026-10-07  1:10 ` [PATCH v2 rtw-next 1/3] wifi: rtw89: coex: Update Wi-Fi/Bluetooth coexistence version to 9.24.2 Ping-Ke Shih
2026-10-08  2:39   ` Ping-Ke Shih
2026-10-07  1:10 ` [PATCH v2 rtw-next 2/3] wifi: rtw89: regd: add NZ/BR/AR for individual TX power settings Ping-Ke Shih
2026-10-07  1:10 ` [PATCH v2 rtw-next 3/3] wifi: rtw89: 8922d: update supported firmware format to 1 Ping-Ke Shih

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=20261007011057.12125-1-pkshih@realtek.com \
    --to=pkshih@realtek.com \
    --cc=kevin_yang@realtek.com \
    --cc=ku920601@realtek.com \
    --cc=linux-wireless@vger.kernel.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