From: Gang Yan <gang_yan@foxmail.com>
To: Miri Korenblit <miriam.rachel.korenblit@intel.com>,
Kalle Valo <kvalo@kernel.org>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Issue with iwlwifi Firmware Loading When Compiled into the Kernel
Date: Thu, 31 Oct 2024 09:46:20 +0800 [thread overview]
Message-ID: <tencent_2C31282B61589DFCC908B3831384D569440A@qq.com> (raw)
Dear Maintainer,
Recently, I met an issue that I would like to bring to your attention and
seek your expertise on.
When I compile the iwlwifi driver directly into the kernel by setting
[CONFIG_IWLWIFI=y], I encounter an error message stating, "iwlwifi direct
firmware load for iwlwifi-so-XXXX failed." However, the relevant firmware
files are present in the /lib/firmware directory.
Based on my observations, I suspect that when iwlwifi is compiled into the
kernel, it attempts to load the firmware before the /lib/firmware directory
mounted. Consequently, the firmware cannot be found. Once the filesystem is
mounted, iwlwifi does not attempt to reload the firmware.
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.
From my perspective, unless there are compelling reasons to pursue the first
option, I would recommend implementing the second solution. It seems more
straightforward and avoids potential complications that might arise from
modifying the driver's core functionality.
I would greatly appreciate your insights on whether my understanding of the
issue is correct and whether such modifications are deemed necessary.
Thank you for your time and consideration.
Best regards,
Gang Yan
next reply other threads:[~2024-10-31 2:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 1:46 Gang Yan [this message]
2024-10-31 8:06 ` Johannes Berg
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=tencent_2C31282B61589DFCC908B3831384D569440A@qq.com \
--to=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®