From: Ping-Ke Shih <pkshih@realtek.com>
To: Jakub Kicinski <kuba@kernel.org>, Kalle Valo <kvalo@kernel.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: pull-request: wireless-next-2023-04-21
Date: Tue, 25 Apr 2023 02:41:46 +0000 [thread overview]
Message-ID: <e31dae6daa6640859d12bf4c4fc41599@realtek.com> (raw)
In-Reply-To: <20230421075404.63c04bca@kernel.org>
> -----Original Message-----
> From: Jakub Kicinski <kuba@kernel.org>
> Sent: Friday, April 21, 2023 10:54 PM
> To: Kalle Valo <kvalo@kernel.org>
> Cc: netdev@vger.kernel.org; linux-wireless@vger.kernel.org
> Subject: Re: pull-request: wireless-next-2023-04-21
>
> On Fri, 21 Apr 2023 10:47:26 +0000 (UTC) Kalle Valo wrote:
> > .../net/wireless/realtek/rtw89/rtw8851b_table.c | 14824 +++++++++++++++++++
> > .../net/wireless/realtek/rtw89/rtw8851b_table.h | 21 +
>
> We should load these like FW, see the proposal outlined in
> https://lore.kernel.org/all/20221116222339.54052a83@kernel.org/
> for example. Would that not work?
>
That would work, and I think struct fields addr and val should be __le32.
And, I have some draft ideas to handle some situations we will face:
1. upgrading to newer driver without built-in tables will break user space
if people don't download table file from linux-firmware.git.
Maybe, we can keep the built-in tables and support loading from files
for couple years at least.
2. c code can do changes along with these tables, so driver should do some
compatibility things for register version.
3. The file contains not only simple registers tables but also TX power tables
and power tracking tables. These tables are multiple dimensions, and
dimensions can be changed due to more channels are supported, for example.
To be backward compatible, we need to add conversion function from
v1, v2 ... to current.
I will think further to make this change smooth.
Ping-Ke
next prev parent reply other threads:[~2023-04-25 2:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 10:47 pull-request: wireless-next-2023-04-21 Kalle Valo
2023-04-21 14:39 ` Jakub Kicinski
2023-04-24 17:34 ` Kalle Valo
2023-04-25 20:52 ` Ryder Lee
2023-04-28 8:50 ` Kalle Valo
2023-04-21 14:54 ` Jakub Kicinski
2023-04-25 2:41 ` Ping-Ke Shih [this message]
2023-04-25 4:14 ` Gregg Wonderly
2023-04-25 4:42 ` Ping-Ke Shih
2023-04-25 5:38 ` Kalle Valo
2023-04-25 14:18 ` Jakub Kicinski
2023-04-25 17:08 ` Johannes Berg
2023-04-26 3:15 ` Ping-Ke Shih
2023-04-26 3:30 ` Ping-Ke Shih
2023-04-26 8:24 ` Johannes Berg
2023-04-27 0:38 ` Ping-Ke Shih
2023-04-28 10:37 ` Kalle Valo
2023-04-28 10:43 ` Kalle Valo
2023-05-01 22:08 ` Jakub Kicinski
2023-04-21 15:00 ` patchwork-bot+netdevbpf
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=e31dae6daa6640859d12bf4c4fc41599@realtek.com \
--to=pkshih@realtek.com \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).