From: Jakub Kicinski <kuba@kernel.org>
To: Vitaliy Sochnev <sochnev.v.74@gmail.com>
Cc: Lorenzo Bianconi <lorenzo@kernel.org>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
stable@vger.kernel.org,
linux-arm-kernel@lists.infradead.org (moderated list:AIROHA
ETHERNET DRIVER),
linux-mediatek@lists.infradead.org (moderated list:AIROHA
ETHERNET DRIVER),
netdev@vger.kernel.org (open list:AIROHA ETHERNET DRIVER),
linux-kernel@vger.kernel.org (open list)
Subject: Re: [PATCH net v2] net: airoha: npu: load the firmware without the sysfs fallback
Date: Mon, 17 Aug 2026 11:24:14 -0700 [thread overview]
Message-ID: <20260817112414.0e82a395@kernel.org> (raw)
In-Reply-To: <20260811181717.19339-1-sochnev.v.74@gmail.com>
On Tue, 11 Aug 2026 19:16:59 +0100 Vitaliy Sochnev wrote:
> airoha_npu_load_firmware() maps a missing firmware file to -EPROBE_DEFER
> so that the NPU can be brought up once the rootfs carrying /lib/firmware
> has been mounted. That mapping holds only as long as request_firmware()
> reports -ENOENT.
Okay, but AFAIU this is a hack. AFAIU PROBE_DEFER is not meant to
be used for FW loading. The driver module should live on the same
'partition' as the firmware. Either have them both available in initrd,
or have neither?
next prev parent reply other threads:[~2026-08-17 18:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 18:16 [PATCH net v2] net: airoha: npu: load the firmware without the sysfs fallback Vitaliy Sochnev
2026-08-13 13:33 ` Simon Horman
2026-08-17 18:24 ` Jakub Kicinski [this message]
2026-08-17 19:45 ` 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=20260817112414.0e82a395@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=lorenzo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sochnev.v.74@gmail.com \
--cc=stable@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