All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: Fabrice Goucem <fabrice.goucem@oss.nxp.com>,
	Fabio Estevam <festevam@gmail.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] configs/imx6ullevk_defconfig: bump Linux to 6.6.4 and U-Boot to 2023.10
Date: Sat, 09 Dec 2023 15:57:28 +0100	[thread overview]
Message-ID: <87lea3pgo7.fsf@48ers.dk> (raw)
In-Reply-To: <20231207120704.47607-1-giulio.benetti@benettiengineering.com> (Giulio Benetti's message of "Thu, 7 Dec 2023 13:07:03 +0100")

>>>>> "Giulio" == Giulio Benetti <giulio.benetti@benettiengineering.com> writes:

 > Let's also enable NXP firmware package to let latest SDMA firmware to be
 > loaded. To achieve this we also need to enable dynamic eudev to let it
 > to load the firmware.

Why is that? I thought request_firmware() nowadays didn't need any help
from user space to fetch files from /lib/firmware?

Is it because this is requested very early before the rootfs is mounted?

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2023-12-09 14:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-07 12:07 [Buildroot] [PATCH] configs/imx6ullevk_defconfig: bump Linux to 6.6.4 and U-Boot to 2023.10 Giulio Benetti
2023-12-07 12:07 ` [Buildroot] [PATCH] configs/freescale_imx6ullevk_defconfig: bump Linux and U-Boot to lf-6.1.36-2.1.0 Giulio Benetti
2023-12-07 12:24 ` [Buildroot] [PATCH] configs/imx6ullevk_defconfig: bump Linux to 6.6.4 and U-Boot to 2023.10 Fabio Estevam
2023-12-09 14:57 ` Peter Korsgaard [this message]
2023-12-09 15:06   ` Giulio Benetti
2023-12-09 15:10     ` Peter Korsgaard

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=87lea3pgo7.fsf@48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=fabrice.goucem@oss.nxp.com \
    --cc=festevam@gmail.com \
    --cc=giulio.benetti@benettiengineering.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.