From: Johannes Berg <johannes@sipsolutions.net>
To: Gang Yan <gang_yan@foxmail.com>,
Miri Korenblit <miriam.rachel.korenblit@intel.com>,
Kalle Valo <kvalo@kernel.org>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Issue with iwlwifi Firmware Loading When Compiled into the Kernel
Date: Thu, 31 Oct 2024 09:06:49 +0100 [thread overview]
Message-ID: <7100cb98b8e46793cfb1197c3af0f151a9628c9d.camel@sipsolutions.net> (raw)
In-Reply-To: <tencent_2C31282B61589DFCC908B3831384D569440A@qq.com>
>
> To address this issue, I have considered two potential solutions:
>
> 1、Modify the Driver Code: Implement a mechanism, such as delayed_work, to
> give iwlwifi another chance to load the firmware after the filesystem has
> been mounted. This would involve adding additional logic to the driver to
> handle retries for firmware loading.
>
> 2、Modify the Kconfig: Change the configuration to allow iwlwifi to be
> compiled only as a module [CONFIG_IWLWIFI=m]. This way, the module can be
> loaded after the filesystem is fully mounted, ensuring that the firmware
> can be found and loaded successfully.
Neither of those is going to happen - you should just build the firmware
into the kernel (or initramfs might be enough?) if you want it built-in.
Or set up firmware loading userspace, and set it up appropriately to
only respond after / is mounted.
In any case, not a kernel problem. You need to fix it on your userspace.
johannes
next prev parent reply other threads:[~2024-10-31 8:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 1:46 Gang Yan
2024-10-31 8:06 ` Johannes Berg [this message]
2024-10-31 8:52 ` Gang Yan
2024-10-31 8:57 ` Johannes Berg
2024-10-31 9:08 ` Gang Yan
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=7100cb98b8e46793cfb1197c3af0f151a9628c9d.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=gang_yan@foxmail.com \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=miriam.rachel.korenblit@intel.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
all inboxes | Powered by JetHome®