From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: imx_v6_v7_defconfig: Add CONFIG_FW_LOADER_USER_HELPER_FALLBACK
Date: Thu, 17 Aug 2017 22:12:45 +0800 [thread overview]
Message-ID: <20170817141243.GG7608@dragon> (raw)
In-Reply-To: <20170817140424.4614-1-gary.bisson@boundarydevices.com>
On Thu, Aug 17, 2017 at 04:04:24PM +0200, Gary Bisson wrote:
> Allows to load firmware files which aren't built inside the kernel.
>
> Especially useful for CODA firmware (vpu_fw_imx6q.bin) which is usually
> located in the rootfs.
>
> Signed-off-by: Gary Bisson <gary.bisson@boundarydevices.com>
> ---
> Hi Shawn,
>
> I'm not sure if this patch is acceptable since I've noticed that no
> configuration currently has that option enabled (why?).
>
> As mentioned in the commit, I had to enable that in order to have CODA
> load the VPU firmware properly.
>
> Another option would be to make the CODA driver a module...
>
> Let me know your thoughts.
@Philipp, do you have any comments on this?
>From reading of the option help text, I feel the option is not
recommended?
config FW_LOADER_USER_HELPER_FALLBACK
This option enables / disables the invocation of user-helper
(e.g. udev) for loading firmware files as a fallback after the
direct file loading in kernel fails. The user-mode helper is
no longer required unless you have a special firmware file that
resides in a non-standard path. Moreover, the udev support has
been deprecated upstream.
Shawn
next prev parent reply other threads:[~2017-08-17 14:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 14:04 [PATCH] ARM: imx_v6_v7_defconfig: Add CONFIG_FW_LOADER_USER_HELPER_FALLBACK Gary Bisson
2017-08-17 14:12 ` Shawn Guo [this message]
2017-08-18 7:56 ` Philipp Zabel
2017-08-17 15:11 ` Fabio Estevam
2017-08-17 15:18 ` Gary Bisson
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=20170817141243.GG7608@dragon \
--to=shawnguo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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