From: Jakub Kicinski <kuba@kernel.org>
To: Kalle Valo <kvalo@kernel.org>
Cc: Ping-Ke Shih <pkshih@realtek.com>,
"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 07:18:48 -0700 [thread overview]
Message-ID: <20230425071848.6156c0a0@kernel.org> (raw)
In-Reply-To: <87leigr06u.fsf@kernel.org>
On Tue, 25 Apr 2023 08:38:17 +0300 Kalle Valo wrote:
> IIRC we discussed this back in initial rtw88 or rtw89 driver review (not
> sure which one). At the time I pushed for the current solution to have
> the initvals in static variables just to avoid any backwards
> compatibility issues. I agree that the initvals in .c files are ugly but
> is it worth all the extra effort and complexity to move them outside the
> kernel? I'm starting to lean towards it's not worth all the extra work.
I don't think it's that much extra work, the driver requires FW
according to modinfo, anyway, so /lib/firmware is already required.
And on smaller systems with few hundred MB of RAM it'd be nice to not
hold all the stuff in kernel memory, I'd think.
We have a rule against putting FW as a static table in the driver
source, right? Or did we abandon that? Isn't this fundamentally similar?
> For me most important is that backwards compatibility is not broken,
> that would be bad for the users. So whatever we decide let's keep that
> in mind.
Right, not for existing devices, only when new device is added.
next prev parent reply other threads:[~2023-04-25 14:19 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
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 [this message]
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=20230425071848.6156c0a0@kernel.org \
--to=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pkshih@realtek.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;
as well as URLs for NNTP newsgroup(s).