From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Johannes Berg <johannes@sipsolutions.net>,
Michael Stapelberg <michael+lkml@stapelberg.ch>
Cc: Kalle Valo <kvalo@kernel.org>,
Franky Lin <franky.lin@broadcom.com>,
Pieter-Paul Giesberts <pieter-paul.giesberts@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
linux-wireless@vger.kernel.org
Subject: Re: wifi breakage due to commit "wifi: brcmfmac: add support for vendor-specific firmware api"
Date: Wed, 15 Mar 2023 11:11:28 +0100 [thread overview]
Message-ID: <f430c376-5992-d394-ce55-5994c793c7c7@broadcom.com> (raw)
In-Reply-To: <a459b9adc5eb7b67a432bd947d47d1df08718762.camel@sipsolutions.net>
[-- Attachment #1: Type: text/plain, Size: 1193 bytes --]
On 3/15/2023 10:57 AM, Johannes Berg wrote:
> On Wed, 2023-03-15 at 10:12 +0100, Arend van Spriel wrote:
>>
>> I think it works pretty similar to firmware loading. These days firmware
>> loading does not rely on a user-space helper and I assumed the same is
>> true for module loading. Will look into it.
>>
>
> As far as I know you still need the modprobe helper in
>
> /proc/sys/kernel/modprobe
Hi Michael,
With hint from Johannes I found this Kconfig option:
config MODPROBE_PATH
string "Path to modprobe binary"
default "/sbin/modprobe"
help
When kernel code requests a module, it does so by calling
the "modprobe" userspace utility. This option allows you to
set the path where that binary is found. This can be changed
at runtime via the sysctl file
/proc/sys/kernel/modprobe. Setting this to the empty string
removes the kernel's ability to request modules (but
userspace can still load modules explicitly).
Now checking the .config that you sent it says:
CONFIG_MODPROBE_PATH="/sbin/modprobe"
So my suspicion is that modprobe is not at that given location?
Regards,
Arend
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4219 bytes --]
next prev parent reply other threads:[~2023-03-15 10:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 19:38 wifi breakage due to commit "wifi: brcmfmac: add support for vendor-specific firmware api" Michael Stapelberg
2023-03-14 22:26 ` Arend Van Spriel
2023-03-14 22:48 ` Michael Stapelberg
2023-03-14 23:21 ` Arend Van Spriel
2023-03-15 7:58 ` Michael Stapelberg
2023-03-15 8:33 ` Arend Van Spriel
2023-03-15 8:53 ` Michael Stapelberg
2023-03-15 9:12 ` Arend van Spriel
2023-03-15 9:57 ` Johannes Berg
2023-03-15 10:00 ` Arend van Spriel
2023-03-15 10:11 ` Arend van Spriel [this message]
2023-03-15 19:53 ` Michael Stapelberg
2023-03-16 6:17 ` Arend Van Spriel
2023-03-16 7:54 ` Michael Stapelberg
2023-03-16 9:40 ` Arend van Spriel
2023-03-17 8:04 ` Michael Stapelberg
2023-03-17 9:13 ` Arend van Spriel
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=f430c376-5992-d394-ce55-5994c793c7c7@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=johannes@sipsolutions.net \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=michael+lkml@stapelberg.ch \
--cc=pieter-paul.giesberts@broadcom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.